Live / Anaplan / Incident
Anaplan: Platform Alerts
Anaplan · anaplan.comMajor incidentResolved2026-11-05 15:46 UTC
Public — what happened
Summary
Anaplan reported a major incident beginning at 14:37 UTC on 2026-11-05 in which some customers could not open their models. Within about ten minutes the company said the trouble was limited to Polaris models. At 15:09 UTC it said it had found the likely cause and was working on restoring service, and at 15:41 UTC it said service was back and it was monitoring. The incident was marked resolved at 15:46.
Affected
us1: Data Center - US East, us2: Data Center - US West, eu1: Data Center - Netherlands, eu2: Data Center - Germany, eu4: Cloud - Europe, us5: Cloud - US East, ap1: Cloud - Japan, us7: Cloud - US, us3: Cloud - US, us4: Cloud - US, ca1: Cloud - Canada, au1: Cloud - Australia, eu3: Cloud - Europe, me1: Cloud - Saudi Arabia, in1: Cloud - India, id1: Cloud - Indonesia, gb1: Cloud - UK, eu5: Cloud - Europe, ae1: Cloud - UAE, us9: Cloud - US, sg1: Cloud - Singapore, Anaplan Website
Timeline
- Started — 2026-11-05 14:37 UTC
- Investigating — 2026-11-05 14:37 UTC (2 updates)
- Identified — 2026-11-05 15:09 UTC
- Monitoring — 2026-11-05 15:41 UTC
- Resolved — 2026-11-05 15:46 UTC · 1h 10m 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 Anaplan 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 Anaplan: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Anaplan report →
More from Anaplan
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.