Discord Status · History · Incident #6168
RESOLVEDMessaging failures
Critical · Started Aug 4, 2026 · 11:49 AM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
Discord Status · History · Incident #6168
RESOLVEDCritical · Started Aug 4, 2026 · 11:49 AM
Duration
1h 27m
Severity
Critical
Detection lead
—
User reports
—
Summary
This incident has been resolved.
Started
Aug 4, 2026 · 11:49 AM
Resolved
Aug 4, 2026 · 1:17 PM
Duration
1h 27m
Severity
Critical
Event timeline
Identified
Aug 4 · 11:49 AM DiscordWe 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.
Identified
Aug 4 · 11:50 AM DiscordWe are continuing to work on a fix for this issue.
Identified
Aug 4 · 12:36 PM DiscordWe are actively working toward system recovery and will post another update in 10 minutes.
Monitoring
Aug 4 · 12:53 PM DiscordWe have a fix in place are seeing recovery, although some users may still be seeing impact.
Monitoring
Aug 4 · 12:59 PM DiscordWe're seeing significant positive impact from our earlier fix; nearly all users should be recovered at this point. We are monitoring closely.
Resolved
Aug 4 · 1:17 PM DiscordThis incident has been resolved.
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026. Pulsetic® is a registered trademark.