Deft Outage History

Deft is up right now

Deft had 5 outages in the last 2 years totaling 102h 36m of downtime — averaging 0.2 incidents per month.

There were 5 Deft outages since June 20, 2024 totaling 102h 36m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.deft.com

Major May 23, 2025

Network Instablity SYD

Detected by Pingoru
May 23, 2025, 04:28 AM UTC
Resolved
May 23, 2025, 05:29 AM UTC
Duration
1h 1m
Affected: Sydney
Timeline · 4 updates
  1. investigating May 23, 2025, 04:28 AM UTC

    The Summit engineering team is investigating Network packet loss and latency in the Sydney region.

  2. identified May 23, 2025, 05:10 AM UTC

    Summit engineers believe this was isolated to transpacific traffic via a single carrier. We have taken actions to reroute traffic.

  3. monitoring May 23, 2025, 05:21 AM UTC

    Summit engineers have taken action to reroute traffic from the problematic carrier, and we are observing the packet loss clearing. Local traffic did not appear to be impacted. We are monitoring for continued stability.

  4. resolved May 23, 2025, 05:29 AM UTC

    We've identified that traffic has rerouted successfully, and all packet loss has cleared.

Read the full incident report →

Major April 1, 2025

Internal Network Transit Event

Detected by Pingoru
Apr 01, 2025, 02:51 AM UTC
Resolved
Apr 01, 2025, 03:05 AM UTC
Duration
14m
Affected: Chicago
Timeline · 2 updates
  1. identified Apr 01, 2025, 02:51 AM UTC

    Limited degraded network performance for select customers with wave circuit transit between Elk Grove Village (DF-CH1 - Digital Realty Trust CH1), and Chicago 350 Cermak (EQ-CH1).

  2. resolved Apr 01, 2025, 03:05 AM UTC

    Waveserver pair between ORD1 and ORD6 was restored to service after a cold boot of the appliances. Traffic is now being passed properly once again.

Read the full incident report →

Notice November 25, 2024

Microsft 365 Outage affecting Summit communications.

Detected by Pingoru
Nov 25, 2024, 06:19 PM UTC
Resolved
Nov 26, 2024, 12:34 AM UTC
Duration
6h 14m
Timeline · 2 updates
  1. monitoring Nov 25, 2024, 06:19 PM UTC

    We are currently experiencing an outage affecting Microsoft 365 services, including email and voice communications. This disruption may impact our ability to communicate effectively, including ticketing responses. Microsoft has acknowledged the issue and is actively working to resolve it. We will provide updates as more information becomes available.

  2. resolved Nov 26, 2024, 12:34 AM UTC

    Microsoft 365 services continue to return to functional status and our email and voice communications are back online. We will monitor these issues throughout the evening in the event of any lingering issues. Thank you for your patience.

Read the full incident report →

Minor September 18, 2024

Network Carrier Incident

Detected by Pingoru
Sep 18, 2024, 01:22 PM UTC
Resolved
Sep 18, 2024, 01:22 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Sep 18, 2024, 01:22 PM UTC

    Deft Engineers have identified an issue with one of our transit providers and are working on shifting traffic off the carrier. They will conduct further investigation with the carrier and provide updates as more information becomes available.

Read the full incident report →

Notice June 20, 2024

Managed Object Storage Degredation

Detected by Pingoru
Jun 20, 2024, 04:44 PM UTC
Resolved
Jun 24, 2024, 03:50 PM UTC
Duration
3d 23h
Affected: ChicagoVirginia
Timeline · 5 updates
  1. investigating Jun 20, 2024, 03:33 PM UTC

    Engineers are currently investigating an issue with our Managed Object Storage.

  2. investigating Jun 20, 2024, 04:44 PM UTC

    We have isolated the issue to our Chicago Managed Object Storage environment

  3. identified Jun 20, 2024, 05:43 PM UTC

    Engineers are implementing a workaround and will continue to test resolution of the issue.

  4. monitoring Jun 20, 2024, 09:23 PM UTC

    We have applied a vendor-suggested fix that appears to have mitigated the issues. We will continue to monitor and test to validate resolution.

  5. resolved Aug 21, 2024, 03:50 PM UTC

    This incident has been resolved.

Read the full incident report →