Today I'm excited to launch RegionCheck, a tool for testing, monitoring, and debugging endpoints from cloud regions around the world.
The idea is simple - test an endpoint's DNS and HTTP connectivity and response from a defined set of cloud regions.
Whether you're troubleshooting an API, validating a deployment, checking DNS propagation, or investigating latency, seeing the results from multiple cloud regions can quickly reveal issues that aren't obvious from your own machine.
What is RegionCheck?
RegionCheck lets you run endpoint checks from AWS, Azure, and Google Cloud regions without provisioning infrastructure or maintaining test instances.
Current capabilities include:
- HTTP endpoint testing
- DNS lookups
- TLS certificate validation
- Continuous monitoring with alerts
- Side-by-side comparison across cloud providers and regions
- Shareable result pages for collaboration
- API/MCP access for automation and agents
Why I built it
When debugging production issues, I often wanted to answer questions like:
- Is DNS returning the same result everywhere? Or is geo-DNS returning the results intended?
- Is TLS certificate propagation for my CDN working as intended?
- Is one region significantly slower than another? Is my CDN caching working as expected?
- Are my geo-HTTP redirects working as intended? (For some interesting examples try www.yahoo.com and www.cnn.com in non-US regions)
There are many tools that exist that provide these answers, but nothing that answers all of these questions in one place.
That's what RegionCheck aims to provide.
Who it's for
RegionCheck is designed for engineers who work with cloud infrastructure, including:
- DevOps engineers
- Site Reliability Engineers (SREs)
- Platform engineers
- Backend developers
- Anyone who likes to take a peek at backend infrastructure
Try it out
RegionCheck is available at https://regioncheck.io
You can run free checks directly from the website; or create an account to access monitoring, alerting, the API, and additional features.
I'd love your feedback
RegionCheck is just getting started, and I'd really appreciate feedback from the engineering community.