Final Update: Thursday, 21 April 2022 20:27 UTC
We've confirmed that all systems are back to normal with no customer impact as of 17:21 UTC 21 April 2022. Our logs show the incident started on 4:21 UTC 21 April 2022 and that during the 13 hours that it took to resolve the issue where customers using Application Insights JavaScript SDK, OneDS JS SDK, and JSLL SDK were experienced the below errors:
- Browser displays SSL warning/errors in the status bar, and Client telemetry is not sent and is lost
- Customers websites fails to load the requested page and could take end users to their global error page, and Client telemetry is not sent and is lost
- No issues are noticed by end customers, and Client telemetry is not sent and is lost.
- Root Cause: The failure was due to configuration change in authentication system.
- Incident Timeline: 13 hours - 4:21 UTC 21 April 2022 through 17:21 UTC 21 April 2022
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.
-Faraz Khan
Update: Thursday, 21 April 2022 18:00 UTC
Root cause has been isolated to to a configuration change in our authentication system that led to cause requests to fail or be denied. We have applied the mitigation but it may take up to an hour for the change to be fully propagated across all systems and for this to be resolved. Starting at 12:00 UTC on 04/21/22, Customers using Application Insights JavaScript SDK, OneDS JS SDK, and JSLL SDK may have experienced the below errors:
- Browser displays SSL warning/errors in the status bar, and Client telemetry is not sent and is lost
- Customers websites fails to load the requested page and could take end users to their global error page, and Client telemetry is not sent and is lost
- No issues are noticed by end customers, and Client telemetry is not sent and is lost.
We will provide an update in the next 2 hours or as the situation warrants
- Work Around: Customers can configure their sites to pull the JS SDKS from this endpoint: https://js.monitor.azure.com . Be sure to update only the domain portion of the URL.
- Next Update: Before 04/21 20:00 UTC
-Eric Singleton
