Many users connecting to these services at that time would have experienced HTTP and DNS timeouts. This observed packet loss translated directly into service degradation. Outage affecting large numbers of Microsoft network interfaces. Spike in Microsoft service outages, as seen through ThousandEyes Internet Insights.ĭuring the incident, ThousandEyes observed high levels of packet loss as Microsoft and other services became unavailable due to connectivity disruptions at and around Microsoft’s network (as seen in figure 2). During the incident, ThousandEyes saw changes in traffic distribution via DNS that may have indicated steps to steer traffic away from impacted areas within Microsoft’s network.īeginning at approximately 7:05 AM UTC, Microsoft experienced a significant global disruption that impacted connectivity to many of its services, including Azure, Teams, Outlook, and Sharepoint (see figure 1).The bulk of the incident lasted approximately 90 minutes, although residual connectivity issues were observed into the following day.The disruption was triggered by an external BGP change by Microsoft that impacted connected service providers, leading to destabilization of global routes to its prefixes, which led to significant packet loss and diminished reachability of its services and those of its customers.The following analysis of Microsoft’s service disruption on January 25, 2023, is based on our extensive monitoring, as well as ThousandEyes’ global outage detection service, Internet Insights. ThousandEyes actively monitors the reachability and performance of thousands of services and networks across the global Internet, which we use to analyze outages and other incidents. See how the outage unfolded in this rolling analysis as more updates will be added as we have them. At around 7:05 AM UTC on January 25, 2023, Microsoft started experiencing service related issues.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |