Cosmic Global - Notice history

100% - uptime

Los Angeles, California - Operational

100% - uptime
Apr 2026 · 99.98%May · 99.89%Jun · 100.0%
Apr 2026
May 2026
Jun 2026

Dallas, Texas - Operational

100% - uptime
Apr 2026 · 99.99%May · 100.0%Jun · 100.0%
Apr 2026
May 2026
Jun 2026

Ashburn, Virginia - Operational

100% - uptime
Apr 2026 · 100.0%May · 100.0%Jun · 100.0%
Apr 2026
May 2026
Jun 2026

London, United Kingdom - Operational

100% - uptime
Apr 2026 · 99.93%May · 100.0%Jun · 100.0%
Apr 2026
May 2026
Jun 2026

Amsterdam, Netherlands - Operational

100% - uptime
Apr 2026 · 99.98%May · 100.0%Jun · 100.0%
Apr 2026
May 2026
Jun 2026

Frankfurt, Germany - Operational

100% - uptime
Apr 2026 · 100.0%May · 100.0%Jun · 100.0%
Apr 2026
May 2026
Jun 2026
100% - uptime

Transit - Operational

100% - uptime
Apr 2026 · 100.0%May · 100.0%Jun · 100.0%
Apr 2026
May 2026
Jun 2026

Proxies - Operational

100% - uptime
Apr 2026 · 100.0%May · 100.0%Jun · 100.0%
Apr 2026
May 2026
Jun 2026

API - Operational

100% - uptime
Apr 2026 · 100.0%May · 100.0%Jun · 100.0%
Apr 2026
May 2026
Jun 2026

Customer Portal - Operational

100% - uptime
Apr 2026 · 100.0%May · 100.0%Jun · 100.0%
Apr 2026
May 2026
Jun 2026

Notice history

May 2026

LAX Partial Outage
  • Resolved
    Resolved

    We have implemented a new upstream link to restore service for the time being. GTT is still investigating the issue on their end; we suspect either a dark fiber cut or a core system failure. So far they have acknowledged the issue and will provide updates over the next hour.

    Once GTT service is restored, we will be able to cut back over without any interruption to traffic, and the new link will remain in place as a backup to increase resilience. We do not anticipate any further issues at this time.

  • Update
    Update

    We are working to spin up an emergency link to restore service until the GTT connection at LAX Equinix is repaired.

    For context: GTT is used to backhaul traffic between our CoreSite and Equinix facilities. While we do maintain redundant links for this purpose, both are currently down, which has effectively left us without connectivity until the issue is resolved. To address this, we are bringing an additional link online through a separate upstream provider — both to restore service now and to provide added resilience against a similar failure in the future.

  • Update
    Update

    We have confirmed that the issue is not caused by a broken uplink on the upstream device as initially suspected. Instead, the GTT port we receive at this location is experiencing problems. We have shifted our focus accordingly and are in contact with GTT for further updates.

  • Identified
    Identified

    We have identified an issue affecting an upstream device at our LAX Equinix facility. Our LAX core network is hosted separately at CoreSite, so traffic continues to flow normally through our filters and proxies; however, client-facing services hosted in Equinix may experience degraded performance or interruptions. We are actively working with the facility to restore full service as quickly as possible and will provide updates as more information becomes available.

Sporadic London issues
  • Resolved
    Resolved

    As of this morning, the data center has confirmed that the rooftop condensers are fully back in working order, along with the AC units that tripped under the increased pressure when the condensers failed. We are now seeing ambient temperatures restored to normal levels within the facility and do not anticipate any further issues.

  • Update
    Update

    Ambient temperatures in the London data center have returned to near-normal levels. An HVAC technician is on site this morning to complete repairs on the remaining air conditioning unit and to verify the integrity of the other cooling systems in the facility.

    We will continue to monitor the situation closely and will provide a final update once all systems have been fully restored and verified.

  • Monitoring
    Monitoring

    Technicians are on site actively working to repair the rooftop condenser and restore the facility to normal operating temperatures. We will continue to provide updates as the situation develops.

  • Identified
    Identified

    We have confirmed the source of the issue: a failed condenser unit on the roof of the data center, compounded by a separate fault with an air conditioning unit inside the facility. Combined with the ongoing heat wave, these failures have caused ambient temperatures to rise to levels that are triggering thermal throttling and, in some cases, thermal-related crashes on affected hardware.

  • Investigating
    Investigating

    We are currently investigating hardware issues affecting our London data center. At this time, network connectivity is not impacted, though some hardware in this location is experiencing problems.

    Our team has identified that ambient temperatures in the facility are running 15-20% above recent average, which we suspect is related to the ongoing heat wave in the region. We are working closely with the data center's NOC to confirm the root cause and resolve the issue as quickly as possible.

    We will provide further updates as more information becomes available. Thank you for your patience.

Apr 2026

Network Outage
  • Postmortem
    Postmortem

    At approximately 1:25AM EST during a routine filter re-deployment (as a hotfix) to address concerns visualized through our monitoring, the deployment process of our Luascript code went haywire. This was not due to any code logic or bugs introduced into the code, as we redeployed the hotfix moments after without issue, but what we believe to be an extremely unlucky software bug that cascaded through all PoPs due to the way the syncing system works. This was not a full outage, but it is what we would classify as a major outage with more than 80% of traffic being dropped at the time.

    The issue was 95% resolved within the first 10 mins by bringing back up Ashburn, Dallas, London and Amsterdam without issue. Los Angeles took about 12 minutes extra due to needing to reboot the filtering appliances there, and gradually shifting traffic back online. Frankfurt was not affected during this time and its traffic was still flowing through the network.

    We are currently investigating why this specific filter deployment went haywire, as we have deployed code over 30 times in the month of March without a single issue, so the situation is obviously one of concern to our customers, and we acknowledge that and are investigation due to it's how peculiar this situation was.

    We do also acknowledge how the 3 outages within the last 30 days are a significant cause for concern, and we do not want to make excuses, but we do want to iterate that all 3 outages have been caused by things out of our control at the time, but we are currently implementing ways to control them. We do understand that to you, our customers, these are in our control as you trust us to maintain the stability of the network you use, so we take full responsibility for the outages even if they weren't directly caused by us, and are making it our goal to implement increased redundancy and resiliency.

    We are currently in the process of shipping out upgraded filtering hardware & software, upgraded routers and upgraded router components to critical locations to not only introduce further redundancy, but as previously mentioned to improve resliency overall.

    We will have more to share on this in the coming weeks, but rest assured we are working on the issues, and we completely understand your frustrations as a customer. Do not hesitate to voice any concerns to us, and we will be glad to respond.

    Please also take a look at the RFO for the outage in Dallas last week and our plans for the future:

    https://status.as30456.net/cmn9oqp8405n49b3k562hrh6i

  • Resolved
    Resolved
    This incident has been resolved.
  • Update
    Update

    All PoPs have recovered except for LAX. We are working on restoring traffic to LAX.

  • Monitoring
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Investigating
    Investigating

    We are currently investigating this incident.

Apr 2026 to Jun 2026

Next