Blog

Postmortems on our own infrastructure, how the product works under the hood, and what shipped this month.

EngineeringNov 18, 2026Stitching Outages Across MidnightA monitor's 90-day history needs more than uptime per day: it needs every outage, when it started and how long it lasted, including the ones that run past midnight. Summarising that per day without losing a single outage took the query from 866 ms to 40 ms, and we checked it against 392 real outages before trusting it.Watchdock Engineering · 6 min read
EngineeringNov 18, 2026Thirty Days of Uptime in 28 MillisecondsThe home screen of our mobile app waited on one request that took up to 27 seconds on a cold cache, because it counted every raw check result from the last 30 days on every load. Summarising each finished day once brought the same query to 201 ms cold and 28 ms warm.EngineeringNov 11, 2026Profiling Our Servers API After a Chart Came Back EmptyA server drawer showed an empty 24 hour chart while every server was up. The data was there; the response was 426 KB and missed the browser's timeout. Profiling the rest of the page turned up a serializer rebuilding itself on every row, three bugs hidden by one `except Exception`, and a 3 second scan behind a list of ten incidents.EngineeringNov 9, 2026Fixing the N+1 Queries Behind Our Docker Containers PageOur new containers page made five requests and two hundred database queries every time it loaded, and dropped every container past the hundredth without saying so. One endpoint shaped for the page, two missing joins, an hourly cache and one index brought it to two requests and seven queries, with every row present.EngineeringNov 6, 2026When We Choose Consistency Over AvailabilityWatchDock acts on things it doesn't own: your servers, your GitHub repository, your payment provider. Each of those actions has its state in two places, and this is how we decide when to refuse an operation rather than tell you something that isn't true.EngineeringNov 4, 2026Profiling a Postgres CPU Spike in Our Django AppOur own Postgres was spiking past 240% CPU while handling a few requests a second. Cleaning out 76 GB of telemetry, one missing index on a JSON key, and three small Django settings brought CPU down by about 60% and disk reads by 98%.
One email when we publish. Nothing else.Postmortems and engineering notes, roughly twice a month.