outages.live
Live
PaddleIncident · 2026-10-21 20:04 UTC

Issue affecting metrics and reporting in the seller dashboard

ResolvedOfficial update

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).

The latest update from Paddle.

State

Resolved

Started

10 d ago

2026-10-21 20:04 UTC

Lasted

4 h 5 min

until 2026-10-22 00:09 UTC

Worst impact

Degraded

Timeline

2 updates
20:0421:0522:0723:0800:09
DegradedUpdate postedTimes in UTC

Identified

4 h 5 min 100%

Updates

Times in UTC

As posted by Paddle

Resolved2026-10-22 00:09 UTC

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).

Identified2026-10-21 20:04 UTC

We have identified the issue affecting metrics and reporting in the seller dashboard, which began around 19:37 UTC, due to an outage with a third party provider. We will update the status once the issue has been resolved. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at sellers@paddle.com.

Paddle in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

3

Days with an incident

4

Median duration

47 min

This incident

5.2× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

4 h 5 min
median 47 min
90 days agoToday

Other Paddle incidents

All incidents

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").

Resolvedresolved 59 d ago

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.

Resolvedresolved 69 d ago

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.

Prompt
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.

RSS
https://outages.cc/feed.xml?providers=paddle
Slack
/feed subscribe https://outages.cc/feed.xml?providers=paddle

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane