- Level
- confirmed
- Worst impact
- Major outage
- Regions
- us
- Down Index
- 46of 100
What to do
Check whether you use Polar in us. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 3h 5m it lasted.
Anything that failed between 2026-06-12 13:25 UTC and 2026-06-12 16:30 UTC may need a replay.Subscribe to Polar's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=polar works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Polar 3
- update
We're having trouble connecting to our database. We're investigating the issue.
provider
- update
Everything should be back to normal.
provider
- resolved
Our deepest apologies for the downtime today between 13:17 and 14:18 UTC. Tens of thousands of businesses trust Polar with their billing, and an incident like this should not happen. We'll publish a full post-mortem in the coming days and take actions to make sure it does not happen again. In the meantime, here's exactly what happened. We rotate secrets frequently as a security policy. Today we rotated our database credentials – but a flaw in our config, where the credentials were tied to the database's Terraform resource, caused Terraform to trigger a full resource replacement. Our production database was replaced. It took us an hour to restore and bring everything back. Was any data lost? No. We run point-in-time recovery with remote backups, hosted on Render with enterprise support. We immediately began a PIT recovery, replaying WAL up to the moment before the Terraform change applied. Recovery completed at 14:16 UTC; we confirmed full data integrity and brought infrastructure back online at 14:18 UTC. A few edge cases we're reconciling now – none involve lost data: - Our API stayed up for ~50s after the latest point in time recovery point and kept accepting event ingestion (which we double-write into Tinybird). A few hundred events landed there; we're going to replay them. - We received 3 Stripe webhooks for in-flight transactions as we went down. We're resolving these and reaching out to the affected customers directly. - After restore, our webhook worker was properly restarted to point to the recovered database. That's fixed; it's catching up now, so webhook delivery is delayed but recovering. Polar is fully operational. The only residual effect was delayed webhook delivery while the worker catched up, which it has now. No action is required on your end. Our post-mortem will detail the full timeline and the guardrails we're adding so this class of failure can't recur, and we’re truly sorry it happened in the first place.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-3289f343dc
Is Polar still down?
No, this incident was resolved 2026-06-12 16:30 UTC. For Polar's live state, see https://down.guide/polar.
How long did it last?
3h 5m, from 2026-06-12 13:25 UTC to 2026-06-12 16:30 UTC, by the times Polar posted.
What was affected?
Polar named in us.
What caused it?
Polar hasn't published a root cause. If it does, it shows here.
Where does this come from?
Polar's official status page, https://status.polar.sh, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.