Monitored services+4 this week
32
12 companies6 regions
Global service posture
Company overview
Independent checks from six regions. Official vendor status is shown separately from observed availability.
20 JUL 2026 · 10:42 UTCRolling 24-hour window
Fleet uptime+0.018%
99.982%
18,402 checks passed4 failed
Median latency−14 ms
284ms
P95 812 msP99 1.24 s
Needs attention2 active
02
1 degraded1 elevated latency
Company health matrix
Independent measurement · 24 hours
| Company | State | 24h uptime | P95 | Regions | Latency trace |
|---|---|---|---|---|---|
BTBaseten | Operational | 99.992% | 843 ms | ||
OAOpenAI | Degraded | 99.841% | 1,328 ms | ||
ANAnthropic | Operational | 100.000% | 912 ms | ||
NXNetflix | Investigating | 99.903% | 1,108 ms | ||
CFCloudflare | Operational | 99.999% | 231 ms | ||
OBObin Solutions | Operational | 99.988% | 615 ms |
Baseten · production API
Inference API
OperationalPOST https://inference.baseten.co/v1/chat/completions
SSE · time to first tokenEvery 30 secondsGoogle Cloud6 regions
Average
555ms
−12 ms vs prior
P50
518ms
Stable
P95
879ms
Budget 1,000 ms
P99
1,167ms
2.1× median
Uptime
99.986%
4 failures
Checks
2,866
2,862 passed
Latency by region
Rolling median · hover or focus chart
Interactive regional latency chart. Use left and right arrow keys to inspect samples.
Dashed threshold marks the 1,000 ms latency budget.72 synchronized samples · 3-hour range
Check continuityGreen passed · amber slow · red failed · grey unavailable
Recent diagnostic events
Failures and state transitions · newest first
| Time | Event | Code | Region | Duration |
|---|---|---|---|---|
| 10:31:30 UTC | Response exceeded latency budgetTTFT reached 1,284 ms before first non-empty SSE event. | 200 | SJC | 1,284 ms |
| 09:58:00 UTC | Upstream connection resetTLS connection closed before a response was received. | — | IAD | 5,001 ms |
| 08:42:30 UTC | Regional recovery confirmedThree consecutive checks returned below the latency budget. | 200 | NRT | 668 ms |