Regions & providers
RegionCheck executes each check from real cloud regions across three providers, so results reflect what users on those networks actually experience.
Where checks run
RegionCheck runs its worker code directly in each cloud region's own compute: AWS Lambda, Google Cloud Run, and Azure Container Apps. Because the check runs on the provider's own network in that region, the timings you see reflect real conditions there, not a proxy or a single central location.
RegionCheck can deploy to 95+ regions across all three providers — AWS, Google Cloud, and Azure — worldwide.
Choosing regions
You pick which specific regions to run a check from, for example checking only the regions closest to your users or every region a provider offers. How many regions you can run in a single check depends on your plan — see Plans & billing for the limits and Rate limits & quotas for how region usage is metered.
Listing regions programmatically
To get the current list of available regions and providers, call the regions endpoint. It requires no authentication:
curl -s https://regioncheck.io/api/regionsThe MCP server exposes the same data through the list_regions tool, so an agent can enumerate available regions before choosing which ones to run a check from.
A few example region codes: us-east-1, eu-west-1, ap-southeast-1. Call the endpoint above for the full, current list rather than relying on a hardcoded set.