Proton Global Outage
A global outage affecting Proton services, causing users to experience connectivity issues and inability to access their accounts or use services.
since
Here's why. Incidents from Friday, August 28, 2026 (UTC), ranked byBreakage Velocity.What is Breakage Velocity?A live score of how fast an outage or regression is spreading. The more people hit it, and the faster, the higher it climbs; it cools off as things calm down.Open-ended scale: under 25 low · 25+ elevated · 100+ high · 300+ extreme.
6 outages, 1 still active today. Worst: Proton (84 d 6 h).
A global outage affecting Proton services, causing users to experience connectivity issues and inability to access their accounts or use services.
since
Between 22:20 and 22:33 UTC, clients in the us-east-1 region experienced disruptions related to message persistence. The issue was resolved after a fix was applied.
– UTC
A network issue affecting the GRU (Sao Paulo, Brazil) region has been resolved. No specific versions or commands are provided to mitigate this problem.
– UTC
Between approximately 14:29 UTC and 15:42 UTC on August 28, 2026, log delivery via MongoDB Atlas Log Integration service was impacted due to an internal service issue. Some users may have encountered delayed or missing logs during this window. Log delivery has since returned to normal.
– UTC
PostgreSQL 15 projects were failing to load /usr/lib/postgresql/15/lib/supautils.so due to GLIBC_2.33 availability issues, disrupting database access in multiple regions. The issue has been resolved and access is now restored.
– UTC
Increased packet loss affecting Customer Applications. Incident has been resolved.
– UTC