There were 15 CacheFly outages since February 13, 2026 totaling 398h 24m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
Our OMA1 is currently unavailable and removed from production. All production 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.
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
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Pingoru polls CacheFly's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
5 free monitors · No credit card required