Downtime Detector

Availability measurement methodology

Every 10 minutes, Checkly sends a real request from N. Virginia and Frankfurt to a published endpoint for each service and records the response status, response time, and timing breakdown. The results measure that probe—not every feature of the provider.

Measure the service, not complaints

Each result comes from a scheduled synthetic check. It is not inferred from social posts, support tickets, or user reports.

Probe a meaningful endpoint

Where possible, the check targets the API, registry, or application endpoint developers actually depend on—not a marketing homepage.

Publish the target and limitations

Every service page names the endpoint being checked. A passing probe proves that endpoint responded; it does not prove every feature or region of the provider is healthy.

How to read a result

A probe is evidence about one endpoint from specific locations at a specific time.

A successful response means the published endpoint answered the configured request. A failed response means the check could not complete successfully after its configured retry behavior. Regional or feature-specific incidents can exist while this probe remains healthy.

The availability pages are informational and are not the service provider’s official status page. Confirm incidents against the provider’s own status page and your application telemetry.

Browse live availabilityHow Checkly monitors uptime