ASArtem Senenkoinuptimepage.hashnode.dev·11h ago · 8 min readHow to write incident status updates that build trustTL;DR. During an outage your status page has a second job: holding trust while the fix is still in progress. Write plainly. Say what customers feel first, say what you are doing, and promise a time fo00
ASArtem Senenkoinuptimepage.hashnode.dev·1d ago · 5 min readWhy I chose Rust over Go for an uptime monitorOriginally published on the Uptimepage blog. I build the thing in Rust, so this is the answer I give when people ask why not Go. I build Uptimepage, an open-source uptime monitor and status page writt00
ASArtem Senenkoinuptimepage.hashnode.dev·4d ago · 5 min readIs 98% uptime good? It allows 7.3 days of downtime a yearI build an uptime monitor, so this question lands in my inbox a lot: is 98% uptime good? For a public website or a paid API, no. For an internal tool or a side project, it is fine. The difference is o00
ASArtem Senenkoinuptimepage.hashnode.dev·Jun 30 · 9 min readBuilding an uptime monitor in Rust: one binary, two databases, 130K checks/sec per coreI spent the last few months building Uptimepage, an open-source uptime monitor and status page written in Rust. This post is the build story: the decisions that shaped it, the parts I rewrote, and the10