CacheFly Outage History

CacheFly is up right now

CacheFly had 48 outages in the last 2 years totaling 443h 13m of downtime, averaging 2 incidents per month.

There were 48 CacheFly outages since October 14, 2025 totaling 443h 13m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: cacheflystatus.com

Minor March 19, 2026

Network Instability - LIM1

Detected by Pingoru
Mar 19, 2026, 06:33 AM UTC
Resolved
Mar 30, 2026, 09:39 PM UTC
Duration
11d 15h
Affected: CDN Delivery - South America
Timeline · 4 updates
  1. investigating Mar 19, 2026, 06:33 AM UTC

    We're currently investigating network issues in Lima, Peru and have temporarily routed CDN traffic to alternate locations

  2. identified Mar 19, 2026, 07:12 AM UTC

    We’ve identified a hardware issue, traffic will continue to route around LIM1 until the failed component is replaced

  3. monitoring Mar 30, 2026, 07:04 PM UTC

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

  4. resolved Mar 30, 2026, 09:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 13, 2026

Network Issue Identified at Lima, Peru (LIM1)

Detected by Pingoru
Mar 13, 2026, 06:36 PM UTC
Resolved
Mar 13, 2026, 09:56 PM UTC
Duration
3h 19m
Affected: LIM1
Timeline · 3 updates
  1. identified Mar 13, 2026, 06:36 PM UTC

    We have identified a network issue impacting our Lima, Peru (LIM1) PoP. Our team is working to mitigate the problem, and traffic is being rerouted to ensure minimal disruption to customers.

  2. monitoring Mar 13, 2026, 07:21 PM UTC

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

  3. resolved Mar 13, 2026, 09:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 12, 2026

IAD2 Ingest Server Outage

Detected by Pingoru
Mar 12, 2026, 06:25 PM UTC
Resolved
Mar 12, 2026, 09:49 PM UTC
Duration
3h 24m
Affected: IAD1
Timeline · 4 updates
  1. investigating Mar 12, 2026, 06:25 PM UTC

    We are currently investigating an outage for our IAD2 ingest servers.

  2. identified Mar 12, 2026, 06:37 PM UTC

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

  3. monitoring Mar 12, 2026, 06:53 PM UTC

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

  4. resolved Mar 12, 2026, 09:49 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 4, 2026

LIM PoP Outage

Detected by Pingoru
Mar 04, 2026, 02:07 PM UTC
Resolved
Mar 04, 2026, 04:11 PM UTC
Duration
2h 4m
Affected: LIM1
Timeline · 4 updates
  1. investigating Mar 04, 2026, 02:07 PM UTC

    Our LIM POP is currently unavailable and removed from production. All production traffic is being re-directed to the next nearest pop.

  2. identified Mar 04, 2026, 02:24 PM UTC

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

  3. monitoring Mar 04, 2026, 03:36 PM UTC

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

  4. resolved Mar 04, 2026, 04:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 25, 2026

HKG1 POP Downtime

Detected by Pingoru
Feb 25, 2026, 02:00 PM UTC
Resolved
Feb 25, 2026, 02:16 PM UTC
Duration
16m
Timeline · 1 update
  1. resolved Feb 25, 2026, 03:41 PM UTC

    Between 14:07 and 14:16 UTC our HKG1 pop experienced a network interruption. We are currently investigating with our providers for a root cause

Read the full incident report →

Notice February 23, 2026

Power Issue Identified at Brisbane, Australia (BNE)

Detected by Pingoru
Feb 23, 2026, 12:15 AM UTC
Resolved
Feb 23, 2026, 07:18 PM UTC
Duration
19h 2m
Timeline · 3 updates
  1. identified Feb 23, 2026, 12:15 AM UTC

    We have identified a power issue at our Brisbane, Australia (BNE) PoP. Redundant systems are keeping services online while we work with local providers to restore full capacity.

  2. monitoring Feb 23, 2026, 06:39 PM UTC

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

  3. resolved Feb 23, 2026, 07:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 20, 2026

OMA1 PoP Outage

Detected by Pingoru
Feb 20, 2026, 07:16 AM UTC
Resolved
Feb 20, 2026, 12:55 PM UTC
Duration
5h 38m
Timeline · 3 updates
  1. investigating Feb 20, 2026, 07:16 AM UTC

    Our OMA1 is currently unavailable and removed from production. All production traffic is being re-directed to the next nearest pop.

  2. monitoring Feb 20, 2026, 12:26 PM UTC

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

  3. resolved Feb 20, 2026, 12:55 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 13, 2026

BOS1 Pop Outage

Detected by Pingoru
Feb 13, 2026, 12:25 AM UTC
Resolved
Feb 13, 2026, 02:20 AM UTC
Duration
1h 54m
Timeline · 3 updates
  1. investigating Feb 13, 2026, 12:25 AM UTC

    Our BOS1 pop has been pulled from production again following our prior maintenance. All production traffic is being re-directed to the next nearest pop at this time

  2. monitoring Feb 13, 2026, 12:32 AM UTC

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

  3. resolved Feb 13, 2026, 02:20 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 26, 2026

LAX DNS Availability

Detected by Pingoru
Jan 26, 2026, 09:15 AM UTC
Resolved
Jan 26, 2026, 10:04 PM UTC
Duration
12h 48m
Affected: LAX1
Timeline · 3 updates
  1. investigating Jan 26, 2026, 09:33 PM UTC

    We're currently investigating alerts for availability of DNS services at our LAX pop.

  2. monitoring Jan 26, 2026, 09:44 PM UTC

    DNS services are back fully operational and we're currently monitoring the service.

  3. resolved Jan 26, 2026, 10:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 14, 2026

MXP1 investigating POP Delivery

Detected by Pingoru
Jan 14, 2026, 08:43 PM UTC
Resolved
Jan 14, 2026, 09:16 PM UTC
Duration
33m
Timeline · 3 updates
  1. investigating Jan 14, 2026, 08:43 PM UTC

    We have pulled the MXP1 pop temporarily due to a delivery issue. During this time while we identify and implement a fix we are re-directing all traffic to the next nearest pop.

  2. monitoring Jan 14, 2026, 09:02 PM UTC

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

  3. resolved Jan 14, 2026, 09:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 31, 2025

EZE1 POP outage.

Detected by Pingoru
Dec 31, 2025, 06:45 AM UTC
Resolved
Jan 01, 2026, 02:19 PM UTC
Duration
1d 7h
Timeline · 4 updates
  1. investigating Dec 31, 2025, 06:45 AM UTC

    Our EZE1 in Buenos Aires, Argentina is currently experiencing an degraded performance. While we're investigating, traffic will be rerouted to the next nearest PoP.

  2. identified Dec 31, 2025, 07:19 AM UTC

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

  3. monitoring Jan 01, 2026, 04:31 AM UTC

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

  4. resolved Jan 01, 2026, 02:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 14, 2025

Investigating CDN Configuration Synchronization

Detected by Pingoru
Dec 14, 2025, 10:00 AM UTC
Resolved
Dec 16, 2025, 03:07 PM UTC
Duration
2d 5h
Timeline · 5 updates
  1. investigating Dec 14, 2025, 12:27 PM UTC

    We are currently investigating an incident related to configuration synchronization on our platform that affects both new and current configurations

  2. identified Dec 14, 2025, 02:24 PM UTC

    A Fix has been rolled out for missing TLS configurations, we're continuing to restore all configurations fully

  3. monitoring Dec 14, 2025, 02:28 PM UTC

    Non TLS configs have been normalized across the CDN footprint and we're seeing 100% availability of all configurations and services at this time

  4. monitoring Dec 15, 2025, 08:55 PM UTC

    Another fix was implemented and configurations for new configs should now be synchronizing correctly oun our platform. We are continuing to monitor at this time.

  5. resolved Dec 16, 2025, 03:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 9, 2025

Investigating timeouts in MXP1

Detected by Pingoru
Dec 09, 2025, 04:01 PM UTC
Resolved
Dec 09, 2025, 08:07 PM UTC
Duration
4h 6m
Timeline · 3 updates
  1. investigating Dec 09, 2025, 04:01 PM UTC

    We are currently investigating reports of timeouts from our MXP1 pop.

  2. monitoring Dec 09, 2025, 04:45 PM UTC

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

  3. resolved Dec 09, 2025, 08:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical December 1, 2025

Investigating Network Issue at Dallas, US (DFW1)

Detected by Pingoru
Dec 01, 2025, 11:45 PM UTC
Resolved
Dec 02, 2025, 02:00 AM UTC
Duration
2h 14m
Affected: DFW1
Timeline · 3 updates
  1. investigating Dec 01, 2025, 11:45 PM UTC

    We are currently investigating SSL errors affecting our Dallas, US (DFW1) PoP. Traffic may be rerouted to the nearest PoP.

  2. monitoring Dec 02, 2025, 12:15 AM UTC

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

  3. resolved Dec 02, 2025, 02:00 AM UTC

    This incident has been resolved.

Read the full incident report →

Major November 14, 2025

SJC1 degraded performance

Detected by Pingoru
Nov 14, 2025, 06:54 PM UTC
Resolved
Nov 14, 2025, 07:55 PM UTC
Duration
1h 1m
Affected: SJC1
Timeline · 3 updates
  1. investigating Nov 14, 2025, 06:54 PM UTC

    We are experiencing degraded performance and elevated error rates in our SJC1 PoP. We are working on addressing the issue

  2. monitoring Nov 14, 2025, 07:12 PM UTC

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

  3. resolved Nov 14, 2025, 07:55 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical November 11, 2025

SJC1 Pop Outage

Detected by Pingoru
Nov 11, 2025, 02:45 PM UTC
Resolved
Nov 11, 2025, 08:44 PM UTC
Duration
5h 58m
Affected: SJC1
Timeline · 3 updates
  1. investigating Nov 11, 2025, 02:45 PM UTC

    We are currently investigating an issue in our SJC pop. During this time all traffic will be re-directed to the next nearest pop.

  2. monitoring Nov 11, 2025, 08:34 PM UTC

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

  3. resolved Nov 11, 2025, 08:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 7, 2025

BOM1 Pop Outage

Detected by Pingoru
Nov 07, 2025, 04:55 PM UTC
Resolved
Nov 07, 2025, 06:04 PM UTC
Duration
1h 9m
Timeline · 3 updates
  1. investigating Nov 07, 2025, 04:55 PM UTC

    We are currently investigating an outage within our BOM1 pop. During this time all traffic is being re-directed to the next nearest pop.

  2. monitoring Nov 07, 2025, 05:53 PM UTC

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

  3. resolved Nov 07, 2025, 06:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 6, 2025

Switch Maintenace For JNB

Detected by Pingoru
Nov 06, 2025, 03:10 AM UTC
Resolved
Nov 06, 2025, 06:20 AM UTC
Duration
3h 10m
Timeline · 4 updates
  1. investigating Nov 06, 2025, 03:10 AM UTC

    During the maintenance, traffic destined for JNB will be re-routed to the nearest pop.

  2. identified Nov 06, 2025, 04:16 AM UTC

    Scheduled maintenance is currently in progress. We will provide updates as necessary.

  3. monitoring Nov 06, 2025, 04:57 AM UTC

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

  4. resolved Nov 06, 2025, 06:20 AM UTC

    The scheduled maintenance has been completed.

Read the full incident report →

Notice November 4, 2025

CMH1 - Pop Outage

Detected by Pingoru
Nov 04, 2025, 06:55 PM UTC
Resolved
Nov 04, 2025, 11:27 PM UTC
Duration
4h 32m
Timeline · 3 updates
  1. investigating Nov 04, 2025, 06:55 PM UTC

    We are currently re-directing all pop traffic for CMH1 to the next nearest pop while we investigate a system outage.

  2. monitoring Nov 04, 2025, 11:10 PM UTC

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

  3. resolved Nov 04, 2025, 11:27 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 30, 2025

SEA1 Investigating SSL Cert Delivery

Detected by Pingoru
Oct 30, 2025, 08:11 PM UTC
Resolved
Oct 30, 2025, 08:50 PM UTC
Duration
38m
Affected: SEA1
Timeline · 3 updates
  1. investigating Oct 30, 2025, 08:11 PM UTC

    We are currently re-routing all pop traffic to our next nearest pop while we investigate an issue with SSL cert delivery in this pop.

  2. monitoring Oct 30, 2025, 08:39 PM UTC

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

  3. resolved Oct 30, 2025, 08:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 28, 2025

Logging and metric data issue

Detected by Pingoru
Oct 28, 2025, 03:53 PM UTC
Resolved
Oct 28, 2025, 09:48 PM UTC
Duration
5h 55m
Affected: Reporting / Log Delivery
Timeline · 4 updates
  1. investigating Oct 28, 2025, 03:53 PM UTC

    We are currently experiencing an issue with our logging and metrics data in the portal, as well as the log shipping feature. We are actively working on resolving the issue.

  2. identified Oct 28, 2025, 06:36 PM UTC

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

  3. monitoring Oct 28, 2025, 07:37 PM UTC

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

  4. resolved Oct 28, 2025, 09:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 16, 2025

FRA2 Investigating Degraded Performance

Detected by Pingoru
Oct 16, 2025, 01:56 PM UTC
Resolved
Oct 16, 2025, 02:25 PM UTC
Duration
29m
Timeline · 3 updates
  1. investigating Oct 16, 2025, 01:56 PM UTC

    We are currently investigating an issue with degraded delivery performance in our FRA2 pop.

  2. identified Oct 16, 2025, 02:10 PM UTC

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

  3. resolved Oct 16, 2025, 02:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 14, 2025

LPB - Pop Outage

Detected by Pingoru
Oct 14, 2025, 05:10 PM UTC
Resolved
Oct 14, 2025, 06:19 PM UTC
Duration
1h 9m
Affected: LPB1
Timeline · 3 updates
  1. investigating Oct 14, 2025, 05:10 PM UTC

    We are currently investigating an issue in our LPB PoP, during this time traffic will be re-directed to the next nearest pop.

  2. monitoring Oct 14, 2025, 05:42 PM UTC

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

  3. resolved Oct 14, 2025, 06:19 PM UTC

    This incident has been resolved.

Read the full incident report →