API status
The external services the Status app depends on, probed from seven regions. Endpoints, tiers and per-service targets come from the app team; each service is judged against its own target, not a shared one.
Targets are the app team's own numbers, so a 2s reading is fine for an IPFS gateway and a failure for the RPC proxy.
Europe is probed on every sweep. The other six regions take turns, one per sweep, so each is refreshed about every three hours; the time under a region says when it was last probed. Taking turns is what keeps the sweep inside Globalping's hourly quota.
Every region is judged against the same target. Those targets were not set with distance in mind, so a region far from a service can read over target while the service itself is fine.
Probes sit in data centres, so a reading shows the network path from that region rather than what a phone on a mobile network would see.
Every check runs without credentials. The Status proxies answer an unauthenticated request with 401 and the WalletConnect relay answers a plain GET with 400, and those rejections are what prove the service is alive.
Nothing here sends alerts yet. These are mostly third-party services, and a week of baseline comes before anyone gets paged about them.