Discord had an age verification bug on 24 September 2026 that lasted 1h 26m. Users saw mismatched age group statuses across devices, for example "unconfirmed" on an older mobile app but "adult" on web or desktop, and the fault sat on Discord's side.
Started
02:08 UTC
Duration
Lasted 1h 26m
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.
What happened?
Discord opened an incident at 02:08 UTC describing an age group status mismatch across devices. The stated example was a user appearing as "unconfirmed" on an older mobile app version while showing as "adult" on web or desktop. This is an account state bug rather than a connectivity failure, so it would not show up as downtime in any uptime check. Discord said it was aware of the issue and working on a fix as of the first update. At 03:05 UTC Discord posted that a fix had been implemented and that it was monitoring results, and it told users to close and refresh their app to pick up the fix for adult status. At 03:32 UTC Discord marked the incident resolved, linking to a post on X for reference. That gives a total span of 1h 26m from first report to resolution. Discord listed no components as affected in its status history for this incident, and gave no root cause for why the mismatch happened in the first place. No user reports were filed during the window on this record, so the complaint volume for this specific bug is not something we can quantify beyond Discord's own three updates. Over the past 90 days Discord has logged 20 incidents with a median duration of 1 hour 4 minutes, so this one ran a bit longer than typical but is not an outlier.
Learning
This incident shows a failure mode that lives entirely in application state rather than in server reachability, and it is a useful case for understanding what external monitoring can and cannot catch. A status check that pings an endpoint and gets a response has no way to see that the account verification flag disagrees between two client versions, because the service was up and responding the whole time. Discord's own age verification logic was wrong for a subset of users, not down, so the fix was a backend patch plus a client refresh rather than a restart of any infrastructure. If your product integrates with Discord for identity or age gating, a green uptime check tells you the API answered, not that the data it returned was correct. The only way to catch this class of bug is to watch for the vendor's own incident filings and correlate them against the specific field or state you depend on. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
