← Back to the carnage
REPLICATE
🟡 Replicate's model downloads are getting 504'd because HuggingFace's CDN decided to ghost them. The usual "we're monitoring" dance has begun while engineers refresh the status page like it's a slot machine. (Auto-resolved: no updates in 24h)
// The official story
HuggingFace download issues
// Status page says
Status: Investigating We are aware of 504s being returned by models that reach out to HuggingFace during setup. We believe this is likely related to the disruption visible at https://status.huggingface.co/. We are monitoring and will update when we can identify the HuggingFace CDN is back up/
🔗 Official status page (for the PR-approved version)
https://www.replicatestatus.com//incidents/01KXN0VFGEEGTX7S8GE91WERCMReplicate's Greatest Hits
🟢 REPLICATE
Aug 26, 2026
🟠 Replicate's A100 hardware is ghosting everyone—the infrastructure apparently got tired of working and self-quarantined itself. Kubernetes said 'nope' and cordoned off the machines like they're contagious. Your training jobs are now stuck in purgatory. (Auto-resolved: no updates in 24h)
🟢 REPLICATE
Jul 31, 2026
🟠 Replicate discovered their caching layer was playing gatekeeper with HuggingFace models, choking out H100/L40S/A100 setups. The fix? Nuking the cache and hoping nobody asks questions while they play detective. GPU performance is bruised but stabilizing. (Auto-resolved: no updates in 24h)
🟢 REPLICATE
Jun 03, 2026
🟡 Your L40S and H200 clusters are playing hot potato with model setup times. High contention means everyone's waiting in line while the hardware pretends to be busy. Engineers are investigating why expensive silicon doesn't want to cooperate. (Auto-resolved: no updates in 24h)
🟢 REPLICATE
May 21, 2026
🟠 Everyone wants the fancy GPUs at once and Replicate didn't order enough. Your AI training job is now experiencing the digital equivalent of waiting for concert tickets—severely disappointed and questionably timed. (Auto-resolved: no updates in 24h)