Earlier this year, we shipped a number of changes to make it faster to calculate who's on call.
We cut our CPU usage by 50% with some simple changes, but struggled to make a meaningful difference until we gave it to Opus 4.6 🧵 (1/7)
Writing a post-mortem shouldn’t require a memory test.
Our new post-mortem editor puts incident context and built-in AI right where you’re writing, so the story comes together without the tab shuffle.
See what other features we've added: go.incident.io/bDkof50
FFS. 30 mins of debugging why the code that was working last night now doesn't work this morning, and it turns out ServiceNow hibernated my dev instance.
Truly a joy to develop with SNow.
If you're having a peaceful night of on-call and happen to see this, you might want to go and check your alerting systems.
There's a PagerDuty incident ongoing for over an hour, and impacting notification delivery.
@picnic is an online supermarket on a mission to make grocery shopping simple, fun, and affordable. And they're clearly a company with great taste, choosing @incident_io to help them achieve their high bar for reliability.
“We are now moving to a level where we are building up structural technical resilience, meaning whenever there's an incident happening, there's no longer customers affected, and that is basically the ultimate goal that we are striving for.”