← Back to the carnage
REPLICATE

🟑 Replicate's T4 setup is throwing a fit when grabbing weights from HuggingFace. Apparently the models forgot how to read. Investigation ongoing, which in tech means someone's stress-testing their espresso machine. (Auto-resolved: no updates in 24h)

⏰ Jan 26, 2026 Fixed (for now) spotted via status_rss

// The official story

Increased setup failures for T4 models

// Status page says

Status: Investigating The problem seems to be isolated to models downloading weights from HuggingFace.

πŸ”— Official status page (for the PR-approved version)

https://www.replicatestatus.com//incidents/01KFWKH9891KD7N0Z3FZJ71G79

Replicate'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 Jul 16, 2026
🟑 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)
🟒 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)