Home
%3CLINGO-SUB%20id%3D%22lingo-sub-463630%22%20slang%3D%22en-US%22%3EDelays%20in%20email%20notifications%20for%20Application%20Insights%20alerts%20-%204%2F16%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-463630%22%20slang%3D%22en-US%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EFinal%20Update%3C%2FU%3E%3A%20Tuesday%2C%2016%20April%202019%2023%3A05%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EStarting%20at%20approximately%204%2F16%2C%2013%3A15%20UTC%20time%2C%20alerting%20email%20notifications%20for%20Application%20Insights%20alerts%20in%20all%20regions%20began%20to%20experience%20increasing%20delays%2C%20with%20latency%20up%20to%20approximately%20two%20hours%20during%20the%20peak%20of%20the%20impact%20window.%26nbsp%3B%20This%20included%20notifications%20for%20both%20Classic%20and%20Near-Real-Time%20alerts%2C%20as%20well%20as%20for%20daily%20cap%20warnings%20%26amp%3B%20availability%20tests.%26nbsp%3B%20Webhooks%20and%20other%20notification%20paths%20were%20not%20impacted.%26nbsp%3B%20%26nbsp%3BWe've%20confirmed%20that%20email%20notification%20latency%20is%20now%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%204%2F16%2C%2022%3A42%20UTC.%26nbsp%3B%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20increased%20load%20in%20a%20dependent%20service.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%204%2F16%2C%2013%3A15%20UTC%20through%204%2F16%2C%2022%3A42%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Application%20Insights%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Matthew%20Cosner%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-463630%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Tuesday, 16 April 2019 23:05 UTC

Starting at approximately 4/16, 13:15 UTC time, alerting email notifications for Application Insights alerts in all regions began to experience increasing delays, with latency up to approximately two hours during the peak of the impact window.  This included notifications for both Classic and Near-Real-Time alerts, as well as for daily cap warnings & availability tests.  Webhooks and other notification paths were not impacted.   We've confirmed that email notification latency is now back to normal with no customer impact as of 4/16, 22:42 UTC. 
  • Root Cause: The failure was due to increased load in a dependent service.
  • Incident Timeline: 4/16, 13:15 UTC through 4/16, 22:42 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Matthew Cosner