Previous incidents
triplepat.net is down
Resolved Nov 22, 2026 at 3:11pm UTC
The nginx web server was down for 1-2 seconds during a deployment, but they happened to be the critical 1-2 seconds that our monitor used to determine whether the website was up. Nginx restarts fast, but sometimes not fast enough.
2 previous updates
a.triplepat.com and a.triplepat.net are down
Resolved Oct 31, 2026 at 9:47pm UTC
The a mirror is now back, both its IPv4 and IPv6 addresses match DNS, and the underlying cause of its absence and the underlying cause of its bad address have both been fixed.
5 previous updates
d.triplepat.com is down
Resolved Oct 28, 2026 at 2:18pm UTC
We rebooted the d-server to bring in the latest kernel and tried to see if it would come back fast enough to slip between uptime probes. It did not. It came close though, as shown by the fact that d.triplepat.net ostensibly stayed up the entire time, despite it being the same server.
2 previous updates
triplepat.com and triplepat.net are down
Resolved Oct 24, 2026 at 6:00pm UTC
We set up real-time back-up for the user database (as opposed to hourly backup, which we already had) and we discovered a bug in our deployment script in the process, which meant the services did not come back up the same in production as they had in testing. This caused the deployment to triplepat.com to fail, which halted the deployment with a non-working triplepat.com, while all the mirrors kept working fine.
The bug is fixed, the user-service was down briefly, and the checkin-service ke...
3 previous updates