After weeks of embarrassing outages, migration deadlines, carrier failures, and machine-traffic spikes, the most compelling service management story right now isn't any single incident. It's how ownership’s evolving.
What kept jumping out at me as I worked through this week’s updates was how often the customer-facing failure sat between systems rather than perfectly inside one of them. That makes this less a list of incidents than a week about who can actually see, own, and explain the whole delivery path.
Customer journeys now cross cloud platforms, carrier networks, third-party APIs and autonomous agents, while status pages and operating teams still tend to stop at organizational boundaries. You can see that in every story in this roundup.
Cloudflare and Fastly are redesigning infrastructure for machine traffic. Twilio's carrier board shows why an operational platform can still sit above a broken customer journey. GitHub is showing what useful incident accountability looks like.
Atlassian is moving Opsgenie customers while changing the Jira Service Management destination underneath them. New Relic, Dynatrace, ServiceNow, NVIDIA, Microsoft, and Atlassian are all, from different angles, turning agent observability and containment into production operations.
For CX leaders, 'is the service up?' is becoming the wrong first question. The more pressing test is whether you can see the full delivery path, work out who owns the break, and explain what changes next.
TL;DR:
-
Machine traffic is now operational traffic. Cloudflare and Fastly are giving agents dedicated controls, APIs, and runtime visibility. Cloudflare’s new Issues feature now pushes production failures and diagnostic context into agent or on-call workflows too.
-
Reliability still breaks at the handoff. Twilio's carrier incidents show why platform uptime doesn't equal journey uptime. Microsoft’s September 30 Azure gateway incident put the same problem into cloud connectivity.
-
Migration and incident transparency matter together. Opsgenie's 2027 deadline arrives while JSM changes, and GitHub's RCAs show what buyers should demand when systems fail.
-
Agent observability is turning into agent control. New Relic and Dynatrace are measuring the problem; ServiceNow and NVIDIA are moving toward containment, while Microsoft and Atlassian are building governance into execution itself.
What Was Announced During Cloudflare Birthday Week 2026?
Cloudflare Birthday Week 2026 spent a lot of time on machines behaving like internet users. In its September 27 founders’ letter, Cloudflare said automated traffic had already overtaken human traffic on its network in May, beating its own late-2027 prediction by well over a year.
“The Internet is changing more today than at any point since Cloudflare launched back on September 27, 2010.”
Cloudflare threw another big number into the mix during the week: daily AI-agent requests were up more than 1,700% in a year. Traffic growing that fast can’t be filed away as a bot-policy issue. It’s something capacity teams, network teams, and service managers have to plan around.
Cloudflare’s also giving those agents more operational reach. Its new cf agentic CLI covers more than 3,000 API operations, letting agents deploy Workers, monitor infrastructure and configure services. Agents had already risen from 25% of Wrangler usage in March to 48% shortly before launch.
There was another announcement in the form of “Issues” too, which groups Worker exceptions and 5xx responses with the telemetry needed to investigate them. Cloudflare says Issues uncovered two previously obscured Workflows bugs within a day of internal use.
That makes Ruth Kirby’s point from one of our webinars especially relevant:
“I can see exactly what’s going on in real time and my information is being updated in real time.”
Cloudflare pushed that idea further on October 2. Traces can now follow an individual request through security rules, caching, routing, Workers, and the origin, giving teams something much closer to the path a customer actually experiences.
There was a connectivity move as well. Cloudflare and Deutsche Telekom are directly interconnecting their networks, with both companies talking up stronger end-to-end resilience.
For me, that’s the useful Birthday Week takeaway: more machine traffic means more places for a customer journey to break, and more pressure to see the whole route when it does.
The Opsgenie Sunset: What Should Customers Do Before April 2027
The Opsgenie sunset is getting harder to treat as a problem for next year. On September 14, Opsgenie and Jira Service Management were hit for around 100 minutes, with alerts delayed by an average of 22 minutes. Atlassian blamed a configuration change that set off redundant calls, rate limiting, and retries until worker threads were exhausted.
Customers have until April 5, 2027, to move. After that, Opsgenie becomes inaccessible and unmigrated data is deleted. Atlassian’s in-app migration tool moves customers into Atlassian Cloud, rather than Jira Service Management Data Center.
There’s plenty of competition for those customers. PagerDuty is pushing more incident work into Slack, while incident.io says changes to Investigations cut the median time to an accurate incident-channel update from 6.7 minutes to three.
That’s why I’d test the ugly part of the migration first. Do alerts still arrive under pressure? Do escalation rules behave properly? Does somebody actually get paged?
Atlassian is already rolling out circuit breakers designed to keep alert creation, notifications, and on-call schedules working when JSM search is unhealthy. RovoOps is also moving into Slack incident and alert channels.
Then came October 1. A JSM incident delayed email-to-ticket processing and notifications, while some new support tickets temporarily lost their SLA component. Atlassian said response times and backlog management could be affected.
At Team ’26 Europe, Atlassian is also previewing Proactive Service Management, including silent fixes, employee-approved remediation and Rovo Desktop.
The destination is getting smarter while customers move toward it. That makes early failure testing more important, not less.
Why Is AI Traffic Growth Becoming a Customer Experience Issue?
Fastly’s latest network data gives the agent-traffic story some useful scale. Machine-generated requests accounted for more than half of traffic on its network in July and August, while AI requests grew around 6.5x faster than human traffic from January to May.
The more revealing number is where those requests go. Fewer than 9% of human requests reach origin infrastructure, compared with more than 51% of automated AI traffic. Agents are looking for live prices, availability and account information, so they’re reaching much deeper into the APIs and systems behind the customer experience.
Fastly’s response includes AI Runtime Control, AI Firewall and expanded API Security. As Chief Product Officer Kelly Shortridge put it:
“To effectively adopt coding agents and implement AI features without losing velocity or eroding existing business resilience, enterprises need control in production, at runtime.”
Cloudflare is seeing the same shift, while Akamai and MuleSoft are extending governance across APIs, agents and MCP servers. The common problem is fairly practical: infrastructure built around people making requests now has software making them continuously.
Fastly made that point more tangible on September 28. Comcast and Fastly are putting Fastly delivery software inside Comcast’s distributed network for high-demand Peacock live events, bringing capacity closer to viewers when millions arrive at once.
That’s why this matters beyond infrastructure teams. Customers increasingly arrive through agents, while the services answering them still depend on APIs, origins, and network paths that can buckle under very different traffic patterns.
Why Do Carrier Problems Break Messaging When Twilio Is Up?
Twilio’s September status board gave us a useful reminder that platform uptime and customer experience aren’t the same thing.
At the start of October, Twilio was carrying AT&T US SMS emergency maintenance, UK carrier maintenance affecting APIs such as SIM Swap and Silent Network Auth, and delayed SMS delivery receipts for CTBC subscribers in Brazil.
Several incidents sat under External Connectivity rather than Twilio Services. That distinction helps operators work out where the fault sits. It means very little to somebody still waiting for a verification code, appointment reminder, or callback.
The same pattern was showing up elsewhere. Sinch was investigating delayed messages and missing delivery receipts on Ooredoo Qatar, while Infobip recorded temporary SMS degradation across Spanish networks. CPaaS platforms still depend on carrier routes, interconnects and regional networks that sit outside the neat boundary of the platform itself.
That makes Twilio’s wider 2026 strategy interesting. The company is putting more emphasis on conversation quality, Branded Calling and performance monitoring. The harder question is how far that visibility can follow the journey once traffic leaves Twilio.