5C AI Outage History

5C AI is up right now

5C AI had 2 outages in the last 2 years totaling 79h 30m of downtime, averaging 0.1 incidents per month.

There were 2 5C AI outages since May 14, 2025 totaling 79h 30m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.hypertec.cloud

Critical July 5, 2025

Network Outage in QC2 zone.

Detected by Pingoru
Jul 05, 2025, 12:23 PM UTC
Resolved
Jul 08, 2025, 07:54 PM UTC
Duration
3d 7h
Affected: Network
Timeline · 4 updates
  1. investigating Jul 05, 2025, 12:23 PM UTC

    Dear customers, The Hypertec cloud team is investigating a network outage in the QC-2 zone. Currently, it seems no traffic can enter or leave our facility. We will provide an update as soon as we have identified the cause. The Hypertec cloud team

  2. investigating Jul 05, 2025, 01:39 PM UTC

    Dear customers, The Hypertec cloud team sent onsite hands to the facility to review equipement and expect feedback soon We will provide an update as soon as we have more information. The Hypertec cloud team

  3. monitoring Jul 05, 2025, 02:48 PM UTC

    Dear customers, The onsite team has addressed the situation and is currently monitoring for stability. On our side all systems report up. If you still face issues, please contact us by replying to this message. The Hypertec Cloud team.

  4. resolved Jul 08, 2025, 07:54 PM UTC

    The stability has been confirmed and so we are resolving this incident.

Read the full incident report →

Notice May 14, 2025

OH1/OH1B network outage

Detected by Pingoru
May 14, 2025, 06:00 AM UTC
Resolved
May 14, 2025, 06:00 AM UTC
Duration
–
Timeline · 1 update
  1. resolved Sep 09, 2025, 11:33 AM UTC

    We have experienced a 87 minutes outage at the oh1/oh1b facilities due to an unannounced maintenance from our provider. This was exacerbated by the fact that the provider had its device reachable but had not started the routing engine. This prevented our router from failing over to the secondary link. Our monitoring has been adjusted to account for that possibility.

Read the full incident report →