Leviy Outage History

Leviy had 3 outages in the last 2 years totaling 15h 49m of downtime — averaging 0.1 incidents per month.

There were 3 Leviy outages since October 3, 2025 totaling 15h 49m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://status.leviy.com

Notice August 13, 2026

Leviy is responding slower than usual | Leviy reageert langzamer dan gebruikelijk

Detected by Pingoru: Aug 13, 2026, 08:34 AM UTC
Resolved: Aug 13, 2026, 01:42 PM UTC
Duration: 5h 8m

Affected: DashboardMobile AppAccountsFilesInsightsAPI

Timeline · 3 updates

investigating Aug 13, 2026, 08:34 AM UTC

We notice that Leviy takes longer to respond than usual. Our engineers are investigating the cause of the problem. We zien dat Leviy er langer dan gebruikelijk over doet om te reageren. Onze engineers onderzoeken de oorzaak.
monitoring Aug 13, 2026, 10:59 AM UTC

A fix has been implemented and we are monitoring the results.
resolved Aug 13, 2026, 01:42 PM UTC

This incident has been resolved.

Read the full incident report →

Minor July 3, 2026

Insights are down

Detected by Pingoru: Jul 03, 2026, 07:16 AM UTC
Resolved: Jul 03, 2026, 10:56 AM UTC
Duration: 3h 39m

Affected: Insights

Timeline · 3 updates

investigating Jul 03, 2026, 07:16 AM UTC

We are currently investigating this issue.
monitoring Jul 03, 2026, 07:40 AM UTC

A fix has been implemented and we are monitoring the results.
resolved Jul 03, 2026, 10:56 AM UTC

This incident has been resolved.

Read the full incident report →

Notice October 3, 2025

Dashboard and Application are loading very slow or not at all

Detected by Pingoru: Oct 03, 2025, 10:00 AM UTC
Resolved: Oct 03, 2025, 05:00 PM UTC
Duration: 7h

Affected: DashboardMobile AppAccountsFilesInsights

Timeline · 4 updates

identified Oct 03, 2025, 01:31 PM UTC

The issue has been identified and a fix is being implemented.
identified Oct 03, 2025, 01:41 PM UTC

We are continuing to work on a fix for this issue.
monitoring Oct 03, 2025, 02:04 PM UTC

A fix has been implemented and we are monitoring the results.
resolved Oct 05, 2025, 06:41 PM UTC

This incident has been resolved.

Read the full incident report →