%3CLINGO-SUB%20id%3D%22lingo-sub-2101461%22%20slang%3D%22en-US%22%3EExperiencing%20errors%20when%20accessing%20alerts%20in%20Azure%20Monitor%20-%2001%2F27%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2101461%22%20slang%3D%22en-US%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EFinal%20Update%3C%2FU%3E%3A%20Wednesday%2C%2027%20January%202021%2010%3A28%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3E%3CDIV%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2001%2F27%2C%2010%3A00%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2001%2F27%2C%2009%3A15%20UTC%20and%20that%20during%20the%2045%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20of%20customers%20may%20have%20received%20errors%20when%20accessing%20alerts.%20The%20alerts%20notifications%20were%20not%20impacted.%3C%2FDIV%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20We%20determined%20that%20a%20recent%20deployment%20task%20impacted%20instances%20of%20the%20backend%20service%20which%20became%20unhealthy%2C%20causing%20these%20errors.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2045%20minutes%20-%2001%2F27%2C%2009%3A15%20UTC%20through%2001%2F27%2C%2010%3A00%20UTC%3CBR%20%2F%3E%3C%2FLI%3E%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Azure%20Monitor%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Anmol%3CBR%20%2F%3E%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2101461%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EActivity%20Log%20Alerts%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMetric%20Alerts%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESmart%20Diagnostics%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Wednesday, 27 January 2021 10:28 UTC

We've confirmed that all systems are back to normal with no customer impact as of 01/27, 10:00 UTC. Our logs show the incident started on 01/27, 09:15 UTC and that during the 45 minutes that it took to resolve the issue some of customers may have received errors when accessing alerts. The alerts notifications were not impacted.
  • Root Cause: We determined that a recent deployment task impacted instances of the backend service which became unhealthy, causing these errors.
  • Incident Timeline: 45 minutes - 01/27, 09:15 UTC through 01/27, 10:00 UTC
We understand that customers rely on Azure Monitor as a critical service and apologize for any impact this incident caused.

-Anmol