Status
How the API is performing
Measured from the requests URLpipe served in the last 7 days — 5,545 in the last 24 hours. Updated every few minutes.
Per endpoint
Processing time, last 7 days
| Endpoint | Requests | Median | 95th percentile |
|---|---|---|---|
| /console | 266 | 16.8 s | 30.4 s |
| /html | 54,285 | 4.8 s | 26.9 s |
| /markdown | 19 | 4.5 s | 18.5 s |
| /meta | 38 | 6.2 s | 12.4 s |
| 1 | 2.5 s | 2.5 s | |
| /screenshot | 23 | 8.1 s | 14.0 s |
| /technologies | 1 | 3.7 s | 3.7 s |
| /lighthouse | 26 | 12.6 s | 23.3 s |
| /keywords | 2 | 6.9 s | 7.3 s |
| /summarize | 0 | — | — |
| /extract | 1 | 3.0 s | 3.0 s |
Times are the whole of the work for successful requests that fetched the page — the visit, the rendering and the extraction. Cached results, which come back in milliseconds, are left out, and so are failures, which are usually the target site's. A slow target site is a slow request, so these numbers include the web's variance, not just ours. Last computed 2026-10-15 14:53 UTC.
Something wrong?
Tell us
If requests are failing in a way this page doesn't explain, email contact@urlpipe.dev with a request token — it is in the X-Result-Token header of every response.