%3CLINGO-SUB%20id%3D%22lingo-sub-1825669%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20issue%20in%20Azure%20Portal%20for%20Many%20Data%20Types%20-%2010%2F28%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1825669%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%3C%2FDIV%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%3EUpdate%3C%2FU%3E%3A%20Wednesday%2C%2028%20October%202020%2001%3A19%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3E%3CDIV%20style%3D%22font-family%3A%20%22%20segoe%3D%22%22%20ui%3D%22%22%3E%3CDIV%20style%3D%22font-family%3A%20SegoeUI%2C%20Lato%2C%20%22%20helvetica%3D%22%22%20neue%3D%22%22%3E%3CP%20style%3D%22margin-bottom%3A%200px%3B%22%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20to%20query%20data%20as%20of%2010%2F27%2C%201%3CSPAN%20style%3D%22color%3A%20rgb(0%2C%200%2C%200)%3B%20font-family%3A%20%22%20helvetica%3D%22%22%20neue%3D%22%22%3E7%3A58%20PST%3C%2FSPAN%3E%26nbsp%3Bto%2019%3A20%20PST.%20Our%20logs%20show%20the%20incident%20started%20on%2010%2F27%2C%201%3CSPAN%20style%3D%22color%3A%20rgb(0%2C%200%2C%200)%3B%20font-family%3A%20%22%20helvetica%3D%22%22%20neue%3D%22%22%3E7%3A58%20PST%3C%2FSPAN%3E%26nbsp%3Band%20that%20during%20the%201%20hours%20and%2021%20mins%20that%20it%20took%20to%20resolve%20the%20issue%203%25%20of%20customers%20experienced%20Data%20access%20issues%20or%20delayed%2Fmissed%20Log%20Search%20alerts%20for%20resources%20hosted%20in%20PRODWUS2.%3CBR%20%2F%3E%3C%2FP%3E%3CP%20style%3D%22margin-bottom%3A%200px%3B%22%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%20style%3D%22margin-bottom%3A%200px%3B%22%3E%3C%2FP%3E%3CUL%20style%3D%22margin-bottom%3A%2012px%3B%20padding-left%3A%202.5em%3B%20list-style%3A%20outside%3B%20clear%3A%20left%3B%22%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20instances%20of%20a%20backend%20service%20became%20unhealthy%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2010%2F27%2C1%3CSPAN%20style%3D%22color%3A%20rgb(0%2C%200%2C%200)%3B%20font-family%3A%20%22%20helvetica%3D%22%22%20neue%3D%22%22%3E7%3A58%20PST%3C%2FSPAN%3E%26nbsp%3Bthrough%2019%3A20%20UTC%3CBR%20%2F%3E%3C%2FLI%3E%3C%2FUL%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E-Arish%20B%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-1825669%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Update: Wednesday, 28 October 2020 01:19 UTC

We've confirmed that all systems are back to normal with no customer impact to query data as of 10/27, 17:58 PST to 19:20 PST. Our logs show the incident started on 10/27, 17:58 PST and that during the 1 hours and 21 mins that it took to resolve the issue 3% of customers experienced Data access issues or delayed/missed Log Search alerts for resources hosted in PRODWUS2.


  • Root Cause: The failure was due to instances of a backend service became unhealthy
  • Incident Timeline: 10/27,17:58 PST through 19:20 UTC
-Arish B