Paddle Dashboard Report Downloads Restored After Brief Outage — LiveFuture News
Open on LiveFuture.ai →

Paddle Dashboard Report Downloads Restored After Brief Outage

Paddle says its incident affecting report downloads in the Paddle Dashboard is resolved, with the disruption lasting under an hour on September 2, 2026.

Paddle says the problem that blocked report downloads in the Paddle Dashboard is over. According to the payment platform's own status update, the incident is no longer active, and the disruption was short-lived.

The official incident start was logged at 2026-09-02T20:31:15.612Z, and the official end came at 2026-09-02T21:19:04.251731+00:00. That places the total window at under an hour. This article reflects the situation as of the publication time of 2026-09-02T21:23:17.607811+00:00, when Paddle had already marked the matter resolved.

What was affected

The trouble centered on one specific feature: pulling report downloads inside the Paddle Dashboard. For merchants and finance teams that use Paddle to handle payments, those reports are a routine part of reconciling sales and tracking activity, so even a brief gap can interrupt normal workflows.

The incident carried a medium severity rating and was classified as an infrastructure issue. Based on the supplied details, the problem was limited to report downloads rather than a wider payments outage, and Paddle's status confirms recovery.

How it fits a wider run of resolved incidents

The Paddle recovery lands alongside a string of other service disruptions that were also reported and then closed out around the same period. Each shares the same basic arc: an official start, an official end, and a return to normal operation.

Cloudflare, for example, reported and resolved a Network Route Leak in Palmas, Brazil, with an official start of 2026-09-01T21:47:09.019Z and an end of 2026-09-01T22:05:44.265Z, affecting the Palmas, Brazil (PMW) location. OpenAI logged two separate resolved incidents as well, one covering elevated errors in ChatGPT conversations for Free and Go plans and another involving elevated errors and latency in ChatGPT Work.

In each of the OpenAI cases, the status update stated plainly, "All impacted services have now fully recovered." Taken together, these are all medium-severity infrastructure events that opened and closed within short windows, which is the same pattern seen in the Paddle case.

What it means for users

For anyone who tried and failed to download a report from the Paddle Dashboard during the affected window, the practical takeaway is straightforward: the feature should be working again, since Paddle no longer lists the incident as active.

If a report seems missing or incomplete, it may be worth simply retrying now that recovery is confirmed. Status pages like Paddle's exist to give exactly this kind of quick signal about when a service dips and when it returns, and this incident followed that expected recovery path.