Irisity Outage History

Irisity is up right now

Irisity had 2 outages in the last 2 years totaling 28h 12m of downtime — averaging 0.1 incidents per month.

There were 2 Irisity outages since December 17, 2025 totaling 28h 12m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.irisity.io

Critical May 29, 2026

Login issues Irisplus CM and Innovi CM

Detected by Pingoru
May 29, 2026, 03:12 AM UTC
Resolved
May 29, 2026, 04:04 AM UTC
Duration
52m
Affected: Portal and login pagePortal and login pageDashboardMonitor tab with alarm handlingMonitor tab with alarm handlingDashboard
Timeline · 3 updates
  1. investigating May 29, 2026, 03:12 AM UTC

    We are currently investigating this issue.

  2. monitoring May 29, 2026, 03:44 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved May 29, 2026, 04:04 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 17, 2025

IRIS+ and innoVi CM Services Degradation Notice

Detected by Pingoru
Dec 17, 2025, 09:28 AM UTC
Resolved
Dec 18, 2025, 12:49 PM UTC
Duration
1d 3h
Affected: Portal and login pagePortal and login pageMonitor tab with alarm handlingMonitor tab with alarm handling
Timeline · 3 updates
  1. investigating Dec 17, 2025, 09:28 AM UTC

    Dear customer, We are experiencing slow response times on multiple components. We are investigating the underlying issue. We will keep you updated as we get more information on this issue. Thank you, Team @ Irisity

  2. monitoring Dec 17, 2025, 01:13 PM UTC

    A fix has been implemented and we are currently monitoring the results.

  3. resolved Dec 18, 2025, 12:49 PM UTC

    Dear Customer, The slow response times previously observed on some components have now returned to normal levels. Our monitoring confirms that performance is stable, and no further impact is expected at this time. We will continue to keep an eye on the system to ensure it remains stable. Best regards Team @ Irisity

Read the full incident report →