Incidents reported on status page for Polar https://status.polar.sh/ https://d1lppblt9t2x15.cloudfront.net/logos/1ac7a10ea063551fd64b8599ec8018a2.png https://status.polar.sh/ en https://status.polar.sh/ Fri, 24 Jul 2026 03:46:02 +0000 https://status.polar.sh/#14a924f5094fdd77c55652d2ecacf4ddf9c9d3c21b2f18b7046398e4bd2f05a9 Workers recovered https://status.polar.sh/ Fri, 24 Jul 2026 03:17:04 +0000 https://status.polar.sh/#14a924f5094fdd77c55652d2ecacf4ddf9c9d3c21b2f18b7046398e4bd2f05a9 Workers went down https://status.polar.sh/ Fri, 24 Jul 2026 03:04:06 +0000 https://status.polar.sh/#da5e7e60eff2cf88f38d24d85f3c33a6ded240560c7e27c2d199c97e78475ed7 Workers recovered https://status.polar.sh/ Fri, 24 Jul 2026 02:39:03 +0000 https://status.polar.sh/#da5e7e60eff2cf88f38d24d85f3c33a6ded240560c7e27c2d199c97e78475ed7 Workers went down https://status.polar.sh/ Thu, 09 Jul 2026 10:21:15 +0000 https://status.polar.sh/#57cd36d0a2f22c44438c847030c8ee7145456dded7669f4b92ef81c2b556ec2e Workers recovered https://status.polar.sh/ Thu, 09 Jul 2026 10:01:13 +0000 https://status.polar.sh/#57cd36d0a2f22c44438c847030c8ee7145456dded7669f4b92ef81c2b556ec2e Workers went down https://status.polar.sh/ Thu, 09 Jul 2026 08:13:44 +0000 https://status.polar.sh/#bb745583445efad6d45420a5493f50827f1f64d3390fb5ed4078bdc62c2c8e76 Webhooks recovered https://status.polar.sh/ Thu, 09 Jul 2026 08:13:07 +0000 https://status.polar.sh/#9e5b801c84351a1bd15d64d5bbb512ca8bd9f6ba5eb5fb9b9c510e8fced5a084 Workers recovered https://status.polar.sh/ Thu, 09 Jul 2026 08:06:09 +0000 https://status.polar.sh/#9e5b801c84351a1bd15d64d5bbb512ca8bd9f6ba5eb5fb9b9c510e8fced5a084 Workers went down https://status.polar.sh/ Thu, 09 Jul 2026 08:05:41 +0000 https://status.polar.sh/#bb745583445efad6d45420a5493f50827f1f64d3390fb5ed4078bdc62c2c8e76 Webhooks went down https://status.polar.sh/incident/933127 Wed, 24 Jun 2026 08:00:00 -0000 https://status.polar.sh/incident/933127#a4d8686f2fa8e7b0422b96187a495371db88f7071884686f52b61a90cd3e1bfb Root cause was a FastAPI + OpenTelemetry incompatibility on the latest 0.137 version. We're investigating how this slipped through our rigorous deployment checks. https://status.polar.sh/incident/933127 Wed, 24 Jun 2026 07:36:00 -0000 https://status.polar.sh/incident/933127#e4dd804075bff43ee427d7af6609b18ab27fdd2f02333a6ef65fdc531ecac575 Everything is back to normal https://status.polar.sh/incident/933127 Wed, 24 Jun 2026 07:13:00 -0000 https://status.polar.sh/incident/933127#aaa550109e0f6ddfdae0083573c7c76b5712d4e526dd51f15e73015fa75e5a36 Our API is currently unreachable, a fix is underway. https://status.polar.sh/incident/922075 Fri, 12 Jun 2026 16:30:00 -0000 https://status.polar.sh/incident/922075#38ee4f173787bd6f2303ef878de4f58a58e51499d54abd1fc93a2979055090c3 Everything is back to normal. https://status.polar.sh/incident/922011 Fri, 12 Jun 2026 16:30:00 -0000 https://status.polar.sh/incident/922011#d07975bb107a518a4d99166418ffd1a68c376f14fbfd57ba7ceb099be81177a1 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. https://status.polar.sh/incident/922075 Fri, 12 Jun 2026 14:26:00 -0000 https://status.polar.sh/incident/922075#b4f23e59dda6f0bbb262ad52aa23bbcaf6c41943d4056e33782f8d5f6310024d Some parts of the merchant dashboard may be slower or fail to load as a consequence of our recent database issues. We've noticed that this is leading to slower processing and webhook delivery too. We're working to resolve this soon. https://status.polar.sh/incident/922011 Fri, 12 Jun 2026 14:17:00 -0000 https://status.polar.sh/incident/922011#87ae78b50550ddfffc14819a3a7e49e26e799c753a4c4b98b4ae785d5be60414 Everything should be back to normal. https://status.polar.sh/incident/922011 Fri, 12 Jun 2026 13:25:00 -0000 https://status.polar.sh/incident/922011#fd42d35d34912db1c43e11b2dfa277e5a85fc07084c619e8bf40efe403137624 We're having trouble connecting to our database. We're investigating the issue. https://status.polar.sh/incident/889817 Thu, 07 May 2026 02:45:00 -0000 https://status.polar.sh/incident/889817#77248d46a3e709c7af047f40603bd989ea62c08b161ec84529f60050826a7746 Everything is up and running again. https://status.polar.sh/incident/889817 Thu, 07 May 2026 02:35:00 -0000 https://status.polar.sh/incident/889817#dd2ed4d1a81426f87397d5605fc2cf979298407db2b921901b49f28aca6c7a57 The upstream issue with our database provider has been resolved. We're now working with them to bring everything back up. https://status.polar.sh/incident/889817 Thu, 07 May 2026 02:22:00 -0000 https://status.polar.sh/incident/889817#1c9add33981fd7218b7f4120bc2a04480540894f9e06038ec0f22edf0be3f93a Our database provider has notified us that they've identified the root cause and are implementing a fix https://status.polar.sh/incident/889817 Thu, 07 May 2026 02:10:00 -0000 https://status.polar.sh/incident/889817#421a9255f928ffcedaa9d33665cb774263ba3f88e620a41ea4bd65416c5a872a Due to issues with our database provider, all services are currently unavailable. We're working with them to get this resolved as quickly as possible. We're sorry for the inconvenience. https://status.polar.sh/incident/883023 Wed, 29 Apr 2026 08:16:00 -0000 https://status.polar.sh/incident/883023#bbc6cc1bb527fe070a141e13c024d121b58666ef32fb5a75f9a3d4096a484a59 Login is working correctly in the sandbox again. https://status.polar.sh/incident/878916 Fri, 24 Apr 2026 13:07:00 -0000 https://status.polar.sh/incident/878916#46ee41bf4922b5bfbcde4aacc5695e0cf0daff6785d3fc986a79c001d4e00684 Tasks are being processed timely again. https://status.polar.sh/incident/878320 Thu, 23 Apr 2026 17:31:00 -0000 https://status.polar.sh/incident/878320#5abbf8b228c5c3c9bff8eb36f726fb7eef38c84af2b9353fc66f7a9e9b8887d2 System events are now showing up again. https://status.polar.sh/incident/877148 Wed, 22 Apr 2026 09:52:00 -0000 https://status.polar.sh/incident/877148#03957e669b9941198d02567d501161aed961099d9fdaf6fafaf09a265945ec20 Event ingestion working as expected again https://status.polar.sh/incident/872049 Wed, 15 Apr 2026 13:00:00 -0000 https://status.polar.sh/incident/872049#14525dd178269ada242c2426dfa6ffb600b4d83db708862e9e55e4b55c3fcf50 Checkout links are functional but are returning 0 tax rate. https://status.polar.sh/incident/746927 Mon, 20 Oct 2025 12:16:00 -0000 https://status.polar.sh/incident/746927#3bb347904ce0632fd7ca1cf71f3547de130e1b4889d5e19c712c91a612d30dcf Downstream issues appear to have been resolved or mitigated. We're still monitoring the issue until AWS & Vercel declare the issue fully resolved on their end. https://status.polar.sh/incident/746927 Mon, 20 Oct 2025 08:16:00 -0000 https://status.polar.sh/incident/746927#f02b475ff84feca826188f8f575771035510dd0e88a8d67c18225696db3e3437 We're seeing degraded performance of our dashboard & checkout flows due to issues at our downstream hosting providers (Vercel & AWS). Webhooks and payment processing are not affected. https://status.polar.sh/incident/713970 Thu, 11 Sep 2025 07:00:35 -0000 https://status.polar.sh/incident/713970#0418249e14c250dfb873fc1636a51ebb40a789abfc41cd3b6da095367ee43f1b We wanted to let you know that **Polar will undergo scheduled maintenance on Thursday, September 11th, 2025, at [07:00 AM UTC](https://www.inyourowntime.zone/2025-09-11_07.00_UTC)**. The maintenance window will last approximately **5 minutes**, during which the platform may be temporarily unavailable. This short downtime will allow us to improve the resiliency and performance of Polar as we continue to grow and serve you better. https://status.polar.sh/incident/516068 Thu, 20 Feb 2025 10:02:00 -0000 https://status.polar.sh/incident/516068#25929023152a4a963e54aab1fc7fbfe508dee4997ac7f9585cd3b96321c0584a Maintenance completed https://status.polar.sh/incident/516068 Thu, 20 Feb 2025 10:00:00 -0000 https://status.polar.sh/incident/516068#45afa6499f61e0432c8a7e7824fdc5080c02fe5c1c3bc78619eb99bda1cac83a Our underlying cloud hosting provider performed storage maintenance for all of their databases. Downtime lasted 2min during this maintenance window.