CacheFly had 51 outages in the last 2 years totaling 442h 6m of downtime — averaging 2.1 incidents per month.
There were 51 CacheFly outages since August 4, 2025 totaling 442h 6m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating an outage within our BSB1 pop. During this time all traffic is being re-directed to the next nearest pop.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an performance issue with our ingress servers. This was first detected at 7:16pm UTC
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Our log shipping infrastructure is currently experiencing elevated load. To maintain overall system stability, infrastructure configuration changes are being temporarily restricted or may be delayed while we work to reduce the load. We are actively monitoring the situation and will provide updates as conditions improve.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue causing delays in log delivery for some customers. The affected services continue to process traffic normally; however, log availability may be delayed while we work to resolve the issue. Our engineering team is actively investigating, and we will provide updates as more information becomes available.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue causing delays in log delivery for some customers. The affected services continue to process traffic normally; however, log availability may be delayed while we work to resolve the issue. Our engineering team is actively investigating, and we will provide updates as more information becomes available.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating reports of service degradation affecting customers served from our IAD POP.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Between 1:16 UTC and 1:37 UTC our MIA1 pop experienced a partial network outage. Services in the pop remained online via redundant services however there was impact for a sub portion of traffic in the pop at this time. As of 1:37 UTC all networking was restored and services are fully functioning again.
The previous incident referenced here: https://www.cacheflystatus.com/incidents/m4d5t9714050 was mistakenly closed, Our fix has been implemented but log processing is still catching up on queued logs at this time.
This incident has been resolved.
At this time we are investigating a service degradation in our Log Processing Pipeline. Our engineers are investigating.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue in our delivery tier that may effect delivery performance.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating performance within our JNB1 pop. During this time all traffic will be re-directed to the next nearest pop.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating a potential network issue affecting our La Paz, Bolivia (LPB1) PoP. Traffic may be rerouted to the nearest PoP, and customers may experience increased latency or brief disruptions.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
An issue has been identified impacting updates to log target configuration. Our team is actively working to resolve it. Log delivery continues to operate normally.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue that is causing a backlog in logging data processing across parts of our network. As a result, some logs may be delayed.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We're currently investigating network issues in POA (Porto Alegre) , and have temporarily routed CDN traffic to alternate locations
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an outage in our MXP1 pop. We have routed traffic to the next nearest pop during this time.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We're currently investigating network issues in Lima, Peru and have temporarily routed CDN traffic to alternate locations
We’ve identified a hardware issue, traffic will continue to route around LIM1 until the failed component is replaced
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an outage for our IAD2 ingest servers.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Our LIM POP is currently unavailable and removed from production. All production traffic is being re-directed to the next nearest pop.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.