Previous incidents

triplepat.com recovered.

A bad release and a bad deploy combined to cause the main node to go down for 25 minutes. As always, one node down (even the main node!) is no problem. The check-in service continued happily on 4 other servers in 4 different failure zones in 3 different clouds, and therefore no user data was lost.

c.triplepat.com recovered.

A brief network blip in AWS. Not a problem for us, with 4 out of 5 servers still up and accessible we remained quadruple-redundant.

Connectivity to that particular GCP host disappeared and then reappeared. As always, one host going down does not constitute an outage.

D is attached to TILAA cloud, which seems to have less-reliable networking than most clouds. Connectivity disappeared and then reappeared. As always, one host going down does not constitute an outage.