Final Update: Thursday, 29 March 2018 11:42 UTC
We've confirmed that all systems are back to normal with no customer impact as of 03/29, 11:40 UTC. Our logs show the incident started on 03/29, 07:15 UTC and that during the 4 hours 25 minutes that it took to resolve the issue 79 customers who have signed for standalone tier plan would have experienced restriction of 512MB daily quota limit.
We've confirmed that all systems are back to normal with no customer impact as of 03/29, 11:40 UTC. Our logs show the incident started on 03/29, 07:15 UTC and that during the 4 hours 25 minutes that it took to resolve the issue 79 customers who have signed for standalone tier plan would have experienced restriction of 512MB daily quota limit.
- Root Cause: The failure was due
to an issue in one of our dependent platform services. - Incident Timeline: 4 Hours & 25 minutes - 03/29, 07:15 UTC through 03/29, 11:40 UTC
We understand that customers rely on Log Analytics as a critical service and apologize for any impact this incident caused.
-Mohini
Update: Thursday, 29 March 2018 10:21 UTC
We are investigating daily quota limit issue within OMS Portal. Root cause is not fully understood at this time. There are 79 customers who are signed for standalone tier continue to experience restriction of 512 MB daily quota limit. We are working to establish the start time for the issue, initial findings indicate that the problem began at 03/29 ~07:15 UTC.
We are investigating daily quota limit issue within OMS Portal. Root cause is not fully understood at this time. There are 79 customers who are signed for standalone tier continue to experience restriction of 512 MB daily quota limit. We are working to establish the start time for the issue, initial findings indicate that the problem began at 03/29 ~07:15 UTC.
- Work Around: None
- Next Update: Before 03/29 12:30 UTC
-Mohini