CyberLynk Outage History

CyberLynk is up right now

CyberLynk had 14 outages in the last 2 years totaling 118h 35m of downtime — averaging 0.6 incidents per month.

There were 14 CyberLynk outages since November 11, 2025 totaling 118h 35m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://www.cyberlynkstatus.net

Major October 2, 2026

MKE1 Managed PBX Call Issues

Detected by Pingoru
Oct 02, 2026, 03:49 PM UTC
Resolved
Oct 02, 2026, 06:25 PM UTC
Duration
2h 36m
Affected: Voice Over IP Services (MKE1)
Timeline · 4 updates
  1. investigating Oct 02, 2026, 03:49 PM UTC

    We are aware of an issue with inbound and outbound calls on managed FreePBX systems, and our engineers are working on a fix. TalkAnywhere and unmanaged FreePBX customers are not affected. We will provide another update shortly.

  2. identified Oct 02, 2026, 04:14 PM UTC

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

  3. monitoring Oct 02, 2026, 04:14 PM UTC

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

  4. resolved Oct 02, 2026, 06:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 26, 2026

MKE1 Upstream Provider Outage

Detected by Pingoru
Aug 26, 2026, 06:36 PM UTC
Resolved
Aug 29, 2026, 06:24 PM UTC
Duration
2d 23h
Affected: MKE1 Core Datacenter InfrastructureMKE1 - Lumen
Timeline · 4 updates
  1. investigating Aug 26, 2026, 06:36 PM UTC

    One of our upstream providers in our Milwaukee data center is experiencing an outage and we are following their updates as they address the issue. Customers traversing this provider may experience temporary latency/packet loss as traffic is automatically rerouted over our other providers.

  2. identified Aug 26, 2026, 07:37 PM UTC

    The upstream provider has acknowledged the issue and is working to identify the problem. All customer traffic was automatically moved to other providers and we are continuing to monitor.

  3. identified Aug 27, 2026, 09:04 PM UTC

    The upstream provider has located a fiber cut and is working to repair it. Since there is no ongoing impact to customer traffic, our next update will be provided when this has been resolved.

  4. resolved Aug 29, 2026, 06:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 23, 2026

PHX1 Packet Loss

Detected by Pingoru
Aug 23, 2026, 01:37 AM UTC
Resolved
Aug 23, 2026, 02:44 AM UTC
Duration
1h 7m
Affected: PHX1 Core Datacenter Infrastructure
Timeline · 3 updates
  1. investigating Aug 23, 2026, 01:37 AM UTC

    Our NOC is investigating degraded performance on some routes to our PHX1 data center.

  2. monitoring Aug 23, 2026, 01:53 AM UTC

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

  3. resolved Aug 23, 2026, 02:44 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 17, 2026

FreePBXHosting VPS Order Provisioning Timeouts

Detected by Pingoru
Aug 17, 2026, 03:19 PM UTC
Resolved
Aug 17, 2026, 09:44 PM UTC
Duration
6h 25m
Affected: Voice Over IP Services (MKE1)Voice Over IP Services (PHX1)
Timeline · 3 updates
  1. identified Aug 17, 2026, 03:19 PM UTC

    We are observing some FreePBXHosting VPS order provisioning failures as a result of an ongoing Github outage that is causing the process to timeout. Our engineers are monitoring this situation and any customers encountering issues can reach out to [email protected] for assistance. We will provide updates as they become available.

  2. monitoring Aug 17, 2026, 05:03 PM UTC

    Our engineers are observing successful VPS provisioning as Github continues to work to resolve their outage on their end. We will continue to monitor and provide updates as needed.

  3. resolved Aug 17, 2026, 09:44 PM UTC

    Github status reflects that their outage has been resolved. Our engineers have verified that VPS provisioning now functions normally.

Read the full incident report →

Minor August 13, 2026

PHX1 Upstream Provider Packet Loss

Detected by Pingoru
Aug 13, 2026, 03:49 PM UTC
Resolved
Aug 14, 2026, 01:20 AM UTC
Duration
9h 30m
Affected: PHX1 - NTT
Timeline · 5 updates
  1. identified Aug 13, 2026, 03:49 PM UTC

    One of our upstream providers in our Phoenix data center is showing some packet loss for ICMP/SNMP traffic and we are following their updates as they address the issue. Customers with monitoring systems traversing this provider may be seeing loss for certain health checks. This does not appear to affect other types of UDP/TCP traffic at this time.

  2. monitoring Aug 13, 2026, 04:29 PM UTC

    Our upstream provider has confirmed the degraded performance is related to the temperature issue referenced in this incident: https://www.cyberlynkstatus.net/incidents/9yp2dn73jvp6 We will provide an update when this is resolved.

  3. monitoring Aug 13, 2026, 05:08 PM UTC

    Our NOC team has moved remaining traffic off of this provider and we are seeing stability across the network. We are continuing to monitor.

  4. monitoring Aug 13, 2026, 10:10 PM UTC

    We are continuing to monitor updates from this provider. Since this circuit is not impacting customer traffic, the next update will be provided when we have received an all-clear from the provider and have observed stability across the path.

  5. resolved Aug 14, 2026, 01:20 AM UTC

    The upstream provider has provided an all-clear, and we will reintroduce the circuit to our bandwidth mix after an observation period.

Read the full incident report →

Major August 13, 2026

PHX1 Temperature Issue

Detected by Pingoru
Aug 13, 2026, 12:24 PM UTC
Resolved
Aug 14, 2026, 12:53 AM UTC
Duration
12h 28m
Affected: Voice Over IP Services (PHX1)Mac Hosting (PHX1)PHX1 Core Datacenter Infrastructure
Timeline · 8 updates
  1. identified Aug 13, 2026, 12:24 PM UTC

    Our Phoenix data center is experiencing increased temperatures, which is causing issues with a subset of network switches. This is impacting some of our services in the Phoenix data center. The data center operator is aware of the issue and is working on a fix. We will continue to monitor and provide updates as they are received.

  2. monitoring Aug 13, 2026, 01:10 PM UTC

    Impacted services are being migrated to healthy network paths and should be recovering shortly. We are continuing to monitor for any additional alarms as our PHX data center works to resolve the cooling issue. The data center facilities team has HVAC vendors on site to assist with recovery.

  3. monitoring Aug 13, 2026, 01:18 PM UTC

    All services that were experiencing a network outage are now recovering. Temperatures are still elevated, and we are continuing to monitor for updates, and are monitoring for any other impacts to our equipment.

  4. monitoring Aug 13, 2026, 03:28 PM UTC

    Temperatures appear to have stabilized or improved slightly, however they are still elevated. The data center is continuing to work with their vendor on a fix.

  5. monitoring Aug 13, 2026, 04:43 PM UTC

    Our data center provider is continuing to work with their vendor on a fix. We are continuing to see stable (but high) temperatures. There is currently no ETR.

  6. monitoring Aug 13, 2026, 05:14 PM UTC

    Our data center provider has provided this update: PHX-01 is experiencing elevated white space temperatures caused by multiple utility bump events attributable to overnight storms in the area. We have on-site vendors working rapidly to resolve the situation and restore adequate cooling. Technicians have activated mitigation efforts to reduce rising space temperatures. Thus far we have restored Chiller D into operation as of 7:45 am local time. Additional remediation measures include the following action items (anticipated commencement local time; anticipated completion local time): -Chiller C restoration (targeted 12:30 pm) -Temporary on floor cooling and heat removal equipment added (approximately 10:00 am) -Additional temporary chiller and temporary backup generator added (targeted approximately 4:00 pm) Following the restoration of Chiller D, we have seen significant temperature reductions and expect that reduction to continue over the next 60 minutes.

  7. monitoring Aug 13, 2026, 10:06 PM UTC

    Temperatures are slowly dropping and we are continuing to monitor.

  8. resolved Aug 14, 2026, 12:53 AM UTC

    Ambient temperatures continue to decrease steadily, and alarms are beginning to clear. It may take a couple more hours for temperatures to fully return to normal, however there is no customer impact. We are closing out this incident while we continue to monitor.

Read the full incident report →

Major July 8, 2026

Issues logging into cPanel, WHM or webmail

Detected by Pingoru
Jul 08, 2026, 10:21 PM UTC
Resolved
Jul 08, 2026, 11:11 PM UTC
Duration
50m
Affected: Web & Email Hosting (MKE1)
Timeline · 3 updates
  1. identified Jul 08, 2026, 10:21 PM UTC

    cPanel is having an issue with their licensing servers. This is preventing people from logging into cPanel, WHM and webmail. We are waiting for cPanel to release a fix for this issue.

  2. monitoring Jul 08, 2026, 10:48 PM UTC

    cPanel has rolled out an update and cPanel, WHM and webmail should be accessible again. We will continue to monitor.

  3. resolved Jul 08, 2026, 11:11 PM UTC

    The issue has been resolved. If you have any further issues with accessing cPanel, WHM or webmail, please open a support ticket.

Read the full incident report →

Major May 31, 2026

MKE1 Packet Loss

Detected by Pingoru
May 31, 2026, 06:03 PM UTC
Resolved
Jun 01, 2026, 03:54 AM UTC
Duration
9h 50m
Affected: MKE1 Core Datacenter InfrastructureVoice Over IP Services (MKE1)Mac Hosting (MKE1)Web & Email Hosting (MKE1)File Sharing (MKE1)Customer Portal
Timeline · 7 updates
  1. investigating May 31, 2026, 06:03 PM UTC

    Our monitoring systems have detected a network outage in our MKE1 data center and an update will be provided shortly

  2. investigating May 31, 2026, 07:43 PM UTC

    Our engineers have confirmed an issue causing high packet loss / latency at our MKE1 data center and are working on a resolution.

  3. identified May 31, 2026, 09:24 PM UTC

    Our NOC has identified a DDoS attack impacting traffic at our MKE1 data center. We are working with our upstream providers to mitigate the issue and will continue to provide updates as information is available.

  4. identified May 31, 2026, 10:59 PM UTC

    We continue to work with our upstream providers to mitigate the issue.

  5. monitoring Jun 01, 2026, 01:29 AM UTC

    Customers should begin seeing improvements as our NOC continues to mitigate this large scale attack. We will provide another update within one hour. Thank you for your patience.

  6. monitoring Jun 01, 2026, 03:19 AM UTC

    All services have been restored and we are continuing to monitor.

  7. resolved Jun 01, 2026, 03:54 AM UTC

    This incident has been resolved. For any customers experiencing unrelated issues, please open a support ticket and we'll be happy to assist. We thank you for your patience.

Read the full incident report →

Minor April 2, 2026

PHX1 FreePBX VPS Node Outage

Detected by Pingoru
Apr 02, 2026, 02:23 PM UTC
Resolved
Apr 02, 2026, 02:49 PM UTC
Duration
25m
Affected: Voice Over IP Services (PHX1)
Timeline · 3 updates
  1. investigating Apr 02, 2026, 02:23 PM UTC

    Our engineers are investigating a temporary disruption with one of our PHX1 FreePBX Hosting VPS nodes that is affecting a small number of customers. We will provide an update shortly.

  2. monitoring Apr 02, 2026, 02:31 PM UTC

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

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

    This incident has been resolved.

Read the full incident report →

Major March 9, 2026

MKE1 FreePBX VPS Node Outage

Detected by Pingoru
Mar 09, 2026, 10:30 PM UTC
Resolved
Mar 09, 2026, 10:51 PM UTC
Duration
20m
Affected: Voice Over IP Services (MKE1)
Timeline · 4 updates
  1. investigating Mar 09, 2026, 10:30 PM UTC

    Our engineers are investigating an outage with one of our FreePBX Hosting VPS nodes that is affecting a small number of customers. We will provide an update shortly.

  2. identified Mar 09, 2026, 10:34 PM UTC

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

  3. monitoring Mar 09, 2026, 10:44 PM UTC

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

  4. resolved Mar 09, 2026, 10:51 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 8, 2026

MKE1 PBXact VPS Node Outage

Detected by Pingoru
Mar 08, 2026, 05:38 AM UTC
Resolved
Mar 08, 2026, 05:55 AM UTC
Duration
16m
Affected: Voice Over IP Services (MKE1)
Timeline · 4 updates
  1. investigating Mar 08, 2026, 05:38 AM UTC

    Our engineers are investigating an outage with one of our PBXact Hosting VPS nodes that is affecting a small number of customers. We will provide an update shortly.

  2. identified Mar 08, 2026, 05:45 AM UTC

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

  3. monitoring Mar 08, 2026, 05:49 AM UTC

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

  4. resolved Mar 08, 2026, 05:55 AM UTC

    This incident has been resolved.

Read the full incident report →

Major December 16, 2025

MKE1 Upstream Provider BGP Connectivity Issue

Detected by Pingoru
Dec 16, 2025, 06:09 PM UTC
Resolved
Dec 16, 2025, 08:31 PM UTC
Duration
2h 22m
Affected: MKE1 Core Datacenter InfrastructureMKE1 - Spectrum
Timeline · 3 updates
  1. monitoring Dec 16, 2025, 06:09 PM UTC

    This is a continuation of the previous BGP incident. The issue has resurfaced, and our network team has removed the problematic upstream provider from our BGP mix while continuing to troubleshoot with that provider. We will provide another update shortly.

  2. monitoring Dec 16, 2025, 06:46 PM UTC

    We are continuing to work with the upstream provider on this issue. We'll provide the next update when there are further developments.

  3. resolved Dec 16, 2025, 08:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 14, 2025

MKE1 Upstream Provider Packet Loss

Detected by Pingoru
Nov 14, 2025, 03:32 PM UTC
Resolved
Nov 14, 2025, 03:53 PM UTC
Duration
21m
Affected: MKE1 - Cogent
Timeline · 2 updates
  1. investigating Nov 14, 2025, 03:32 PM UTC

    We are observing packet loss for traffic traversing one our upstream providers in our MKE1 data center. Our NOC is engaging with the provider and we will provide an update shortly.

  2. resolved Nov 14, 2025, 03:53 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 14, 2025

Managed Voice Inbound Call Validation Issue

Detected by Pingoru
Nov 14, 2025, 04:38 AM UTC
Resolved
Nov 14, 2025, 04:50 AM UTC
Duration
11m
Affected: Voice Over IP Services (MKE1)
Timeline · 3 updates
  1. identified Nov 14, 2025, 04:38 AM UTC

    Our engineers have identified an inbound call validation issue. Adjustments are being made to correct the issue that may cause some minor delays in call completion.

  2. monitoring Nov 14, 2025, 04:44 AM UTC

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

  3. resolved Nov 14, 2025, 04:50 AM UTC

    This incident has been resolved.

Read the full incident report →