How these numbers are calculated
Source. Every billed API call writes one row to our request log with the HTTP status the caller received and how long our server took to answer. A scheduled job reads those rows every 15 minutes and stores one snapshot; this page and the success-rate line on our homepage and pricing page read that same snapshot.
Success rate = responses with status below 400 ÷ (responses below 400 + responses 500 and above). A 503 or any other 5xx counts as a failure. Client errors (4xx) are left out of the rate: they usually mean an invalid URL, a missing parameter or a private or deleted profile. Over the last 30 days, 404 “not found” responses were 4.0% of all responses and other client errors were 2.6%. Some 404s may be our miss rather than a deleted profile; we cannot tell them apart yet, so they are reported here instead of being counted either way.
Retries. When we retry upstream internally, the caller still sees one response and it counts once, by its final status. If you retry a failed call yourself, each attempt counts separately.
Latency is measured from the moment our server starts handling a request until the response is ready. It does not include network time between you and us. Only successful responses that were fetched live count; cached responses are excluded. Median is the 50th percentile, p95 the 95th (linear interpolation).
Low traffic. A platform needs at least 30 counted requests in a window before we show a rate or latency for it. Fewer than that is marked “low traffic”.
Degraded means the last-24-hour success rate is below 95%, or the live check above shows the most recent requests failing.
Internal test traffic excluded. Requests from our own test and monitoring accounts are not counted.
Not counted. Requests rejected before they reach a platform (invalid API key, rate limit, request validation, insufficient credits) are either not logged or are client errors, so they do not affect the rate. Requests lost while the server restarts are not logged either.
Not measured. We do not run an external uptime probe, so this page does not claim an uptime figure. Success rate is not uptime.
Excluded periods
- Sep 30, 2026, 2:08 PM UTC – Oct 3, 2026, 10:02 AM UTC: No server errors were logged in this period while client errors were, so failures may not have been recorded. Excluded until verified.
Endpoint data excluded before a fix
/v1/instagram/profile-search before Oct 11, 2026, 10:15 AM UTC: Upstream failures were returned as empty results before this date.
Methodology version 1.