Live · Beijing node · refreshed weekly
The stack, category by category.
Each page loads exactly one third-party integration the way a normal product would — so when it fails, you know precisely which layer of your stack broke.
—dependencies probed
—blocked from Beijing
—still reachable
Live verdicts
One dependency per page.
The chips below show the latest verdict straight from the most recent run. Community-submitted targets are probed over the network and marked with a badge.
Fonts & icons 3 dependencies
Auth & identity 3 dependencies
Analytics & tags 2 dependencies
Maps, media, embeds 3 dependencies
Missing a dependency you ship? Submit a target Vote: which SaaS next?
Verdict color code
Reachable < 1s
Degraded 1–3s
Blocked > 3s or connection failed
Measured as total request time from the Beijing node; any HTTP status counts as connected.
Go deeper
See what whole platforms cost you.
Firebase, Netlify, and Vercel — deployed for real and probed end to end from the same Beijing node. Or run the probes yourself; every script is open source.