Replicate: SLA evidence report
Replicate: SLA evidence report
We hold no probe record for Replicate: we read its status page, so the only incident record here is what Replicate declared there. Nothing below is a measurement of ours, and the absence of one is not a record of no downtime.
- Incidents Replicate declared
- 8
- On its own status page, in this window.
- Window
- 2026-10-06 to 2026-11-05
- UTC, 30 days.
Oct 7, 2026, 2:48 AM UTC to Oct 7, 2026, 11:51 AM UTC
Network Performance Issues in Columbus, impact major
Oct 7, 2026, 2:41 PM UTC to Oct 7, 2026, 3:24 PM UTC
Cloudflare API service issues, impact minor
Oct 8, 2026, 2:00 PM UTC to Oct 8, 2026, 5:00 PM UTC
Network Performance Issues in Kochi, impact minor
Oct 8, 2026, 9:35 PM UTC to Oct 8, 2026, 10:32 PM UTC
Network Performance Issues in Sofia, impact minor
Oct 9, 2026, 2:41 PM UTC to Oct 9, 2026, 7:30 PM UTC
Cloudflare DNS Resolver 1.1.1.1 and Gateway DNS are having issues in SIN, impact minor
Oct 9, 2026, 6:50 PM UTC to Oct 9, 2026, 7:10 PM UTC
Network Performance Issues in Queretaro, impact minor
Oct 9, 2026, 6:52 PM UTC to Oct 10, 2026, 2:12 AM UTC
Cloudflare API service issues, impact minor
Oct 12, 2026, 1:32 PM UTC to Oct 12, 2026, 2:05 PM UTC
Cloudflare Workers API, impact minor
Methodology
These incidents come from Replicate's own public status feed, polled on our own schedule, and are shown as the vendor wrote them. They are not our measurement, we do not estimate an SLA credit from them, and they are not proof of downtime for your account. The credit Replicate owes, if any, is decided under its own SLA.