This article is contributed. See the original author and article here.
We’ve confirmed that all systems are back to normal with no customer impact as of 7/2, 20:00 UTC. Our logs show the incident started on 7/2, 18:00 UTC and that during the 2 hours that it took to resolve the issue customers may have experienced data latency, data gaps and incorrect alert activation
- Root Cause: The failure was due to an incorrect DNS entry.
- Incident Timeline: 2 Hours – 7/2, 18:00 UTC through 7/2, 20:00 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.
Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.