Final Update: Thursday, February 8th 2018 06:07 UTC
We’ve confirmed that all systems are back to normal as of 2018-02-08 05:30 UTC. Our logs indicates that failures started on 2018-02-07 19:30 UTC .We have an understanding of what caused this issue and have taken steps to prevent recurrence. Sorry for any inconvenience this may have caused.
- Root Cause: There were invalid entries left over after a deployment was rolled back in one of the config table which is used by service for lookup. Deleting these invalid entries mitigated the issue.
- Chance of Re-occurrence: Low
- Incident Timeline: 9 hours – 2018-02-07 19:30 UTC through 2018-02-08 05:30 AM UTC.
Initial Update: Thursday, February 8th 2018 04:28 UTC
We're investigating an issue with Packaging service in South Brazil. We were alerted by our monitor of a possible issue in South Brazil for packaging. Users may see an error message "Invalid URI: The hostname could not be parsed" while accessing their accounts.
- Next Update: Before Thursday, February 8th 2018 06:00 UTC
This post first appeared on MSDN Blogs | Get The Latest Information, Insights, Announcements, And News From Microsoft Experts And Developers In The MSDN Blogs., please read the originial post: here