%3CLINGO-SUB%20id%3D%22lingo-sub-1449777%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Latency%20in%20Azure%20portal%20for%20Activity%20Log%20Alerts%20-%2006%2F08%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1449777%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%3CU%3EFinal%20Update%3C%2FU%3E%3A%20Tuesday%2C%2009%20June%202020%2000%3A59%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20style%3D%22color%3A%20rgb(51%2C%2051%2C%2051)%3B%20font-family%3A%20SegoeUI%2C%20Lato%2C%20%26quot%3BHelvetica%20Neue%26quot%3B%2C%20Helvetica%2C%20Arial%2C%20sans-serif%3B%22%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%206%2F9%2C%2000%3A30%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%206%2F8%2C%2021%3A15%20UTC%20and%20that%20during%20the%203%20hours%20and%2015%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20customers%20experienced%20delayed%20Activity%20Log%20alerts%20by%20up%20to%203.5%20hours%3C%2FSPAN%3E.%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%26nbsp%3B%3CSPAN%20style%3D%22color%3A%20rgb(51%2C%2051%2C%2051)%3B%20font-family%3A%20SegoeUI%2C%20Lato%2C%20%26quot%3BHelvetica%20Neue%26quot%3B%2C%20Helvetica%2C%20Arial%2C%20sans-serif%3B%22%3EThe%20failure%20was%20due%20to%20the%20service%20reaching%20an%20operating%20limit%20as%20a%20result%20of%20large%20unexpected%20spike%20in%20alert%20notifications%20across%20regions%3C%2FSPAN%3E.%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%203%20Hours%20%26amp%3B%2015%20minutes%20-%206%2F8%2C%2021%3A15%20UTC%20through%206%2F9%2C%2000%3A30%20UTC%3C%2FLI%3E%0A%3C%2FUL%3E%3CSPAN%20style%3D%22color%3A%20rgb(51%2C%2051%2C%2051)%3B%20font-family%3A%20SegoeUI%2C%20Lato%2C%20%26quot%3BHelvetica%20Neue%26quot%3B%2C%20Helvetica%2C%20Arial%2C%20sans-serif%3B%22%3EWe%20understand%20that%20customers%20rely%20on%20Activity%20Log%20Alerts%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E-Subhash%3CBR%20%2F%3E%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EInitial%20Update%3C%2FU%3E%3A%20Monday%2C%2008%20June%202020%2023%3A49%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Activity%20Log%20Alerts%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20delayed%20alerts.%20Alerts%20will%20eventually%20fire.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%3CNONE%20or%3D%22%22%20details%3D%22%22%3E%3C%2FNONE%3E%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2006%2F09%2004%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Subhash%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1449777%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EActivity%20Log%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Tuesday, 09 June 2020 00:59 UTC

We've confirmed that all systems are back to normal with no customer impact as of 6/9, 00:30 UTC. Our logs show the incident started on 6/8, 21:15 UTC and that during the 3 hours and 15 minutes that it took to resolve the issue customers experienced delayed Activity Log alerts by up to 3.5 hours.
  • Root CauseThe failure was due to the service reaching an operating limit as a result of large unexpected spike in alert notifications across regions.
  • Incident Timeline: 3 Hours & 15 minutes - 6/8, 21:15 UTC through 6/9, 00:30 UTC
We understand that customers rely on Activity Log Alerts as a critical service and apologize for any impact this incident caused

-Subhash

Initial Update: Monday, 08 June 2020 23:49 UTC

We are aware of issues within Activity Log Alerts and are actively investigating. Some customers may experience delayed alerts. Alerts will eventually fire.
  • Work Around:
  • Next Update: Before 06/09 04:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Subhash