Dexis Outage History

Dexis is up right now

Dexis had 2 outages in the last 2 years totaling 14h 36m of downtime — averaging 0.1 incidents per month.

There were 2 Dexis outages since September 30, 2025 totaling 14h 36m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.dexis.com

Major October 29, 2025

DEXIS IS Connect/DEXIS IS ScanFlow are currently being impacted by a widespread outage from Microsoft Azure

Detected by Pingoru
Oct 29, 2025, 05:41 PM UTC
Resolved
Oct 30, 2025, 12:39 AM UTC
Duration
6h 57m
Affected: DEXIS IS Connect
Timeline · 5 updates
  1. monitoring Oct 29, 2025, 05:41 PM UTC

    Our products are currently impacted by a widespread outage from Microsoft Azure. The next update will be provided in 30 minutes, or as events warrant. For more info, you can consult Microsoft Azure status page https://azure.status.microsoft/en-us/status

  2. monitoring Oct 29, 2025, 08:53 PM UTC

    The Azure team has deployed their "last known good" configuration, and we are seeing gradual recovery in service health. We will continue to monitoring the service health closely.

  3. monitoring Oct 29, 2025, 10:02 PM UTC

    Services seems to be stabilized and are now operational. We will continue to monitor for stability.

  4. monitoring Oct 29, 2025, 11:05 PM UTC

    Microsoft Azure is continuing to observe recovery across affected services. Our systems remain stable, and we're monitoring closely.

  5. resolved Oct 30, 2025, 12:39 AM UTC

    All Microsoft Azure Services have fully recovered and are operating as expected. We have validated system stability and are now resolving this incident.

Read the full incident report →

Major September 30, 2025

Integration between DEXIS IS Connect and SPARK is currently unavailable

Detected by Pingoru
Sep 30, 2025, 08:10 AM UTC
Resolved
Sep 30, 2025, 03:49 PM UTC
Duration
7h 39m
Affected: DEXIS IS Connect
Timeline · 3 updates
  1. identified Sep 30, 2025, 08:10 AM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Sep 30, 2025, 03:25 PM UTC

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

  3. resolved Sep 30, 2025, 03:49 PM UTC

    This incident has been resolved.

Read the full incident report →