RealUptime

Discord: SLA evidence report

2026-08-24 to 2026-09-23 · measured by RealUptime from independent regions · generated Sep 23, 2026, 9:53 AM UTC

Discord: SLA evidence report

Measured downtime
51h 2m
Across 14 outages in this window.
Window
2026-08-24 to 2026-09-23
UTC, 30 days.

  • Sep 21, 2026, 4:40 AM UTC to Sep 22, 2026, 2:24 AM UTC

    Single region: South America

    21h 44mmeasured in this window

    Discord's claim at the time: Said operational the whole time we measured this outage

  • Sep 13, 2026, 1:34 PM UTC to Sep 13, 2026, 6:00 PM UTC

    Multiple regions: South America, Australia

    4h 26mmeasured in this window

    Discord's claim at the time: Said operational the whole time we measured this outage

  • Sep 12, 2026, 9:42 AM UTC to Sep 12, 2026, 1:46 PM UTC

    Single region: South America

    4h 4mmeasured in this window

    Discord's claim at the time: Said operational the whole time we measured this outage

  • Sep 10, 2026, 5:16 PM UTC to Sep 10, 2026, 6:01 PM UTC

    Single region: Australia

    45.1mmeasured in this window

    Discord's claim at the time: Said operational the whole time we measured this outage

  • Sep 10, 2026, 1:37 AM UTC to Sep 10, 2026, 2:17 AM UTC

    Single region: South America

    40.1mmeasured in this window

    Discord's claim at the time: Said operational the whole time we measured this outage

  • Sep 9, 2026, 6:53 AM UTC to Sep 9, 2026, 7:21 AM UTC

    Single region: Southeast Asia

    27.9mmeasured in this window

    Discord's claim at the time: Said operational the whole time we measured this outage

  • Sep 8, 2026, 8:30 PM UTC to Sep 8, 2026, 11:04 PM UTC

    Multiple regions: South America, Australia

    2h 34mmeasured in this window

    Discord's claim at the time: Said operational the whole time we measured this outage

  • Sep 8, 2026, 6:29 PM UTC to Sep 8, 2026, 6:53 PM UTC

    Single region: South America

    24.2mmeasured in this window

    Discord's claim at the time: Said operational the whole time we measured this outage

  • Sep 8, 2026, 8:44 AM UTC to Sep 8, 2026, 9:28 AM UTC

    Single region: South America

    44.2mmeasured in this window

    Discord's claim at the time: Said operational the whole time we measured this outage

  • Sep 6, 2026, 3:36 PM UTC to Sep 6, 2026, 7:16 PM UTC

    Single region: South America

    3h 40mmeasured in this window

    Discord's claim at the time: Said operational the whole time we measured this outage

  • Sep 6, 2026, 9:13 AM UTC to Sep 6, 2026, 10:46 AM UTC

    Single region: Australia

    1h 33mmeasured in this window

    Discord's claim at the time: Said operational the whole time we measured this outage

  • Sep 5, 2026, 7:40 PM UTC to Sep 6, 2026, 4:49 AM UTC

    Single region: Australia

    9h 9mmeasured in this window

    Discord's claim at the time: Said operational the whole time we measured this outage

  • Sep 5, 2026, 3:31 AM UTC to Sep 5, 2026, 3:55 AM UTC

    Single region: South America

    24.4mmeasured in this window

    Discord's claim at the time: Said operational the whole time we measured this outage

  • Sep 3, 2026, 7:11 PM UTC to Sep 3, 2026, 7:36 PM UTC

    Single region: South America

    24.6mmeasured in this window

    Discord's claim at the time: Said operational the whole time we measured this outage

What we probed

primary
https://discord.com/api/v10/gateway
secondary
https://discordstatus.com/

Estimate an SLA credit

Enter what you pay Discord for this period and their own stated SLA target. This estimates a credit from the measured downtime above. It is one common way to reason about an SLA credit, not Discord's own contract terms, and it is not a legal determination. RealUptime is not counsel.

Based on 3,061.8 measured downtime minutes across this report's window.

Methodology

Every outage above is a period our probes measured Discord as down from enough of the regions we check it from to count as a real outage, not a single unreliable reading (see how we tell the difference). Measured downtime is the wall-clock time inside the window an outage's regions were failing; regions failing together still count as one outage, not one per region.

Discord's claim at the time comes from their own public status feed, polled on our own schedule, and is shown separately from what we measured. We never change our own reading based on what a vendor claims, and their claim never becomes our reading.

This is one external observation from RealUptime's own regions, not Discord's own SLA measurement, which is usually defined against their own instrumentation and may cover a different scope than what we probe. The credit estimate above is a starting point for a conversation with Discord, not a legal determination, and RealUptime is not counsel.