API status
Live reliability and usage at the Spotify Data API origin.
Not enough data
Waiting for an observation
The monitoring feed has not supplied usable observations. No health claim can be made yet.
Traffic at a glance
Last 15 completed minutes- Requests / minute
- —
- Latest completed minute
- Service availability
- —
- Excludes other client errors
- Successful responses
- —
- 2xx + 3xx / all requests
- p95 response time
- —
- Estimated · p50 —
- Requests
- —
- 24h: —
- HTTP 429
- —
- Responses that hit a rate limit
- Server errors
- —
- 5xx responses
- Cache-served requests
- —
- — responses
Usage over time
Minute by minute
0 of 0 intervals have no observation.
Coverage unavailable · Only completed intervals are shown. Gaps mean no observation, not zero traffic.
Endpoint activity
Last 15 completed minutes. Paths are grouped; individual request IDs are never shown.
| Endpoint | State | Requests | RPM | Availability | p95 | 429 | 5xx | Upstream throttles | Cache |
|---|---|---|---|---|---|---|---|---|---|
| No observed endpoint traffic in this window. | |||||||||
Service areas
Based on observed requestsService-area observations are not available yet.
What these numbers mean
Scope. Requests reaching the API origin across its instances. Requests rejected by a marketplace or gateway before reaching the origin, and demo responses served by this website's cache, are outside this view. Internal retry failures are not counted separately.
Availability. Successful HTTP responses divided by successful HTTP responses plus 429, 5xx and aborted requests. Other client errors are counted separately. An error inside an HTTP 200 response can remain outside this measure; detected upstream throttles are listed separately. This is HTTP request-based reliability, not a time-based uptime SLA.
Latency and caching. p50 and p95 are estimates from latency buckets, including cache-served requests. Cache hits include cached and coalesced responses. Upstream throttles can overlap with 5xx and must not be added twice. “≥” means at least that many throttles were observed with incomplete coverage. A dash means no complete count is available; it does not mean zero.
Coverage. Missing intervals and idle service areas cannot prove health. History starts when collection is enabled and remains partial until each window fills. This page refreshes every 30 seconds while visible.