Top all-time · #1370
The incident.io Blog
Company blog · incident.io/blogstartupsprogrammingproductivity
The incident.io Blog is the company blog at incident.io, writing about startups, programming and productivity. Since 2021, 52 different Hacker News readers have linked it 135 times, most often “Tracking developer build times to decide if the M3 MacBook is worth upgrading”. It is still writing: the last post was on 2026-10-30, and you can follow it by feed.
Too few sampled comments (20) to say how often HN recommends it.?
Why HN links it
HN readers link the incident.io blog for its engineering and operations posts, including on-call practice, incident management guides, data stack write-ups, build-time measurements, and product engineering.
Summarised by Claude from a sample of 20 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
incident.io is a software reliability platform unifying on-call, agentic root cause analysis, incident response, and status pages – helping teams resolve issues faster.
Most-linked posts?
- Tracking developer build times to decide if the M3 MacBook is worth upgrading7 people · 7 mentions · first linked 2023-12-19
- Bloom filters: the niche trick behind a 16× faster API6 people · 7 mentions · first linked 2025-11-16
- /3 people · 3 mentions · first linked 2021-11-09
- Handling third-party provider outages3 people · 3 mentions · first linked 2022-06-30
- Don't count your incidents, make your incidents count3 people · 3 mentions · first linked 2021-06-18
- Keep the Monolith, but Split the Workloads3 people · 3 mentions · first linked 2023-04-19
- Learning from Incidents – Formula 13 people · 3 mentions · first linked 2021-07-28
- incident.io – create, resolve and manage incidents directly in Slack3 people · 3 mentions · first linked 2021-01-20
- Incidents Are for Everyone2 people · 3 mentions · first linked 2021-06-23
- Write-up of a project to reduce pager load2 people · 2 mentions · first linked 2022-04-22
What Hacker News says?
Fun one: https://incident.io/blog/festive-macbooks
Comment linking /blog/festive-macbooks
on “Apple M5 chip”Submitted Tracking developer build times to decide if the M3 MacBook is worth upgrading as a story · 653 points
HN discussionA lot of the graphs near the end comparing side-to-side had different scales on the Y axis. Take results with a grain of salt. https://incident.io/_next/image?url=https%3A%2F%2Fcdn.sanity...
on “Tracking developer build times to decide if the M3 MacBook is worth upgrading”Submitted Postgres sequences can skip 32 unexpectedly as a story · 134 points
HN discussionCool idea. I thought I’d try to make a Kagi Lens to accomplish the same thing: https://kagi.com/lenses/LdYine8hZtYmrt8yTMngOUtvTM9rmkRy Kagi Lenses can be defined in many ways, one of which is specifying URLs to search. Unfortunately you can only provide 10 URLs per lens. Here are the ones I chose: https://stripe.com/blog/engineering , https://engineering.fb.com/ , https://www.uber.com/en-US/blog/engineering/ , http…
Comment linking /blog
on “Show HN: Engineering.fyi – Search across tech engineering blogs in one place”Submitted A practical guide to incident management as a story · 132 points
HN discussionBiased as I work for them but I think https://incident.io/blog/engineering is definitely worth adding.
Comment linking /blog/engineering
on “Show HN: Engineering.fyi – Search across tech engineering blogs in one place”Submitted Logs and tracing: not just for production, local development too as a story · 66 points
HN discussionThere's some nice tooling these days for this. E.g. https://firehydrant.com/ and https://incident.io both make this a faster, more embedded process.
Comment linking /
on “Ask HN: Is GitHub down?”Submitted A modern data stack for startups (2022) as a story · 58 points
HN discussionIt's great to see more competition in this space. Generally speaking, what I miss in these "incident management" products is also an integrated, flawless way to handle incidents when they're happening. I'm talking about: 1. Quickly creating a proper chat 2. Quickly creating an incident document where you can pin chat messages and use it in the post-mortem. Ideally, pinning some graphs that you'd extract from your ob…
Comment linking /
on “Grafana OnCall: an easy-to-use on-call management tool”Submitted Tracking developer build times to decide if the M3 MacBook is worth upgrading as a story · 32 points
HN discussionI think the main problem is that measuring a lot of these things is incredibly hard. The post mentioned laptops and build time and it reminded me of a blog post[1] trying to figure out if it's worth upgrading to m3 macbooks. I encorage you to read the post yourself, but my impression is that the whole project was a huge waste of time. I suspect most attempts to measure impact will end this way. I also think a lot of…
Comment linking /blog/festive-macbooks
on “Don't Be Frupid”Submitted Incidents Are for Everyone as a story · 26 points
HN discussionThis is something we spoke about in https://incident.io/blog/on-call-at-incident-io . Specifically: > On-call payment is not expected to cover any time you spend working outside of hours. If you're paged and end up working in your evening, you should take time off in lieu. We trust you to manage this time yourself. I'll make sure this is added this to the guide. Thanks for the nudge!
Comment linking /blog/on-call-at-incident-io
on “A practical guide to incident management”Submitted The things we find hardest in incident response as a story · 20 points
HN discussion> At incident.io, our engineering team runs on-call Friday-to-Friday, with a 5pm handover. This works great for us: as an engineer coming off the pager you get to finish work nice and early on a Friday and enjoy your evening. [0] [0]: https://incident.io/guide/on-call/compassionate-on-call/ Is this an American thing? 5pm is not “nice and early on a Friday”! 4pm is about what time you should be finishing, and 3pm is…
Comment linking /guide/on-call/compassionate-on-call/
on “A practical guide to incident management”Submitted Designing Your Incident Severities as a story · 17 points
HN discussionHey Hackernews! I work at incident.io, where we’re building an incident management platform that helps your organisation deal with incidents at scale. Today, we’re launching a set of resources intended to help those building their own incident processes that we’re calling the practical guide to incident management. It includes chapters on: - On-call, what it means, who’s involved, and how it should be compensated -…
Comment linking /guide
on “A practical guide to incident management”Submitted Incident.io Raises $62M as a story · 13 points
HN discussionIt would work for most of our business reporting, but BigQuery is so good at what it does and cheap that it doesn't make much sense to avoid it. We also have some parts of our dataset that are complicated to compute. An example is that we estimate the hours that people have spent working on incidents, with a method that we describe here: https://incident.io/guide/insights/workload That requires us to do some expensi…
Comment linking /guide/insights/workload
on “A modern data stack for startups (2022)”Submitted We turned off Pub/Sub and nobody noticed as a story · 10 points
HN discussionWe do very similar things ourselves: our insights product ( https://incident.io/learn ) uses Metabase to power the dashboards. The data that goes into those insights can be quite complex and the queries are actually threading JSON parameters through into BigQuery SQL queries using JavaScript UDFs to power the filters in the dashboard (show incidents with these custom field values). This works pretty well with signed…
Comment linking /learn
on “A modern data stack for startups (2022)”Submitted Don't add a read replica until you've read this as a story · 10 points
HN discussionThis is an article from Jan 2022 when we were a company of 10, and now are a company of ~80. Worth some observations that: - We're still using Fivetran for the EL stages. Costs are much more significant than they were before and we're looking (for the high volume sources) into options like DataStream as cost savers, but it's not unmanageable. - dbt is still working great, even if we've done a lot of investment havin…
Comment linking /blog/updated-data-stack
on “A modern data stack for startups (2022)”Submitted Bloom filters: the niche trick behind a 16× faster API as a story · 7 points
HN discussionInteresting Pricing strategy (for Incident.io) Plan A: $16 (month/user) Plan B: $10,000+ Call Us Plan C: Call Us Those are some of the steepest price cliffs I’ve ever come across. https://incident.io/pricing#plan-comparison
Comment linking /pricing
on “A modern data stack for startups (2022)”Submitted incident.io – create, resolve and manage incidents directly in Slack as a story · 7 points
HN discussionI'm one of the engineers at incident.io, so thanks for the mention! But yes, when we first started the majority of our customers bought us for incident management and used PagerDuty as their on-call provider (phones them, receives the alerts, hands-off to us when an incident starts). We've since built on-call directly into our product and we've had loads of those customers migrate entirely into us, dropping PagerDut…
Comment linking /customers/intercom
on “What do people use for on-call these days?”Submitted Observability as a Superpower as a story · 6 points
HN discussion
