Hi @jameshartig Thanks for reaching out and providing the screenshot. After further investigation on these timings reported similarly from other customers, we have been working with our upstream provider to resolve this issue. Since then, we have observed improvement in DNS times from the Dallas, Fremont, and Newark locations resulting from a fix implemented on March 29th.
Our Atlanta location should now have similarly lower DNS resolution times, beginning around 9AM PT yesterday (4/3). We’re continuing to work with our upstream provider and monitor DNS request timings at these locations, so let us know if you’re continuing to see these high DNS request times.
It looks like the screenshot above was taken on the 30th – is this issue still occurring from any location(s) in particular, or all locations?
There is no present way to ignore (not capture) DNS timings, though you can click the
DNS lookup button below the chart (pictured above) to show adjusted timings without this timing. Additionally, all request timings are broken out into individual attributes of the
SyntheticRequest Insights event, allowing you to generate your own reports within Insights that could exclude these timings. Additional details on the Synthetics data available within Insights can be found here: