Live  /  Yoobi  /  Incident

Yoobi: Storing koppeling met Exact | Disruption Exact integration

Yoobi · yoobi.nlMajor incidentResolved2026-11-04 14:51 UTC
Public — what happened

Summary

Yoobi reported a major disruption to its connection with Exact, beginning on 2 November 2026 at 12:34 UTC, which meant the link between the two services was not working properly. Yoobi said the problem stemmed from an outage on Exact's side and that it was monitoring the situation. On 3 November at 08:30 UTC it said it had found the cause and was working on a fix it expected to put in place soon. The incident was marked resolved on 4 November at 14:51.

Affected

Yoobi web application servers, Yoobi Task servers, Yoobi Extended reporting, Yoobi API, Yoobi sendmail

As listed on Yoobi’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 Yoobi 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 Yoobi: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Yoobi report →

More from Yoobi

Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.

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

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