Exosite Outage History

Exosite partial outage · 1 active incident View live status →

Exosite had 6 outages in the last 2 years totaling 10h 11m of downtime — averaging 0.2 incidents per month.

There were 6 Exosite outages since November 12, 2024 totaling 10h 11m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.exosite.com

Critical July 22, 2026

Murano Issue

Detected by Pingoru
Jul 22, 2026, 04:54 PM UTC
Resolved
Jul 22, 2026, 05:32 PM UTC
Duration
37m
Affected: Murano PlatformExoSense®Murano Device API / IoT ConnectorsMurano Time Series ServiceExosite Account & Billing Management ApplicationMurano Web ServiceMurano Event SystemMurano Key/Value Store ServiceExoSense Device SimulatorMurano User Service
Timeline · 3 updates
  1. investigating Jul 22, 2026, 04:54 PM UTC

    We are actively investigating an issue with Murano

  2. monitoring Jul 22, 2026, 05:02 PM UTC

    We have restored the platform services and continue to monitor.

  3. resolved Jul 22, 2026, 05:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 14, 2026

Murano User Service

Detected by Pingoru
May 14, 2026, 11:00 PM UTC
Resolved
May 15, 2026, 12:24 AM UTC
Duration
1h 23m
Affected: Murano User Service
Timeline · 3 updates
  1. investigating May 14, 2026, 11:00 PM UTC

    We are currently investigating an issue with the Murano User service impacting service requests.

  2. monitoring May 14, 2026, 11:14 PM UTC

    The issue has been mitigated and is being monitored.

  3. resolved May 15, 2026, 12:24 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 2, 2026

One Platform availability

Detected by Pingoru
Apr 02, 2026, 03:34 PM UTC
Resolved
Apr 02, 2026, 06:02 PM UTC
Duration
2h 28m
Affected: Portals Web Interface / Portals APIOne Platform / API
Timeline · 3 updates
  1. investigating Apr 02, 2026, 03:34 PM UTC

    We are investigating an issue affecting One Platform availability

  2. monitoring Apr 02, 2026, 05:40 PM UTC

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

  3. resolved Apr 02, 2026, 06:02 PM UTC

    This incident has been resolved.

Read the full incident report →

Major December 10, 2025

Performance Degradation

Detected by Pingoru
Dec 10, 2025, 08:58 PM UTC
Resolved
Dec 10, 2025, 09:25 PM UTC
Duration
26m
Affected: ExoSense®
Timeline · 3 updates
  1. investigating Dec 10, 2025, 08:58 PM UTC

    We are currently investigating an issue with the Exosense data pipeline.

  2. monitoring Dec 10, 2025, 09:15 PM UTC

    We've taken action to resolve the issue and will continue to monitor.

  3. resolved Dec 10, 2025, 09:25 PM UTC

    This issue has been resolved.

Read the full incident report →

Major June 8, 2025

Account & Billing Management interface availability

Detected by Pingoru
Jun 08, 2025, 07:15 PM UTC
Resolved
Jun 08, 2025, 11:52 PM UTC
Duration
4h 36m
Affected: Exosite Account & Billing Management Application
Timeline · 3 updates
  1. identified Jun 08, 2025, 07:15 PM UTC

    We've identified an issue with our upstream billing provider that is currently impacting availability of Account & Billing Management. Device connectivity and IoT application processing are not impacted.

  2. monitoring Jun 08, 2025, 11:12 PM UTC

    We are seeing improved availability from our systems to our upstream provider at this time.

  3. resolved Jun 08, 2025, 11:52 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 18, 2024

Business account billing information temporarily unavailable

Detected by Pingoru
Nov 18, 2024, 09:59 PM UTC
Resolved
Nov 18, 2024, 10:37 PM UTC
Duration
38m
Affected: Exosite Account & Billing Management Application
Timeline · 2 updates
  1. identified Nov 18, 2024, 09:59 PM UTC

    We've identified an issue with our upstream billing provider that is resulting in longer load times and billing information being temporarily unavailable.

  2. resolved Nov 18, 2024, 10:37 PM UTC

    This incident has been resolved.

Read the full incident report →