Starting around 5AM CST, May 5th, Minneapolis, MN location started to experience some DNS resolution errors to specific URLs. Upon further research, we narrow down issue to AWS DNS servers, such as NS-47.AWSDNS-05.COM. Each time MN location queries AWS DNS servers, the resolution fails. We do not believe it is an issue with AWS DNS, because our other locations resolve OK. Also, MN location works fine with most of other DNS providers. Because of large number of services rely on AWS DNS, for now we disabled monitoring from MN location to avoid false positives. We are actively working to restore the service from MN monitoring location. Please check this page for additional updates as they come: https://www.dotcom-monitor.com/blog/category/dotcom-monitor-system-status/
Why External Synthetic Monitoring is Required to Complete the APM Stack
June 4, 2020
With the digital landscape shifting everything on the web, and companies fighting for better user experiences, your sites and applications are no longer just a
