A small graphical overview of the previous month, now that it’s complete in the Log…
| April 2026 | |||||||
|---|---|---|---|---|---|---|---|
|
|
|
|
|
|
| |
|
|
|
|
|
|
| SYD×2, GraphQL, dashboard, metrics, ORD, NRT |
|
|
|
|
|
|
| ORD, SYD, WireGuard, certs |
|
|
|
|
|
|
|
| WireGuard, SIN, dashboard, GraphQL, IAD |
|
|
|
|
|
|
|
| deploys, MPG |
See the earlier March grid for a description of the annotations.
The first four days of April (corresponding to the top row) were clear of incidents, which was certainly a nice way to start things off…
The wide red mark on April 17 was the Vault certificates store (again); this is one of the few remaining services from the era of using Raft-based clusters for global metadata/configuration (as I understand it). In the longer term, there are plans for replacing it, and a note in the companion forum thread mentioned the decentralized PetSem as the probable substitute.
The wide red stroke on April 28, eleven days later, was a global failure of deploys, due to the Machines API erroneously returning an empty list when asked about existing Machines. This event slightly straddled midnight (00:00 UTC), which is why there are two bars, two outgoing links, etc.
Aside: Four incidents didn’t make it into the Infra Log, per se. (Possibly just because there was no further commentary that could be added.) In those spots, the cell in the table links either to the real-time status page’s archives or to a post in the present forum thread, depending on what else was in the air that day.