ChangesBunny.netS3 Storage degradation in Frankfurt
Bunny.net: Incident updated: S3 Storage degradation in Frankfurt
Summary pending. The diff below shows exactly what changed.
Incident page: the full timeline of updates
What changed
Struck in red is what Bunny.net removed; blue is what they added. Muted text is unchanged context.
Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
Before captured
In the 2026-11-19 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
002f847a89dc8d8c…After captured
In the 2026-11-19 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
7328ae5933f4b5e4…
History of this incident
TodayFriday, November 20Fri, Nov 20
1 incident change
- Normal progressIncident
Incident updateS3 Storage degradation in Frankfurt
YesterdayThursday, November 19Thu, Nov 19
1 incident change
- Normal progressIncident
Incident updateS3 Storage degradation in Frankfurtthis change
Cite this
Incident updated: S3 Storage degradation in Frankfurt on Bunny.net’s status page, changed 2026-11-19 11:53 UTC (change 1 of 2).
- Title
- Incident updated: S3 Storage degradation in Frankfurt
- Vendor
- Bunny.net
- Date
- URL
- https://rewindex.com/change/r943a18ac68f33f