Live / Exact / Incident
Exact: Exact Online - Oops errors when working in Exact Online (Global)
Exact · exact.comMinor incidentResolved2026-11-06 08:31 UTC
Public — what happened
Summary
Exact said that some users of Exact Online around the world were seeing "Oops" error messages, and that some bank statement imports were failing. The company began investigating on 2026-11-05 at 13:22 UTC and reported at 15:17 UTC that it had found the problem and was working on a solution. At 21:12 UTC it said a fix was in place and it was watching the results, and the incident was marked resolved on 2026-11-06 at 08:31 UTC. Exact rated the incident as minor.
Affected
Exact Online, Exact Online Premium
Timeline
- Started — 2026-11-05 13:22 UTC
- Investigating — 2026-11-05 13:22 UTC
- Identified — 2026-11-05 15:17 UTC
- Monitoring — 2026-11-05 21:12 UTC
- Resolved — 2026-11-06 08:31 UTC · 19h 09m 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 Exact 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 Exact: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Exact report →
More from Exact
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.