Live  /  Exact  /  Incident

Exact: Exact Multivers/Exact Boekhoud Gemak - Transferring data through ODBC not possible (NL)

Exact · exact.comMinor incidentResolved2026-11-12 13:55 UTC
Public — what happened

Summary

Exact said some customers of Exact Multivers and Exact Boekhoud Gemak in the Netherlands may have been unable to transfer data through an ODBC connection, and it rated the issue as minor. The company began investigating at 09:54 UTC on 2026-11-12 and apologized for the inconvenience. Its updates did not name a cause, and the incident was marked resolved at 13:55 UTC the same day.

Affected

Exact Boekhoud Gemak, Exact Multivers

As listed on Exact’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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 47, 2026, our weekly internet health report.

The full archive is on the Exact status & history page.

Related: Exact status & history. SquidGrid is not affiliated with Exact.