Skip to content
ScrapeField

Status

Every endpoint, and how it is actually doing

Generated from real traffic, not written by hand. When something is degraded this page says so before you have to ask.

These numbers are from 15:06 UTC, 6 November 2026. The page reads them again each minute.

99.5%success rate, 30 days(92,545 calls)
3,978 msp50 latency(p95 7,583 ms)
45/45 operational

Google Maps

Operational
StateEndpointSuccess rateMedian time95th percentile
Operational /v1/google-maps/places Nightly test: answered in Test: 953 ms
Operational /v1/google-maps/place Nightly test: answered in Test: 576 ms
Operational /v1/google-maps/reviews Nightly test: answered in Test: 2,108 ms
Operational /v1/google-maps/photos Nightly test: answered in Test: 590 ms
Operational /v1/google-maps/posts Nightly test: answered in Test: 527 ms

LinkedIn

Operational
StateEndpointSuccess rateMedian time95th percentile
Operational /v1/linkedin/profile 99.9% 3890 ms 7719 ms
Operational /v1/linkedin/company Nightly test: answered in Test: 3,642 ms
Operational /v1/linkedin/employee-stats Nightly test: answered in Test: 2,887 ms
Operational /v1/linkedin/employees Nightly test: answered in Test: 1,709 ms
Operational /v1/linkedin/people 98.0% 3673 ms 13652 ms
Operational /v1/linkedin/services Nightly test: answered in Test: 1,620 ms
Operational /v1/linkedin/companies Nightly test: answered in Test: 775 ms
Operational /v1/linkedin/posts Nightly test: answered in Test: 4,509 ms
Operational /v1/linkedin/post Nightly test: answered in Test: 5,467 ms
Operational /v1/linkedin/comments Nightly test: answered in Test: 1,178 ms
Operational /v1/linkedin/reactions 100.0% 1792 ms 3337 ms
Operational /v1/linkedin/activity 99.4% 3658 ms 5994 ms
Operational /v1/linkedin/jobs Nightly test: answered in Test: 1,307 ms
Operational /v1/linkedin/job Nightly test: answered in Test: 2,360 ms
Operational /v1/linkedin/ads 98.4% 6460 ms 9164 ms
Operational /v1/linkedin/ad Nightly test: answered in Test: 1,580 ms
Operational /v1/linkedin/group — — —
Operational /v1/linkedin/groups Nightly test: answered in Test: 465 ms

Instagram

Operational
StateEndpointSuccess rateMedian time95th percentile
Operational /v1/instagram/profile Nightly test: answered in Test: 4,902 ms
Operational /v1/instagram/posts Nightly test: answered in Test: 2,924 ms
Operational /v1/instagram/post — — —
Operational /v1/instagram/comments — — —
Operational /v1/instagram/hashtag Nightly test: answered in Test: 4,516 ms
Operational /v1/instagram/search Nightly test: answered in Test: 17,476 ms

TikTok

Operational
StateEndpointSuccess rateMedian time95th percentile
Operational /v1/tiktok/profile Nightly test: answered in Test: 3,182 ms
Operational /v1/tiktok/followers Nightly test: answered in Test: 3,250 ms
Operational /v1/tiktok/videos Nightly test: answered in Test: 3,070 ms
Operational /v1/tiktok/video — — —
Operational /v1/tiktok/comments — — —
Operational /v1/tiktok/search Nightly test: answered in Test: 5,311 ms
Operational /v1/tiktok/trending Nightly test: answered in Test: 10,866 ms
Operational /v1/tiktok/ads Nightly test: answered in Test: 2,103 ms

X

Operational
StateEndpointSuccess rateMedian time95th percentile
Operational /v1/x/profile Nightly test: answered in Test: 3,643 ms
Operational /v1/x/posts Nightly test: answered in Test: 1,796 ms
Operational /v1/x/post Nightly test: answered in Test: 2,210 ms
Operational /v1/x/replies — — —
Operational /v1/x/retweeters — — —
Operational /v1/x/followers — — —
Operational /v1/x/search Nightly test: answered in Test: 1,768 ms
Operational /v1/x/community Nightly test: answered in Test: 2,085 ms

Columns: success rate over the last 30 days, then p50 and p95 latency. A call that fails is never charged. An endpoint with fewer than 50 calls shows our nightly test of it instead, from 03:00 UTC, 6 November 2026: whether it answered, and how long the slowest of its sources took.

How we define these

Success rate is the share of requests that returned data, over the last 30 days, excluding requests that failed because of the parameters you sent, and requests refused with a 429 because too many were in flight. A 429 costs nothing and says when to try again. A 404 for a profile that genuinely does not exist is a success: we answered the question correctly.

Latency is measured from when we start answering a request, after its key is checked, to when its answer is recorded, and excludes cache hits — which would flatter it considerably.

Whose calls. Real calls only: the no-key demo and our test accounts are left out. A call our own account makes for its own work is a real call, and counts. An endpoint shows a number once it has 50 calls in the last 30 days.

Operational means we can serve the endpoint now, and its success rate over the last 24 hours is at least 95% where it had 50 calls in that time. The state is about now; the 30 days’ success rate beside it is the record, and keeps a bad day for a month. Where we can, an endpoint is served by more than one source, so a problem at one of them is invisible to you.

Degraded means we can serve it, but its success rate over the last 24 hours is under 95%, or every source for it has just failed three times in a row and is paused for a minute, or our nightly check of it failed, or at least three calls to it failed in the last half hour. Unavailable means we cannot serve that endpoint at all — and calls to it are not charged.