Officient incident

Exact Reeleezee - Loket connection with Reeleezee doesn't work (NL)

Minor Resolved View vendor source →
Started
Apr 15, 2026, 01:23 PM UTC
Resolved
Apr 21, 2026, 08:56 AM UTC
Duration
5d 19h
Detected by Pingoru
Apr 15, 2026, 01:23 PM UTC

Affected components

Exact Reeleezee

Update timeline

  1. investigating Apr 15, 2026, 01:23 PM UTC

    Exporting payroll journal entries from Loket to Reeleezee via API connection gives error 'Fout vanuit Reeleezee code 99: PortalConnectorWebservice: Failure Uploading message'. We are currently investigating the cause of this issue. Our apologies for the inconvenience.

  2. resolved Apr 21, 2026, 08:56 AM UTC

    The issue has been resolved. Loket has fixed the technical issue that prevented automatic journal exports to Reeleezee between August 8 and 20, 2026. You can now manually re-export any missing journals from Loket to Reeleezee. Our apologies for the inconvenience.

Looking to track Officient downtime and outages?

Pingoru polls Officient's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Officient reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Officient alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Officient for free

5 free monitors · No credit card required