Oxahost Outage History

Oxahost is up right now

Pingoru has recorded 28 incidents for Oxahost: 13 in the last 12 months and 0 in the last 90 days.

Source: oxahost-status.com

28incidents recorded
13last 12 months
0last 90 days
6 hourstypical duration
Incidents per month
036AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Oxahost in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 2026433 of 720 (5%)
July 202665 of 744 (1%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 508 (0%)

Incidents, newest first

Minor July 19, 2026 Connectivity issues in Rack 02 in DC Ben Arous 42m Datacenters (DC1: Ben Arous-Tunisia)

Started Jul 19, 2026, 01:29 PM UTC· resolved Jul 19, 2026, 02:12 PM UTC

  1. investigating Jul 19, 2026, 01:29 PM UTC

    We are currently investigating this incident.

  2. resolved Jul 19, 2026, 02:12 PM UTC

    The disruption was traced back to a **network hardware issue**, specifically an intermittent failure on a top-of-rack switch uplink. While redundant secondary paths prevented a total blackout, a subset of servers experienced brief packet loss and latency spikes. On-site network engineers quickly isolated the faulty hardware and are actively deploying a replacement component to restore full, seamless operational stability.

Read the full incident report →

Minor July 16, 2026 cPanel accounts could not connect to Remote MySQL Server 10 4h 13m Shared Hosting (cPanel /WHM Shared Hosting)

Started Jul 16, 2026, 09:30 PM UTC· resolved Jul 17, 2026, 01:44 AM UTC

  1. investigating Jul 16, 2026, 09:30 PM UTC

    We are currently investigating this incident.

  2. investigating Jul 16, 2026, 09:36 PM UTC

    We are currently investigating this incident.

  3. identified Jul 17, 2026, 12:24 AM UTC

    We are continuing to work on a fix for this incident.

  4. resolved Jul 17, 2026, 01:44 AM UTC

    Following rigorous efforts by our engineering team, we determined that restoring the crashed MySQL 10 instance to its previous state was not technically feasible. To ensure platform stability, we executed our DRP and successfully restored our system utilizing yesterday's backup. We recognize the severity of this outage for our customers. In accordance with our SLA commitments, we are offering one free month of service to all impacted accounts. Please contact our Support department directly to initiate your SLA credit request before next 14 days.

Read the full incident report →

Minor July 16, 2026 Partial power disruption – Tunis Datacenter 11m Datacenters (DC4 : Tunis - Tunisia)

Started Jul 16, 2026, 10:54 AM UTC· resolved Jul 16, 2026, 11:06 AM UTC

  1. investigating Jul 16, 2026, 10:54 AM UTC

    We are currently investigating this incident.

  2. resolved Jul 16, 2026, 11:06 AM UTC

    Power has been fully restored at the Tunis Datacenter, and all services are back online. We sincerely apologize for any inconvenience caused.

Read the full incident report →

Notice June 25, 2026 Upstream connectivity issues 1d 6h Datacenters (DC4 : Tunis - Tunisia)

Started Jun 25, 2026, 05:55 AM UTC· resolved Jun 26, 2026, 12:10 PM UTC

  1. investigating Jun 25, 2026, 05:55 AM UTC

    We are currently investigating this incident.

  2. monitoring Jun 25, 2026, 06:43 AM UTC

    Upstream carrier issue identified and mitigated by the operator. We are currently in the monitoring phase to verify full recovery.

  3. identified Jun 25, 2026, 07:12 AM UTC

    We are experiencing a reoccurrence of service disruptions. Our team is actively investigating the incident and will provide updates as they become available.

  4. identified Jun 25, 2026, 10:02 AM UTC

    Our upstream telecom partner has confirmed they are mitigating a large-scale Distributed Denial of Service (DDoS) attack targeting the national network backbone. The provider is actively working on mitigation strategies, but some disruptions continue. We sincerely apologize for the impact on your services and appreciate your patience as we navigate this major infrastructure event.

  5. monitoring Jun 25, 2026, 01:44 PM UTC

    Uplink has been stable for more than two hours now. We are continuing to monitor the situation closely, and if there are no further interruptions, we will close the incident. Thank you again for your patience!

  6. resolved Jun 26, 2026, 12:10 PM UTC

    Following 24 hours of continuous monitoring confirming full network stability, this incident is now officially closed. A comprehensive incident report will be published on our blog within the next 48 hours. This post will detail the root cause of the upstream operator outage and outline the technical measures we are implementing to prevent this type of issue in the future. Thank you for your patience.

Read the full incident report →

Minor June 11, 2026 Some virtual servers are offline on COMPUTE 20 2h 14m Private Servers (Virtual Private Servers)

Started Jun 11, 2026, 01:08 AM UTC· resolved Jun 11, 2026, 03:23 AM UTC

  1. investigating Jun 11, 2026, 01:08 AM UTC

    We are currently investigating this incident.

  2. monitoring Jun 11, 2026, 02:39 AM UTC

    We identified a hardware issue. We implemented a fix and are currently monitoring the result.

  3. resolved Jun 11, 2026, 03:23 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 19, 2025 Urgent Network Notice: Connectivity Issues in DC2 (Ooredoo) 4h 22m

Started Dec 19, 2025, 06:58 AM UTC· resolved Dec 19, 2025, 11:21 AM UTC

  1. investigating Dec 19, 2025, 06:58 AM UTC

    We are currently experiencing intermittent connectivity issues within our **DC2 Data Center** affecting services routed through **Ooredoo**..

  2. monitoring Dec 19, 2025, 07:58 AM UTC

    Operator "Ooredoo" has implemented a fix and services are back to normal, we are currently monitoring the result..

  3. resolved Dec 19, 2025, 11:21 AM UTC

    The incident is now fully resolved. Following the implemented fix, we have completed more than 3-hour observation window with no further performance degradation or service interruptions. System metrics have returned to baseline, and all services are operating normally..

Read the full incident report →

Minor December 2, 2025 Oxahost Client Area Update – Oxahost

Started Dec 02, 2025, 02:00 AM UTC· resolved Dec 02, 2025, 02:00 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor June 5, 2025 Degraded Performance – COMPUTE10 VPS Node 7h 55m

Started Jun 05, 2025, 05:14 AM UTC· resolved Jun 05, 2025, 01:10 PM UTC

  1. investigating Jun 05, 2025, 05:14 AM UTC

    We are observing degraded performance on the COMPUTE10 VPS node. Affected virtual machines may experience higher CPU load, slower I/O, or intermittent time-outs. Our engineering team is actively running diagnostics to identify the root cause and mitigate the impact. No other compute nodes are affected at this time. We will provide an update soon if we have new information. Thank you for your patience and understanding..

  2. monitoring Jun 05, 2025, 11:10 AM UTC

    We implemented a fix and are currently monitoring the result..

  3. resolved Jun 05, 2025, 01:10 PM UTC

    This incident has been resolved..

Read the full incident report →

Major April 30, 2025 Operations System Major Update –

Started Apr 30, 2025, 11:00 PM UTC· resolved Apr 30, 2025, 11:00 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major December 19, 2024 Some servers are down on TN-DC1 12h 1m

Started Dec 19, 2024, 09:35 PM UTC· resolved Dec 20, 2024, 09:37 AM UTC

  1. investigating Dec 19, 2024, 09:35 PM UTC

    We are currently investigating this incident..

  2. monitoring Dec 20, 2024, 12:00 AM UTC

    Switch loop detected. We replaced hardware and resolved the issue. Now we intensively monitor for 8 hours. We're sorry for any inconvenience..

  3. resolved Dec 20, 2024, 09:37 AM UTC

    No downtime observed. Since more than 8 hours. Incident closed..

Read the full incident report →

Minor December 5, 2024 Hotline systems update –

Started Dec 05, 2024, 05:00 PM UTC· resolved Dec 05, 2024, 05:00 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →