Status

Measured endpoint health

Real success rate and typical response time across active FastFetchz endpoints.

Last 7 days

93.9%

49 customer calls measured

Degraded

All endpoints

Every billable call across the catalog

Last hour

—

Last 24 hours

not enough traffic · 4.9s typical · 12 calls

Last 7 days

93.9% success · 5.9s typical · 49 calls

Degraded

Social endpoints

Instagram, TikTok, YouTube, Facebook, LinkedIn, X / Twitter, Reddit, Threads

Last hour

—

Last 24 hours

not enough traffic · 4.9s typical · 12 calls

Last 7 days

93% success · 6.0s typical · 43 calls

Degraded
5 groups had insufficient traffic in these windows

Commerce, Ads intelligence, Music & audio, Link in bio & storefronts, Search & Local

How we measure this

Success rate and typical response time are computed from our own request logs, grouped by catalog category, over the last hour, the last 24 hours and the last 7 days. The short windows surface a live incident; the 7-day window is where lower-volume groups reach a reportable sample. Figures cover customer traffic only: our own testing and audit accounts, withdrawn services, and rate-limited or insufficient-credit responses are all excluded — they describe our staff or an account, not an endpoint. Below 20 calls in a window we publish no percentage, because at that size it is noise rather than a measurement.

This page is served by the same infrastructure it reports on, so it is not an independent oracle: if the API is unreachable, this page may be too. Your own per-request status codes and latency are always in your dashboard request logs.

Incident notes

No open incidents. Anything we are actively investigating is posted here, with the affected groups named.

.

Report an issue