{"host":"api.elevenlabs.io","name":"ElevenLabs","slug":"elevenlabs-api","state":"up","answer":"As of 16:25 UTC: up (answered in 1.1 s from our vantage).","question":"Is the ElevenLabs API down?","current":{"at":"2026-11-19T16:25:00+00:00","class":"up","status":401,"total_ms":1055.6,"error":null},"last_probe":"2026-11-19T16:25:00+00:00","age_s":157,"vantage":"werk-nl","windows":{"24h":{"samples":288,"up":288,"degraded":0,"down":0,"unexpected":0,"probe_fault":0,"uptime_pct":100.0,"p50_ms":990.9,"p95_ms":1416.4,"coverage_pct":100.0},"7d":{"samples":475,"up":475,"degraded":0,"down":0,"unexpected":0,"probe_fault":0,"uptime_pct":null,"p50_ms":null,"p95_ms":null,"coverage_pct":23.6,"withheld":"collecting: under 50 % of this period is measured yet"},"30d":{"samples":475,"up":475,"degraded":0,"down":0,"unexpected":0,"probe_fault":0,"uptime_pct":null,"p50_ms":null,"p95_ms":null,"coverage_pct":5.5,"withheld":"collecting: under 50 % of this period is measured yet"}},"incidents":[],"ongoing_incident":null,"last_24h_line":"Last 24 h: 100.0% up.","class_definition":"up: an expected answer (HTTP 401, 403 or 200) inside 10 seconds","definitions":"up = an expected status (401, 403 or 200) within 10 s; degraded = answered but slower than 3x the host's own 7-day p95, or a one-off 5xx; down = no answer or a repeated 5xx; unexpected = an unexpected status, not counted; probe_fault = our own network failed for nearly all hosts, not counted. An outage is claimed only after 2 or more consecutive down windows (one failed probe is a blip: it may be our own network).","limits":"What this proves: from this vantage (one IPv4 network, one location) the provider's DNS, TCP, TLS and edge or gateway answered, and how fast. What it does NOT prove: that a model generates, that your key, quota or region works, that other regions or IP ranges are up, or that a failure we saw is global. A provider can be fully up for this probe while inference is failing, and the reverse. Treat a down window as 'unreachable from here', and use several sources (and the provider's own status page) for a claim.","method":"Every 5 minutes one unauthenticated HTTPS GET per host, to a cheap documented path (usually the model list), from one vantage. We time DNS, the TCP connect, the TLS handshake and the time to the first byte of the answer, and record the HTTP status. No API key is used and no model is called, so it costs the providers and us nothing. An answer of 401, 403 or 200 (the documented reply of an unauthenticated call) inside 10 seconds is up; slower than three times the host's own 7-day p95 is degraded; a timeout, a DNS, connection or TLS error is down; a 5xx is degraded the first time and down when it repeats in the next window. A status we did not expect (a moved path) is reported as unexpected and left out of the uptime figure. If nearly every host fails to connect in the same run the run is marked probe_fault (that is our network) and left out as well. Uptime is (up + degraded) / (up + degraded + down) over the windows we actually measured; coverage shows how many of the possible windows exist. An incident is two or more consecutive down windows. The raw rows are append-only and never edited.","probe_path":"/v1/user","daily":[{"day":"2026-11-18","samples":277,"up":277,"degraded":0,"down":0,"unexpected":0,"probe_fault":0,"uptime_pct":100.0,"p50_ms":921.2,"p95_ms":1391.7},{"day":"2026-11-19","samples":198,"up":198,"degraded":0,"down":0,"unexpected":0,"probe_fault":0,"uptime_pct":100.0,"p50_ms":992.9,"p95_ms":1496.7}],"interval_s":300,"uptime_definition":"(up + degraded) / (up + degraded + down) over the measured windows","license":"CC BY 4.0"}