Operations | Monitoring | ITSM | DevOps | Cloud

After-hours calls can create missed messages and send urgent issues to the wrong clinician. For private medical practices, that risk grows when call answering and on-call escalation rely on the same loosely defined workflow. Answering service receives an inbound call, captures information, and categorizes the request. On-call routing identifies the responsible clinician, delivers the message, and escalates it when the clinician does not respond.

At incident.io we are huge fans of Postgres; we've written about it a lot over the years, including how to choose the right indexes and how we're proud of being boring (The Pet Shop Boys). We use Postgres as our primary transactional database, which as of today has ~900 tables, and counting! The vast majority of our codebase does something along the following lines: read some data from Postgres, execute some business logic, then write that data back to Postgres. It is not, however, always that simple.

ilert AI SRE is now generally available. Alongside it, this quarter brings Compass, a lifecycle assistant that surfaces the next move during an incident, a dedicated space for postmortems, rich incident cards in Microsoft Teams and Google Chat, on-call schedules that follow support hours and holidays, a new CLI, and dark mode. Here's everything that shipped.

Railway-hosted domains returned HTTP 404 to new connections in all four Railway regions on September 30, 2026, for about five minutes between roughly 07:35 and 07:40 UTC. This happened after a new version of Railway's routing service went live before the database schema change it depended on had been applied.

Here’s everything you need to know about incident management.

At incident.io, we've spent the last two years building Investigations, our AI SRE. When you get paged, it starts investigating straight away, looking across your telemetry, recent deploys, past incidents, docs and code, and posts what it's found in your incident channel (or on your phone, if it's 2am and you're still deciding whether you need to get out of bed). By the time you open your laptop, you're starting at step six of triage rather than step one.

Managing a growing IT environment requires more than reacting to problems as they appear. IT teams and managed service providers (MSPs) need continuous visibility into endpoints, servers, networks and other infrastructure so they can identify potential issues, perform maintenance and resolve problems remotely. That is where remote monitoring and management (RMM) software comes in. RMM tools provide IT teams with a centralized way to monitor and manage distributed IT environments.