Scheduled Maintenence
We will be performing scheduled maintenance on the database that supports payment processing on Monday, October 5th, 2026, starting at 07:00 UTC. The maintenance is expected to be completed by 08:00 UTC. During this maintenance window, some services may experience brief interruptions or degraded performance. Payments taken through Checkout, subscription renewals, refunds and payment method updates may fail for a short period and can be retried. Webhooks for payment events may be delayed and will be delivered once the maintenance is complete. Sandbox is not affected. We do not anticipate any data loss or long-term disruption, but if you have any questions or concerns, please contact our Customer Support team at sellers@paddle.com.
The latest update from Paddle.
State
Scheduled
Started
41 d ago
2026-09-21 08:57 UTC
Ongoing for
41 days
Worst impact
Maintenance
Timeline
1 updateScheduled
41 days 100%
Updates
Times in UTCAs posted by Paddle
We will be performing scheduled maintenance on the database that supports payment processing on Monday, October 5th, 2026, starting at 07:00 UTC. The maintenance is expected to be completed by 08:00 UTC. During this maintenance window, some services may experience brief interruptions or degraded performance. Payments taken through Checkout, subscription renewals, refunds and payment method updates may fail for a short period and can be retried. Webhooks for payment events may be delayed and will be delivered once the maintenance is complete. Sandbox is not affected. We do not anticipate any data loss or long-term disruption, but if you have any questions or concerns, please contact our Customer Support team at sellers@paddle.com.
Paddle in the last 90 days
Full historyIncidents in 90 days
3
Days with an incident
4
Median duration
47 min
This incident
Not comparable
Other Paddle incidents
All incidentsPaddle·Issue affecting metrics and reporting in the seller dashboard
The incident affecting metrics and reporting in the seller dashboard has been fully resolved. All services are now operating normally. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact our Customer Support team at [sellers@paddle.com](mailto:sellers@paddle.com).
Paddle·Report downloads unavailable in the Paddle Dashboard
The incident affecting report downloads in the Paddle Dashboard has been fully resolved. Our engineers deployed a fix, and the generated reports can now be downloaded as expected. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact our Customer Support team at [sellers@paddle.com](mailto:sellers@paddle.com "sellers@paddle.com").
Paddle·Retain
The incident affecting Retain has been fully resolved. All services are now operating normally. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact our Customer Support team at sellers@paddle.com.
Follow Paddle
Your coding agent knows when Paddle is down, and tells you when a failure is theirs, not yours. You can also get Paddle incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "paddle" and tell me if Paddle has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=paddle/feed subscribe https://outages.cc/feed.xml?providers=paddleFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane