Buttondown Outage History
7 incidents recorded over the last 365 days, 7 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Buttondown Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 9, 2026 | Issues with the web app, and the backlogAll services has been restored! We're working directly with authors' who were impacted by the downtime. 💙 | 2h 58m | Resolved |
| Jul 17, 2026 | Issues logging into the appWe've gotten confirmation from customers that the app is working as expected again, and they're able to log in. 🚀 But we'll keep an eye on the [Cloudflare… | 48 min | Resolved |
| Jul 14, 2026 | Error when uploading image or fileUploading attachments works now. | 7 min | Resolved |
| Jun 10, 2026 | Images not loadingThe fix has been stable, and we've had confirmation from Authors that images are working as expected now. Marking this resolved ✅ | 1h 8m | Resolved |
| Jun 4, 2026 | Email sending delaysWe're seeing the backlog clear, and emails arriving in inbox! We'll continue to keep an eye on the outbound queue. | 42 min | Resolved |
| Apr 24, 2026 | Archives are not loadingArchives have remained stable, and we're no longer seeing any lingering errors. This incident is now resolved. | 5h 27m | Resolved |
| Mar 31, 2026 | Investigating reports that the app is downThe fix has been stable, so we're calling this incident resolved. We'll have a recap post available soon. | 27h 28m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Buttondown incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Buttondown Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Buttondown acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Buttondown outage in this window ran 1d 3h, against a mean recovery of 5h 31m. If you depend on Buttondown in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.