Live / Central 1 / Incident
Central 1: NC231795 – Microsoft 365 Service Disruption
Central 1 · central1.comResolved2026-11-13 19:07 UTC
Public — what happened
Summary
Central 1 said a disruption affecting Microsoft 365 applications began on 2026-11-12 at 18:43 UTC, slowing email sending and receiving and limiting access. The company said it was following Microsoft's updates, and it asked customers who depend on email alerts for its EFM, FAS and AFT applications to sign in directly to check pending items. By 12:47 UTC on 2026-11-13 it reported partial recovery, with some users regaining Outlook access while delayed email continued to trickle in. The incident is marked resolved as of 19:07 UTC on 2026-11-13.
Affected
Central 1 Services, Payment Services, Treasury Services, Digital Banking Services, Incident Alerting
Timeline
- Started — 2026-11-12 18:43 UTC
- Investigating — 2026-11-12 18:43 UTC
- Monitoring — 2026-11-12 20:20 UTC (2 updates)
- Resolved — 2026-11-13 19:07 UTC · 24h 24m 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 Central 1 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 Central 1: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Central 1 report →
More from Central 1
Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.