Live / Fourth / Incident
Fourth: Singe Sign On Degraded Access Impacting Mobile Apps
Fourth · fourth.comMajor incidentResolved2026-09-16 14:52 UTC
Public — what happened
Summary
Fourth reported a major problem with single sign-on that degraded access to its mobile apps, beginning on 2026-09-16 at 09:22 UTC. The company said the trouble originated with its identity provider, which reported rolling out a fix to the remaining affected instances and manually restarting those the automated fix did not fully repair. Fourth noted that affected customers could still see long delays, intermittent errors, and trouble reaching some services or opening support cases. The incident moved into monitoring and was marked resolved on 2026-09-17 at 11:19.
Timeline
- Started — 2026-09-16 09:22 UTC
- Resolved — 2026-09-17 11:19 UTC · 25h 57m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Fourth against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Fourth: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Fourth report →
More from Fourth
Covered in The Squid’s Ink, Week 39, 2026, our weekly internet health report.