CacheFly had 51 outages in the last 2 years totaling 135h 36m of downtime — averaging 2.1 incidents per month.
There were 51 CacheFly outages since July 11, 2025 totaling 135h 36m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating reports of timeouts from our MXP1 pop.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating SSL errors affecting our Dallas, US (DFW1) PoP. Traffic may be rerouted to the nearest PoP.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are experiencing degraded performance and elevated error rates in our SJC1 PoP. We are working on addressing the issue
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue in our SJC 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 an outage within our BOM1 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.
During the maintenance, traffic destined for JNB will be re-routed to the nearest pop.
Scheduled maintenance is currently in progress. We will provide updates as necessary.
A fix has been implemented and we are monitoring the results.
The scheduled maintenance has been completed.
We are currently re-directing all pop traffic for CMH1 to the next nearest pop while we investigate a system outage.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
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 with degraded delivery performance in our FRA2 pop.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating an issue in our LPB PoP, during this time 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 an outage of media streaming encoding services within our ORD1 pop.
This incident has been resolved.
We’re currently investigating an outage in Argentina, all traffic is automatically failing over to other locations.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating an issue in our ORD1 pop, during this time traffic will be re-directed to the next nearest pop.
A change has been implemented and we are monitoring the results.
This incident has been resolved.
Our PoP HKG is currently experiencing an degraded performance, we are investigating and will keep you update through this channel.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue in our BSB1 pop, during this time all traffic will be redirected to the next nearest pop.
An issue with our upstream provider has been identified. We are continuing to redirect all traffic to the next nearest pop at this time.
This incident has been resolved.
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.
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 with our DNS globally
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing ingest issues in TKO, IAD and ORD that might affect cache miss delivery in other PoPs. Our engineers are working on resolving the issue.
This incident has been resolved.
There is currently an outage in our BSB1 Pop, we are currently investigating the issue and re-routing all traffic to the next nearest pop during this time.
An issue within our upstream provider has been identified, at this time we are continuing to redirect traffic to the next nearest pop until a fix can be implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Our PoP MIA is currently experiencing an degraded performance. While we're investigating, traffic will be rerouted to the next nearest PoP.
We've isolated the DNS issue in miami and put a fix in place
This incident has been resolved.
We are currently investigating an outage in our DME1 pop, all traffic will be re-directed to the next nearest pop during this time.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an outage in our AMS1 Pop. All traffic will be re-directed to the next nearest pop while we investigate.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Our GRU1 POP is currently experiencing an degraded performance. While we're investigating, traffic will be rerouted to the next nearest PoP.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.