Service tokens “allow automated services to authenticate to other services,” Cloudflare said in its detailed post-incident report : Cloudflare disruption as seen through ThousandEyes Internet Insights On January 24, less than 24 hours before the Microsoft incident, around 4:55 PM UTC, several Cloudflare services experienced two hours of downtime after a code deployment accidentally overwrote some service token metadata before it was recognized and rolled back.įigure 2. We also observed similar incidents at both Cloudflare and Slack. We ended our last installment of the Weekly Pulse with the network configuration change by Microsoft on January 25 that caused application reachability issues globally.īut it wasn’t the only incident caused by a configuration change to occur in that timeframe.
U.S.-centric outages accounted for 30% of all observed outages, which is larger than the percentage observed on January 16-22 and January 23-29, where they accounted for 26% of observed outages. This was followed by a drop from 117 to 73, a 38% decrease compared to the previous week. 
This pattern was not reflected domestically, initially rising from 102 to 117, a 15% increase when compared to January 23-29. This downward trend continued with global outages dropping from 331 to 301, a 9% decrease compared to the previous week. 
Global outages trended down, dropping initially from 373 to 331, an 11% decrease when compared to January 23-29. Before we dive into this week's highlights, we take a look at some of the global trends we observed across ISPs, cloud service provider networks, collaboration app networks, and edge networks over the past two weeks (January 30-February 13):
0 kommentar(er)
