Discord outage: Applications experiencing 503 errors

1. resolvedMar 12, 2026, 21:06 UTC

   We believe the 503s have been resolved.

2. investigatingMar 12, 2026, 20:50 UTC

   We are aware that bot traffic may be hitting 503 errors and are investigating the issue.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Discord's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Snowflake: AWS - Middle East (UAE): INC0152681Critical · Mar 1, 2026, 13:33 UTC
• Grafana Cloud: Complete outage in prod-me-central-1Critical · Mar 2, 2026, 06:43 UTC
• Smartsheet: Brandfolder Monthly Reports DelayedMajor · Feb 27, 2026, 21:55 UTC
• MongoDB Atlas: Impaired Cluster Operations – AWS me-central-1 (United Arab Emirates) and AWS me-south-1 (Bahrain)Major · Mar 1, 2026, 19:30 UTC
• Confluent Cloud: Elevated error rates in AWS me-south-1 and me-central-1 regionsMajor · Mar 2, 2026, 07:19 UTC
• Confluence: Static macro rendering is failing in Confluence CloudMajor · Mar 12, 2026, 11:42 UTC
• Snowflake: INC0153465Major · Mar 12, 2026, 19:42 UTC

How often does Discord have incidents?

Discord reported 18 incidents in the last 90 days, 16 of them major or critical. A typical incident lasted 1h 13m. See Discord's uptime and incident history