What incident.io shipped
Each line links to incident.io's own note; the short summaries are FoxPlug's. Not affiliated with incident.io.
Last 90 days, as of November 21, 2026
incident.io ships more often than 23% of the other 26 dev tools products we track: 21st of 27, at 0.7 entries a week over the days its feed covers. How the rank is worked out.
November 2026
- November 16, 2026 · Is AI just another third-party dependency? Yes, right up until it isn't
October 2026
- October 30, 2026 · What does a commercial analyst actually do?
- October 29, 2026 · Degrade gracefully: designing AI features that keep working when the model doesn't
- October 14, 2026 · We gave cloud agents a phone to QA
- October 6, 2026 · How savepoints quietly throttled our Postgres queue
- October 1, 2026 · Building Investigations: what it takes to build an AI SRE
September 2026
- September 22, 2026 · Almost excited to get paged
- September 2, 2026 · Interning at incident.io: rate limiting, resiliently
August 2026
- August 11, 2026 · We turned off Pub/Sub and nobody noticed
- August 5, 2026 · Introducing Investigations, powered by Nexus.
- August 3, 2026 · Institutional knowledge doesn't scale: Building an agentic data analyst
July 2026
- July 29, 2026 · Dashboards aren’t (quite) dead
- July 28, 2026 · Fact-checking PagerDuty's Opsgenie alternatives comparison table
- July 21, 2026 · Don't add a read replica until you've read this
- July 9, 2026 · Your genie is vanishing: introducing the Opsgenie rescue program
June 2026
May 2026
- May 28, 2026 · Customers over control: how we measure On-call reliability
- May 19, 2026 · Engineering teams in 2027
- May 13, 2026 · incident.io launches PagerDuty Rescue Program
- May 11, 2026 · Humans aren’t fast enough for 4 9’s
April 2026
- April 28, 2026 · Who's on call? How we improved schedule rendering performance 2,500x
- April 23, 2026 · What does using AI for post-mortems actually mean?
- April 23, 2026 · How it feels to run an incident with Investigations
- April 16, 2026 · Why post-mortem action items die
- April 13, 2026 · What to do when OpsGenie sunsets
March 2026
- March 20, 2026 · How to migrate your paging tool without breaking your team
- March 18, 2026 · How Catalog changes the game for long-term maintenance
- March 17, 2026 · We rebuilt our post-mortems from the ground up
- March 4, 2026 · The post-mortem problem
February 2026
- February 26, 2026 · Keeping it boring: the incident.io technology stack
- February 24, 2026 · Secure access at the speed of incident response
- February 1, 2026 · Everything you need to know about ITIL 5, AI and incident management
December 2025
- December 19, 2025 · DevEx matters for coding agents, too
- December 1, 2025 · Stop choosing between fast incident response and secure access
November 2025
- November 20, 2025 · AWS re:Invent 2025: The top sessions SREs should attend
- November 14, 2025 · Bloom filters: the niche trick behind a 16× faster API
- November 13, 2025 · Recapping SEV0 London 2025
- November 10, 2025 · Weaving AI into the fabric of incident.io
Ship updates like these to your users
incident.io keeps a public record of what it ships. FoxPlug gives your product the same: a changelog page, an in-app widget and release posts, all from one place.
See FoxPlugSee a live changelog and widgetYour changelog, written for you
FoxPlug writes your changelog from your releases and commits in plain English and publishes it as a page and a feed your users can follow. The page above shows what that looks like for a product people really use.
Write my changelog See the changelog FoxPlug wrote from its own commits
Free to start. Pro is a month.
FoxPlug Pro
- A public changelog page and feed for each project
- Written from your releases and commits, in plain English your users read
- Connect GitHub and new releases become new entries