Buttondown Outage History

Buttondown is up right now

Buttondown had 7 outages in the last 2 years — averaging 0.3 incidents per month.

There were 7 Buttondown outages since April 2, 2026. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.buttondown.com

Minor September 9, 2026

Issues with the web app, and the backlog

Detected by Pingoru
Sep 09, 2026, 10:17 PM UTC
Resolved
Sep 09, 2026, 10:17 PM UTC
Duration
—
Affected: Subscriber-facing appAuthor-facing appEmailsAutomations
Timeline · 7 updates
  1. investigating Sep 09, 2026, 07:18 PM UTC

    Status: Investigating We're currently investigating reports that the Dashboard and Archives are down. Affected components Subscriber-facing app (Full outage) Author-facing app (Full outage)

  2. investigating Sep 09, 2026, 07:21 PM UTC

    Status: Investigating We're seeing the Dashboard and Archives come back online, but with some intermittent errors. The team is still investigating the root cause. Affected components Subscriber-facing app (Partial outage) Author-facing app (Partial outage)

  3. monitoring Sep 09, 2026, 07:32 PM UTC

    Status: Monitoring We've mitigated the issue, and we're seeing the Dashboard and Archives come back online. We'll continue monitoring. Affected components Author-facing app (Operational) Subscriber-facing app (Operational)

  4. investigating Sep 09, 2026, 07:58 PM UTC

    Status: Investigating While the Dashboard and Archives are fully back online, we're investigating reports that the backlog is not clearing quickly enough. This is impacting things like drafts, and outbound emails. Affected components Automations (Degraded performance) Emails (Degraded performance) Author-facing app (Operational) Subscriber-facing app (Operational)

  5. investigating Sep 09, 2026, 08:25 PM UTC

    Status: Investigating The team is continuing to investing the issue with the backlog clearing slowly. Affected components Subscriber-facing app (Operational) Automations (Degraded performance) Emails (Degraded performance) Author-facing app (Operational)

  6. monitoring Sep 09, 2026, 08:39 PM UTC

    Status: Monitoring We're seeing the backlog clear, but are continuing to monitor to make sure there are no lingering issues. Affected components Subscriber-facing app (Operational) Automations (Degraded performance) Emails (Degraded performance) Author-facing app (Operational)

  7. resolved Sep 09, 2026, 10:17 PM UTC

    Status: Resolved All services has been restored! We're working directly with authors' who were impacted by the downtime. 💙 Affected components Subscriber-facing app (Operational) Automations (Operational) Emails (Operational) Author-facing app (Operational)

Read the full incident report →

Minor July 17, 2026

Issues logging into the app

Detected by Pingoru
Jul 17, 2026, 03:56 PM UTC
Resolved
Jul 17, 2026, 03:56 PM UTC
Duration
—
Affected: Author-facing app
Timeline · 4 updates
  1. investigating Jul 17, 2026, 03:08 PM UTC

    Status: Investigating We're currently investigating reports of issues logging into the author-facing app. Affected components Author-facing app (Partial outage)

  2. identified Jul 17, 2026, 03:23 PM UTC

    Status: Identified We've identified that this is being caused by an ongoing incident: https://www.cloudflarestatus.com/incidents/652w59bvnbsj with an upstream vendor. We're currently working to move off the impacted servers to restore service. Affected components Author-facing app (Partial outage)

  3. monitoring Jul 17, 2026, 03:44 PM UTC

    Status: Monitoring We've moved our infrastructure off of impacted servers. We're currently confirming with customers that they're able to log into the app, and we'll continue monitoring. Affected components Author-facing app (Degraded performance)

  4. resolved Jul 17, 2026, 03:56 PM UTC

    Status: Resolved We'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 incident](https://www.cloudflarestatus.com/incidents/652w59bvnbsj) as updates come in. Affected components Author-facing app (Operational)

Read the full incident report →

Minor July 14, 2026

Error when uploading image or file

Detected by Pingoru
Jul 14, 2026, 07:13 PM UTC
Resolved
Jul 14, 2026, 07:13 PM UTC
Duration
—
Affected: Author-facing app
Timeline · 3 updates
  1. identified Jul 14, 2026, 07:05 PM UTC

    Status: Identified We've identified an issue that causes a server error when uploading and image or file into the Editor. Working on a fix now. Affected components Author-facing app (Partial outage)

  2. monitoring Jul 14, 2026, 07:12 PM UTC

    Status: Monitoring We restored the authentication key that was rolled which seems to have fixed the problem. Affected components Author-facing app (Operational)

  3. resolved Jul 14, 2026, 07:13 PM UTC

    Status: Resolved Uploading attachments works now. Affected components Author-facing app (Operational)

Read the full incident report →

Minor June 10, 2026

Images not loading

Detected by Pingoru
Jun 10, 2026, 04:35 PM UTC
Resolved
Jun 10, 2026, 04:35 PM UTC
Duration
—
Affected: Subscriber-facing appAuthor-facing appEmails
Timeline · 4 updates
  1. investigating Jun 10, 2026, 03:05 PM UTC

    Status: Investigating We're currently investigating reports that images are not loading in the Editor, Archives and Emails. Affected components Subscriber-facing app (Degraded performance) Emails (Degraded performance) Author-facing app (Degraded performance)

  2. identified Jun 10, 2026, 04:00 PM UTC

    Status: Identified We've learned that this image issue is related to an ongoing incident with Cloudflare files: https://www.cloudflarestatus.com/incidents/fpxb33vnw9bw. We're continuing to monitor the situation and we'll update when we have more information. Affected components Subscriber-facing app (Degraded performance) Emails (Degraded performance) Author-facing app (Degraded performance)

  3. monitoring Jun 10, 2026, 04:15 PM UTC

    Status: Monitoring We've moved traffic off the impacted Cloudflare infrastructure, and we're seeing images working as expected again. (Give your browser a good refresh!) We'll continue to monitor for any lingering issues. Affected components Subscriber-facing app (Operational) Emails (Operational) Author-facing app (Operational)

  4. resolved Jun 10, 2026, 04:35 PM UTC

    Status: Resolved The fix has been stable, and we've had confirmation from Authors that images are working as expected now. Marking this resolved ✅ Affected components Emails (Operational) Author-facing app (Operational) Subscriber-facing app (Operational)

Read the full incident report →

Minor June 4, 2026

Email sending delays

Detected by Pingoru
Jun 04, 2026, 11:59 PM UTC
Resolved
Jun 04, 2026, 11:59 PM UTC
Duration
—
Affected: Emails
Timeline · 4 updates
  1. investigating Jun 04, 2026, 11:00 PM UTC

    Status: Investigating We're monitoring an incident on Postmark: https://status.postmarkapp.com/notices/cjagqohtofnqt9ts-email-sending-delays, that's causing a delay for outbound newsletters and transactional emails. Affected components Emails (Partial outage)

  2. identified Jun 04, 2026, 11:25 PM UTC

    Status: Identified We're currently rerouting traffic to other ESPs. This includes newsletters on the Buttondown domain, and newsletters with managed custom domains: https://docs.buttondown.com/sending-from-a-custom-domain#managed-sending-domain-setup, and transactional emails. Newsletters with a manual sending domain on Postmark servers are still impacted by this outage. Affected components Emails (Partial outage)

  3. monitoring Jun 04, 2026, 11:46 PM UTC

    Status: Monitoring Postmark shipped a fix, and are recovering from the incident! We're seeing the backlog start to clear, and we'll continue monitoring. Affected components Emails (Degraded performance)

  4. resolved Jun 04, 2026, 11:59 PM UTC

    Status: Resolved We're seeing the backlog clear, and emails arriving in inbox! We'll continue to keep an eye on the outbound queue. Affected components Emails (Operational)

Read the full incident report →

Minor April 24, 2026

Archives are not loading

Detected by Pingoru
Apr 24, 2026, 10:00 PM UTC
Resolved
Apr 24, 2026, 10:00 PM UTC
Duration
—
Affected: Subscriber-facing app
Timeline · 3 updates
  1. investigating Apr 24, 2026, 04:32 PM UTC

    Status: Investigating We're currently investigating reports that Archives are not loading. Affected components Subscriber-facing app (Full outage)

  2. monitoring Apr 24, 2026, 04:49 PM UTC

    Status: Monitoring Archives are back online, but may have some lingering errors. We'll continue to monitor. Affected components Subscriber-facing app (Degraded performance)

  3. resolved Apr 24, 2026, 10:00 PM UTC

    Status: Resolved Archives have remained stable, and we're no longer seeing any lingering errors. This incident is now resolved. Affected components Subscriber-facing app (Operational)

Read the full incident report →

Minor April 2, 2026

Investigating reports that the app is down

Detected by Pingoru
Apr 02, 2026, 12:00 AM UTC
Resolved
Apr 02, 2026, 12:00 AM UTC
Duration
—
Affected: Subscriber-facing appAuthor-facing app
Timeline · 5 updates
  1. investigating Mar 31, 2026, 08:20 PM UTC

    Status: Investigating We're currently investigating reports that the Buttondown app is down. This is impacting both the author-facing Dashboard, as well as Archives. Affected components Author-facing app (Full outage) Subscriber-facing app (Full outage)

  2. monitoring Mar 31, 2026, 08:36 PM UTC

    Status: Monitoring Both the Dashboard and Archives back online, but the team is going to continue to monitor. Affected components Subscriber-facing app (Operational) Author-facing app (Operational)

  3. investigating Apr 01, 2026, 07:12 PM UTC

    Status: Investigating We're currently investigating reports that the author-facing Dashboard and Archives are down. Affected components Subscriber-facing app (Full outage) Author-facing app (Full outage)

  4. monitoring Apr 01, 2026, 07:33 PM UTC

    Status: Monitoring We're seeing that the Dashboard and Archives are back online! We'll continue monitoring and looking for additional error reports. Affected components Subscriber-facing app (Operational) Author-facing app (Operational)

  5. resolved Apr 02, 2026, 12:00 AM UTC

    Status: Resolved The fix has been stable, so we're calling this incident resolved. We'll have a recap post available soon. Affected components Subscriber-facing app (Operational) Author-facing app (Operational)

Read the full incident report →