Buttondown logo

Is Buttondown Down?

SaaSLive status, outages, and incident history

No. Buttondown is up right now.

Every monitored Buttondown system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 18m agoLive 路 60s while moving

Know the moment Buttondown breaks

Buttondown is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official Buttondown status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

Buttondown Component Status

The main Buttondown systems on this page. All 5 are operational right now.

5operational
API
Operational
Author-facing app
Operational
Automations
Operational

2 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Emails, Subscriber-facing app.

See all of them free

Component statuses may change independently during partial outages.

Recent Buttondown Outages & Incidents

Incident history from the official Buttondown status page, including resolution updates.

Issues with the web app, and the backlogResolved Sep 9, 2026 路 2h 58mResolved

All services has been restored! We're working directly with authors' who were impacted by the downtime. 馃挋 --- [2026-09-09T20:39:04Z] (monitoring) We're seeing the backlog clear, but are continuing to monitor to make sure there are no lingering issues. --- [2026-09-09T20:25:29Z] (investigating) The team is continuing to investing the issue with the backlog clearing slowly. --- [2026-09-09T19:59:36Z] (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. --- [2026-09-09T19:32:56Z] (monitoring) We've mitigated the issue, and we're seeing the Dashboard and Archives come back online. We'll continue monitoring. --- [2026-09-09T19:21:42Z] (investigating) We're seeing the Dashboard and Archives come back online, but with some intermittent errors. The team is still investigating the root cause. --- [2026-09-09T19:18:57Z] (investigating) We're currently investigating reports that the Dashboard and Archives are down.

Issues logging into the appResolved Jul 17, 2026 路 48 minResolved

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. --- [2026-07-17T15:44:10Z] (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. --- [2026-07-17T15:23:45Z] (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. --- [2026-07-17T15:08:28Z] (investigating) We're currently investigating reports of issues logging into the author-facing app.

Error when uploading image or fileResolved Jul 14, 2026 路 7 minResolved

Uploading attachments works now. --- [2026-07-14T19:12:29Z] (monitoring) We restored the authentication key that was rolled which seems to have fixed the problem. --- [2026-07-14T19:09:55Z] (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.

Buttondown Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Buttondown incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% average 路 1 day with incidentsSep 25

Live Buttondown Outage Reports

Problems reported by engineers using Buttondown. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Buttondown problems reported yet.

Something wrong with Buttondown on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Buttondown

Is Buttondown down? Buttondown reports live availability for 5 components at status.buttondown.com, among them Author-facing app, Subscriber-facing app and API. Track Buttondown outages, degradations and past incidents here, with uptime history and alerts across your SaaS stack.

Over the past 30 days, PulsAPI has measured Buttondown uptime at 100.00%. Response times, incident history, and SLA tracking for Buttondown are available on the PulsAPI dashboard.

Buttondown Status FAQ

Is Buttondown down right now?

The verdict at the top of this page comes from the latest poll of the official Buttondown status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if Buttondown is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Buttondown recovers.

How do I check Buttondown uptime history?

PulsAPI tracks Buttondown uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Buttondown changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Buttondown outages?

PulsAPI reads the official Buttondown status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual Buttondown components?

Yes. PulsAPI monitors 5 individual Buttondown components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Buttondown goes down?

Yes. Create a free account and subscribe to Buttondown: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Buttondown to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Buttondown problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Buttondown?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Buttondown plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Buttondown with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services