All services / Messaging and meetings

Discord

Current assessment
Operational (provider)
Confidence
High confidence
Scope
Provider-wide
Last verified
Oct 25, 01:41 AM UTC
Sources
OfficialKorantix

Official incident history

  1. Elevated API error rate

    Started: · Duration: 65 min
    Provider updates (2)
    1. Investigating “We are currently investigating this issue.”
    2. Resolved “This incident has been resolved.”
    Resolved

  2. Age group status mismatch across devices

    Started: · Duration: 84 min
    Provider updates (4)
    1. Investigating “We’re aware of an issue where users are seeing mismatched age group statuses across devices. For example, appearing as “unconfirmed” on an older mobile app version, but "adult" on web/desktop. We’re aware of the issue and actively working on a fix.”
    2. Identified “We’re aware of an issue where users are seeing mismatched age group statuses across devices. For example, appearing as “unconfirmed” on an older mobile app version, but "adult" on web/desktop. We’re aware of the issue and actively working on a fix.”
    3. Monitoring “A fix has been implemented and we are monitoring results. Please close and refresh your app to get the fix for adult status.”
    4. Resolved “This incident has been resolved. https://x.com/discord/status/2102964092189475028?s=20”
    Resolved

  3. Issue / Delay in establishing call connection

    Started: · Duration: 141 min
    Provider updates (4)
    1. Investigating “We are currently investigating this issue.”
    2. Identified “The issue has been identified and a fix is being implemented.”
    3. Monitoring “A fix has been implemented and we are monitoring the results.”
    4. Resolved “This incident has been resolved.”
    Resolved

  4. Issue establishing voice call

    Started: · Duration: 62 min
    Provider updates (4)
    1. Investigating “We are currently investigating this issue.”
    2. Identified “The issue has been identified and a fix is being implemented.”
    3. Monitoring “A fix has been implemented and we are monitoring the results.”
    4. Resolved “This incident has been resolved.”
    Resolved

  5. API Errors

    Started: · Duration: 25 min
    Provider updates (3)
    1. Investigating “We are currently investigating this issue.”
    2. Monitoring “A fix has been implemented and we are monitoring the results.”
    3. Resolved “This incident has been resolved.”
    Resolved

  6. Google Pay Outage

    Started: · Duration: 28 min
    Provider updates (2)
    1. Identified “We're currently experiencing an issue that prevents users from completing purchases (including Nitro subscriptions and Shop items) through the Android app. This is caused by an ongoing outage with Google Play. Purchases on other platforms (iOS, web, and desktop) are unaffected, and existing subscriptions remain active. We're monitoring Google's status and will post an update as soon as service …”
    2. Resolved “This incident has been resolved.”
    Resolved

  7. Session Unavailability

    Started: · Duration: 50 min
    Provider updates (4)
    1. Investigating “We are currently investigating this issue.”
    2. Identified “The issue has been identified and we are working to restore service.”
    3. Monitoring “A fix has been implemented and we are currently monitoring recovery of services.”
    4. Resolved “This incident has been resolved.”
    Resolved

  8. Media Proxy Latency High

    Started: · Duration: 82 min
    Provider updates (4)
    1. Investigating “We are currently investigating an issue involving high error-rates for image downloads.”
    2. Identified “The issue has been identified and a fix is being implemented.”
    3. Monitoring “A fix has been implemented and we are monitoring the results.”
    4. Resolved “This incident has been resolved.”
    Resolved

  9. Issue with establishing voice calls

    Started: · Duration: 141 min
    Provider updates (3)
    1. Investigating “We are currently investigating this issue.”
    2. Monitoring “A fix has been implemented and we are monitoring the results.”
    3. Resolved “This incident has been resolved.”
    Resolved

  10. Some Servers Unavailable

    Started: · Duration: 56 min
    Provider updates (3)
    1. Identified “We've identified an issue causing some servers to appear unavailable in the client”
    2. Monitoring “A fix has been implemented and we are monitoring the results.”
    3. Resolved “This incident has been resolved.”
    Resolved

  11. Some servers unavailable

    Started: · Duration: 62 min
    Provider updates (4)
    1. Investigating “Some servers may appear unavailable in the client. We are investigating”
    2. Identified “The issue has been identified and a fix is being implemented.”
    3. Monitoring “A fix has been implemented and we are monitoring the results.”
    4. Resolved “This incident has been resolved.”
    Resolved

  12. Voice endpoint selection issues

    Started: · Duration: 16 min
    Provider updates (3)
    1. Investigating “We are investigating problems with voice endpoint selection. Your calls may fail to start or may fail to get an endpoint.”
    2. Identified “We've identified an issue with our endpoint selection service and are applying a mitigation now. We are seeing recovery to endpoint selection now.”
    3. Resolved “This incident has been resolved.”
    Resolved

  13. Server Unavailability

    Started: · Duration: 134 min
    Provider updates (3)
    1. Investigating “We're investigating an issue where some servers are offline.”
    2. Monitoring “We have recovered. We are still investigating the root cause and will post an update once we have more information”
    3. Resolved “This incident has been resolved.”
    Resolved

  14. Some servers and other services (voice calls, activities) not available for some users

    Started: · Duration: 115 min
    Provider updates (3)
    1. Investigating “Some users may not be able to connect to some of their servers”
    2. Identified “We are taking steps to remediate the issue”
    3. Resolved “This incident has been resolved.”
    Resolved

  15. Issue with establishing a call

    Started: · Duration: 14 min
    Provider updates (3)
    1. Investigating “We are currently investigating this issue.”
    2. Monitoring “A fix has been implemented and we are monitoring the results.”
    3. Resolved “This incident has been resolved.”
    Resolved

  16. Issues sending messages for bots and users

    Started: · Duration: 41 min
    Provider updates (3)
    1. Identified “We're aware of an issue preventing users and bots from sending messages, we're working on fully restoring service”
    2. Monitoring “We've recovered service and are continuing to monitor for recovery.”
    3. Resolved “This issue has been fully resolved”
    Resolved

  17. Messaging failures

    Started: · Duration: 87 min
    Provider updates (3)
    1. Identified “We are currently investigating an issue that is impacting users' ability to send direct messages. Other functionality including interactions, shop, and SDK integrations are also affected.”
    2. Monitoring “We have a fix in place are seeing recovery, although some users may still be seeing impact.”
    3. Resolved “This incident has been resolved.”
    Resolved

  18. session starts, DM message delivery down

    Started: · Duration: 17 min
    Provider updates (2)
    1. Investigating “You may have issues logging in or not receiving DM messages live”
    2. Resolved “This incident has been resolved.”
    Resolved

  19. unable to establish voice connection

    Started: · Duration: 25 min
    Provider updates (3)
    1. Investigating “We are currently investigating this issue.”
    2. Monitoring “A fix has been implemented and we are monitoring the results.”
    3. Resolved “This incident has been resolved.”
    Resolved

  20. API Errors

    Started: · Duration: 180 min
    Provider updates (3)
    1. Investigating “We are currently investigating this issue.”
    2. Identified “We've identified an upstream latency issue, and we're working to mitigate its impacts.”
    3. Resolved “This incident has been resolved.”
    Resolved

What the provider published about this service, with the provider's own updates (wording quoted as published).

Evidence

Official
Discord Status ↗ · All Systems Operational · Oct 25, 01:41 AM UTC
Korantix
HTTP 200 · 451 ms · Oct 25, 01:40 AM UTC

Why this assessment

  • Provider reports no active incident.
  • Korantix reached the endpoint (HTTP 200, 451 ms). This only shows that the endpoint answered.
  • 451 ms is within this service's usual range (median 469 ms, p95 709 ms over 665 checks).

Rule set assess-1. The same evidence always gives the same result.

Evidence and freshness

Each source separately: who says it, when it was last observed, and whether it is recent enough to be used.

SourceLast observedAgeUsed in assessment
Official1 min agoYes — recent
Korantix2 min agoYes — recent

Technical details

Affected components (provider)

The provider lists no degraded components.

Official status page ↗