Automate Incident Intake and Start Response in Seconds | Harness Blog
Manual intake eats the first 10 to 30 minutes of an incident. Harness AI SRE runs it as automation and gives those minutes back to your responders.
Operations | Monitoring | ITSM | DevOps | Cloud
The Place Where Modern Operations & Technology Come Together
The latest News and Information on Incident Management, On-Call, Incident Response and related technologies.
Stop Chasing Field Technicians - Track Work Progress with One-Tap Status Updates
Field service managers need visibility into more than just whether a technician has arrived. They need to know when work begins, when it’s completed, and when the technician is heading to the next job. Without a simple, consistent way to communicate these milestones, dispatchers and supervisors are left making phone calls and sending text messages just to find out what’s happening. Most of the time, nothing is wrong.
Incident Communication Lessons From Spotify Outages
Good incident communication is the difference between an outage your users forgive and an outage that quietly pushes them toward a competitor. That lesson landed hard in late July 2026, when Gergely Orosz of The Pragmatic Engineer publicly walked away from publishing video podcasts on Spotify after a run of reliability failures. The bug that broke publishing was almost beside the point.
From Incident Data to Operational Knowledge: A Safer Role for Generative AI in IT Ops
IT operations teams produce an enormous amount of information. Alerts, logs, incident messages, deployment records, support tickets, runbooks and post-incident reviews all contain operational knowledge. The problem is that much of this knowledge remains fragmented and difficult to reuse. Generative artificial intelligence can help organise and transform this information, but its safest role is not unrestricted control over production infrastructure. Its strongest initial use cases involve reading, summarising, classifying and drafting information for an engineer to review.
Alert Fatigue Is Now a Reliability Risk in 2026
Two big reliability surveys landed in 2026, and together they deliver an uncomfortable verdict: alert fatigue has stopped being a morale complaint and turned into a measurable production risk. Engineers are drowning in signals, most of which mean nothing, and the noise is now directly causing outages.
AI-Related Outages Are Reshaping On-Call in 2026
AI-related outages just moved from a fringe worry to a mainline reliability problem, and the on-call rotation is where that shift lands first. A new StackGen analysis of nearly 178,000 public status-page records found that incidents disclosed by AI model and AI application companies now account for more than one in ten reported outages, a sixfold jump from 1.7 percent in 2023 to 10.7 percent so far in 2026.
AI-Generated Code Incidents Are Breaking On-Call
The story of 2026 engineering has a plot twist that on-call teams saw coming. AI coding assistants now write a large share of production code, pull requests per developer are up, and delivery velocity looks great on the dashboard. Then the pager goes off.
The August 6, 2026 GitHub Actions Outage: Queued Jobs, Throttled Webhooks, Impact Lasting 10 Hours
On August 6, 2026, GitHub opened an incident for degraded Actions performance at 15:22 UTC. Within about twenty minutes, Actions availability was listed as degraded, workflow runs were failing to start or failing partway through, and the Actions REST API was returning errors. Pages was pulled into the same incident shortly afterwards. The status page marked Actions and Pages as mitigated at 00:05 UTC on August 7, and closed the incident at 02:04 UTC.
PagerDuty External Status Pages
Keep your users and customers informed about the health of your services with PagerDuty External Status Pages.
PagerDuty Status Update Templates
Status Update Templates give your team control over how status updates are sent to stakeholders and what information is included. Customize your templates for different audiences and different types of incidents using the templating language Liquid.