Eerdere incidenten
b.triplepat.com is down
Opgelost Jun 26, 2025 at 7:48am UTC
b-mirror went down for unknown reasons and could not be connected to via ssh. It also stopped producing metrics.
A reboot fixed it, but a further investigation to figure out the root cause is also underway.
1 eerdere update
b.triplepat.com and c.triplepat.com are down
Opgelost Jun 20, 2025 at 9:16am UTC
C is back up now too.
As always, because at least one of a,b,c, and d was up no data has been lost and no user experience was affected.
4 eerdere updates
Some services are down
Opgelost Jun 8, 2025 at 2:32pm UTC
triplepat.com went down on a push. Tailscale was down (but this wasn't detected: thing to fix #1) so the bad push was unable to bind the internal services and refused to bring anything up.
We logged the machine back into our tailnet, redeployed, and everything was fine.
No user data was lost (again: for the outage to count as real every machine must be unreachable), but we now have a new thing to monitor and alert on to prevent such outages in the future.
b.triplepat.com is down
Opgelost May 16, 2025 at 12:49pm UTC
We rebooted the server and it was slow to come back up. As always, one server down is not a problem for us.
2 eerdere updates
triplepat.com is offline
Opgelost Apr 15, 2025 at 3:37pm UTC
triplepat.com is hersteld.
1 eerdere update
triplepat.com is down
Opgelost Apr 14, 2025 at 2:10pm UTC
The root cause is a failed nginx deployment due to what looks like a race condition and/or an overly-picky health check. We are auditing the health checks.
Redeploying the exact same config worked, so it's clear that this failure has something to do with either races or ephemeral machine state.
2 eerdere updates