Live  /  Exact  /  Incident

Exact: Exact Online - HTTP 503 during token request and token renewal (NL/BE)

Exact · exact.comMinor incidentResolved2026-11-09 07:40 UTC
Public — what happened

Summary

Exact said that some requests for access tokens to the Exact Online API, including token renewals, were intermittently failing with an HTTP 503 error and no response body, affecting customers in the Netherlands and Belgium. The company reported the problem on 5 November 2026 at 10:13 UTC, rated it minor, and said it was investigating. The text provided includes no cause, but the incident is marked as resolved as of 9 November 2026 at 07:40.

Affected

Exact API

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 46, 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.