Snapchat Outage - Nearly 50,000 Reports Filed

Snapchat stopped working for a large slice of its user base on Thursday night. Reports began stacking up on Downdetector at around 9:30 p.m. ET and peaked roughly an hour and a quarter later, near 10:45 p.m. ET, with close to 49,000 people flagging a problem — one of the sharpest spikes the app has produced in years.

The complaints were consistent. Downdetector's breakdown at the peak put about half the reports on login failures, 30% on the app itself misbehaving, and 20% on server connection errors. The chatter on X matched: accounts logged out without warning, snaps stuck mid-send, stories that would not load, and a login screen rejecting credentials that had worked an hour earlier.

By about 5 a.m. ET on Friday the spike had drained away and Downdetector was back to its normal background noise, according to Fox 13. Snap has published nothing — no status note, no cause, no acknowledgement. That is consistent with how the company has handled most of its outages.

What 49,000 reports actually measures

Downdetector counts self-submitted problem reports, not affected accounts, and it accepts only one report per user per service per day. So 49,000 is a floor: the number of people annoyed enough to go find an outage-tracking site, against the 453 million daily active users Snap reported for the fourth quarter of 2024. How many people actually opened the app and got nothing is not knowable from outside Snap, and any "percentage of users affected" figure built on Downdetector data is guesswork dressed up as data.

What the chart is genuinely good for is timing and shape — when a failure started, how steeply it climbed, and when it stopped. The regional heat map is similarly rough: it reflects where reporting users are concentrated, which mostly tracks population density rather than the geography of the fault.

Snapchat's outage history

Snapchat goes down less often than the volume of complaints suggests, but its incidents have been large when they land.

The worst stretch was the summer of 2021. A build of the iOS app pushed to the App Store in late June crashed on launch for a wide swathe of users; Snapchat acknowledged a problem with the latest App Store version and shipped a corrected build that many people had to install manually. A month later, on 29 July, users were locked out again. "We're aware of an issue preventing some Snapchatters from logging in," Snapchat Support posted at the time. Downdetector logged well over 100,000 reports before it cleared.

Not every failure has been Snap's own. On 2 June 2019, network congestion inside Google Cloud in the eastern United States took Snapchat down alongside YouTube, Gmail, Nest and Discord — an upstream provider fault that Snap could do nothing about.

Why it breaks, and what you can do

Snap does not publish post-mortems, so the honest answer for Thursday night is that nobody outside the company knows. The two causes that have been documented in the past are a bad client release and an upstream cloud failure, and a login-heavy failure profile like this one points at the authentication path rather than the app binary — the app opened fine for most people, it just would not let them in.

That also means the standard troubleshooting advice was useless here. Reinstalling, clearing the cache, or switching from Wi-Fi to cellular does nothing against a server-side authentication failure, and repeated login attempts during an outage can trip Snapchat's own rate limits and leave you locked out longer than everyone else. Checking Downdetector and waiting was, on this occasion, the whole fix.