Discord's API and Media Proxy ran an elevated error rate for 1h 7m on 1 October 2026. The fault sat on Discord's side, not yours.
Started
19:48 UTC
Duration
Lasted 1h 7m
Source
IsDown
Next time
Discord is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: Media Proxy, API
What happened?
Discord logged one incident on this day, titled "Elevated API error rate", starting at 19:48 UTC. The status page lists two components affected: Media Proxy and API. Discord posted an investigating note at 19:48 and marked the incident resolved at 20:52, giving a duration of 1h 7m. That is the entirety of what Discord published, two updates, no further detail on what caused the error rate or which calls were affected. No user reports were filed during the window. Discord does not explain in these updates why the API and Media Proxy specifically were hit, or whether the errors were isolated to certain regions or request types. One resolved filing from Discord is as much as there is to go on here, so anything beyond "errors rose, then stopped" is not on the record. Over the past 90 days Discord has logged 21 incidents with a median duration of 1 hour 6 minutes, which puts this incident squarely in line with Discord's typical pattern rather than standing out as unusual. No post-mortem has been published.
Learning
An elevated API error rate is a server-side problem, it happens inside Discord's infrastructure before your requests even get a clean response, so pinging your own endpoints during that hour would have told you nothing about it. Your own monitoring watches whether your product is reachable and responding, which is a different question from whether the API you depend on is behaving. UptimeRobot's 30 day data on Discord shows 13 incidents, all resolved, with a median duration of 1h 5m, consistent with what played out here. The shape of this kind of failure is: no warning, a block of elevated errors for roughly an hour, then a resolution with no explanation attached. If you build on Discord's API, expect that pattern to repeat and plan retries and fallbacks around it rather than waiting for a cause to be published. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
