Here’s a graphical summary of the previous month’s entries, for readier overview scanning…
| March 2026 | |||||||
|---|---|---|---|---|---|---|---|
| 1 | 4 | 7 | |||||
|
|
|
|
|
|
| secrets, BGP, egress IPs, SYD |
|
|
|
|
|
|
|
| GraphQL, Sprites |
|
|
|
|
|
|
|
| ORD, SIN, Sprites, DFW×2, metrics |
|
|
|
|
|
|
|
| DFW, logs, FRA, ORD, IAD, Sprites, builders |
|
|
| 
|
|
|
| AMS, SJC, Sprites, SIN |
The format is a little different from Season One of the official Log, in that width is now a gauge of how many users/customers or features were affected, and intensity (dark vs. light colors) indicates that it was a full outage as opposed to simply flakey, slower, etc. Height is still the duration of the incident, however. In most cases, these are my own estimates/guesses as an outside observer, so take them with a grain of salt.
(For those reading only the alt texts: “
” is a narrow short box, “─” is a wide short box, and “│” is a tall thin one. Fractions indicate intensity.)
Each row of the table covers a week, beginning at the upper left on March 1st, and then proceeding with seven columns for each of the seven days. (Unfortunately, there isn’t much flexibility in inking column edges, or the like.)
The worst of this month’s were all either tall but narrow or wide but short. The Fly.io platform has come a long way from the “Big Red Box days” of the olden times.
Aside: In most cases, you can click on a day’s cell in the table to see the most severe Log entry of that day. Occasionally, however, there are multiple candidates or similar ambiguity, and it instead leads to a post within the present forum thread.
Incidents can straddle midnight (00:00 UTC), so, conversely, it’s possible to get the same link out of multiple cells.
Aside2: There were also many reports in the forum over this time period of failed individual Sprites and flakey or unavailable builders. The Depot builders in particular seem a little sensitive to region congestion.
Aside3: Dates and times are in UTC.