CacheFly Outage History

CacheFly is up right now

Pingoru has recorded 50 incidents for CacheFly: 48 in the last 12 months and 7 in the last 90 days.

Source: cacheflystatus.com

50incidents recorded
48last 12 months
7last 90 days
14 hourstypical duration
Incidents per month
036AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking CacheFly 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 2026349 of 720 (7%)
May 2026519 of 744 (3%)
June 2026424 of 720 (3%)
July 2026416 of 744 (2%)
August 2026533 of 744 (4%)
September 2026131 of 720 (4%)
October 202600 of 540 (0%)

Incidents, newest first

Minor March 19, 2026 Network Instability - LIM1 11d 15h CDN Delivery - South America

Started Mar 19, 2026, 06:33 AM UTC· resolved Mar 30, 2026, 09:39 PM UTC

  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) 3h 19m LIM1

Started Mar 13, 2026, 06:36 PM UTC· resolved Mar 13, 2026, 09:56 PM UTC

  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 3h 24m IAD1

Started Mar 12, 2026, 06:25 PM UTC· resolved Mar 12, 2026, 09:49 PM UTC

  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 2h 4m LIM1

Started Mar 04, 2026, 02:07 PM UTC· resolved Mar 04, 2026, 04:11 PM UTC

  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 16m

Started Feb 25, 2026, 02:00 PM UTC· resolved Feb 25, 2026, 02:16 PM UTC

  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) 19h 2m

Started Feb 23, 2026, 12:15 AM UTC· resolved Feb 23, 2026, 07:18 PM UTC

  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 5h 38m

Started Feb 20, 2026, 07:16 AM UTC· resolved Feb 20, 2026, 12:55 PM UTC

  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 1h 54m

Started Feb 13, 2026, 12:25 AM UTC· resolved Feb 13, 2026, 02:20 AM UTC

  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 12h 48m LAX1

Started Jan 26, 2026, 09:15 AM UTC· resolved Jan 26, 2026, 10:04 PM UTC

  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 33m

Started Jan 14, 2026, 08:43 PM UTC· resolved Jan 14, 2026, 09:16 PM UTC

  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. 1d 7h

Started Dec 31, 2025, 06:45 AM UTC· resolved Jan 01, 2026, 02:19 PM UTC

  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 2d 5h

Started Dec 14, 2025, 10:00 AM UTC· resolved Dec 16, 2025, 03:07 PM UTC

  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 4h 6m

Started Dec 09, 2025, 04:01 PM UTC· resolved Dec 09, 2025, 08:07 PM UTC

  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) 2h 14m DFW1

Started Dec 01, 2025, 11:45 PM UTC· resolved Dec 02, 2025, 02:00 AM UTC

  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 1h 1m SJC1

Started Nov 14, 2025, 06:54 PM UTC· resolved Nov 14, 2025, 07:55 PM UTC

  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 5h 58m SJC1

Started Nov 11, 2025, 02:45 PM UTC· resolved Nov 11, 2025, 08:44 PM UTC

  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 1h 9m

Started Nov 07, 2025, 04:55 PM UTC· resolved Nov 07, 2025, 06:04 PM UTC

  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 3h 10m

Started Nov 06, 2025, 03:10 AM UTC· resolved Nov 06, 2025, 06:20 AM UTC

  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 4h 32m

Started Nov 04, 2025, 06:55 PM UTC· resolved Nov 04, 2025, 11:27 PM UTC

  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 38m SEA1

Started Oct 30, 2025, 08:11 PM UTC· resolved Oct 30, 2025, 08:50 PM UTC

  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 5h 55m Reporting / Log Delivery

Started Oct 28, 2025, 03:53 PM UTC· resolved Oct 28, 2025, 09:48 PM UTC

  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 29m

Started Oct 16, 2025, 01:56 PM UTC· resolved Oct 16, 2025, 02:25 PM UTC

  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 1h 9m LPB1

Started Oct 14, 2025, 05:10 PM UTC· resolved Oct 14, 2025, 06:19 PM UTC

  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 →