%3CLINGO-SUB%20id%3D%22lingo-sub-1364623%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Service%20Map%20-%2005%2F06%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1364623%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%3CU%3EFinal%20Update%3C%2FU%3E%3A%20Wednesday%2C%2006%20May%202020%2018%3A11%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2005%2F06%2C%2017%3A44%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2005%2F06%2C%2016%3A14%20UTC%20and%20that%20during%20the%201%20hour%20and%2030%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20of%20customers%20in%20East%20US%20region%20might%20have%20experienced%20Data%20Access%20issue%20for%20Service%20Map.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20an%20issue%20in%20one%20of%20our%20dependent%20services.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20hour%20and%2030%20minutes%20-%2005%2F06%2C%2016%3A14%20UTC%20through%2005%2F06%2C%2017%3A44%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Service%20Map%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Saika%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%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%2006%20May%202020%2017%3A29%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20investigating%20issues%20within%20Service%20Map.%20Some%20customers%20continue%20to%20experience%20Data%20Access%20issue%20in%20East%20US.%20We%20are%20working%20to%20establish%20the%20start%20time%20for%20the%20issue%2C%20initial%20findings%20indicate%20that%20the%20problem%20began%20at%2005%2F06%20~16%3A14%20UTC.%20We%20currently%20have%20no%20estimate%20for%20resolution.%3CUL%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2005%2F06%2020%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3E-Saika%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%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1364623%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EService%20Map%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Wednesday, 06 May 2020 18:11 UTC

We've confirmed that all systems are back to normal with no customer impact as of 05/06, 17:44 UTC. Our logs show the incident started on 05/06, 16:14 UTC and that during the 1 hour and 30 minutes that it took to resolve the issue some of customers in East US region might have experienced Data Access issue for Service Map.
  • Root Cause: The failure was due to an issue in one of our dependent services.
  • Incident Timeline: 1 hour and 30 minutes - 05/06, 16:14 UTC through 05/06, 17:44 UTC
We understand that customers rely on Service Map as a critical service and apologize for any impact this incident caused.

-Saika

Update: Wednesday, 06 May 2020 17:29 UTC

We are investigating issues within Service Map. Some customers continue to experience Data Access issue in East US. We are working to establish the start time for the issue, initial findings indicate that the problem began at 05/06 ~16:14 UTC. We currently have no estimate for resolution.
  • Next Update: Before 05/06 20:30 UTC
-Saika