All Systems Operational

About This Site

This page shows the current status and potential disruptions of our Dyflexis SAAS infrastructure.
You can subscribe for updates at the top right of the page.

Uptime over the past 90 days. View historical uptime.
Dyflexis Web Application Operational
90 days ago
99.92 % uptime
Today
Dyflexis Mobile App Operational
90 days ago
99.99 % uptime
Today
API Operational
90 days ago
99.99 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Mar 13, 2026

No incidents reported today.

Mar 12, 2026

No incidents reported.

Mar 11, 2026

No incidents reported.

Mar 10, 2026

No incidents reported.

Mar 9, 2026

No incidents reported.

Mar 8, 2026

No incidents reported.

Mar 7, 2026

No incidents reported.

Mar 6, 2026

No incidents reported.

Mar 5, 2026
Nmbrs Payroll Integration Outage – Payroll Processing Not Possible
Resolved - This incident has been resolved.
Mar 5, 12:24 CET
Monitoring - Op dit moment is er een storing bij Nmbrs Payroll, waardoor verloningen via de Nmbrs-koppeling momenteel niet mogelijk zijn. Nmbrs is dit probleem aan het onderzoeken.
Hou de status pagina van Nmbrs zelf in de gaten via https://status.nmbrs.com/

At the moment there is an outage with Nmbrs Payroll, which means that payroll processing via the Nmbrs integration is currently not possible. Nmbrs is investigating the issue.
You can keep an eye on the Nmbrs status page via: https://status.nmbrs.com/
Mar 5, 09:37 CET
Mar 4, 2026

No incidents reported.

Mar 3, 2026

No incidents reported.

Mar 2, 2026

No incidents reported.

Mar 1, 2026

No incidents reported.

Feb 28, 2026
Dyflexis is unavailable
Resolved - This incident has been resolved.
Feb 28, 02:11 CET
Monitoring - The situation is now stabilizing.
Feb 28, 01:54 CET
Update - We are continuing to work on a fix for this issue.
Feb 28, 00:44 CET
Identified - We have identified the source of the problem to be our infrastructure provider. They are aware of the issue and working to resolve it.
Feb 28, 00:38 CET
Investigating - We are currently investigating this issue.
Feb 28, 00:03 CET
Feb 27, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage