Replicate

Impact-weighted uptime

Replicate published 2.5 incidents per 30 days on average to its status feed across the last 6 months (n=15). We surface this number instead of classifying providers because uptime feeds vary in publishing volume for reasons we cannot judge from outside; compare the uptime numbers below across providers with this denominator in mind.

Uptime weighted by per-incident UIS over the window, computed from incidents this provider published to its own feed. n splits into live (observed in real time) and historical (re-derived from the provider's own archive). Not directly comparable across providers — see the feed-volume disclosure above. How this is computed.

Multi-region reachability + latency

Published SLA compliance

Component classification · 4 rules

Components classified by class (primary inference, secondary API, auxiliary). Flagship models tracked: 0.

Latency probe · parallel-run, methodology v1.0

Alt-signal observations · last 24 hours

Unconfirmed signal observations from the last 1440 minutes. None are published incidents; they corroborate confirmed incidents and feed the multi-source gate. Single-source signal is intentionally not auto-posted.