Skip to main content
Checkly logo

Is Checkly Down?

No — Checkly is up

Reachable from all 8 checked regions

Average response time: 260ms

Last checked · checks run every 6 hours

Official status page: https://is.checkly.online

Checkly uptime

100%
Last 7 days
99.69%
Last 30 days
99.69%
Last 90 days
204ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 12 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

9-day clean streak
Aug 12: no data
Aug 13: no data
Aug 14: no data
Aug 15: no data
Aug 16: no data
Aug 17: no data
Aug 18: no data
Aug 19: no data
Aug 20: no data
Aug 21: no data
Aug 22: no data
Aug 23: no data
Aug 24: no data
Aug 25: no data
Aug 26: no data
Aug 27: no data
Aug 28: no data
Aug 29: no data
Aug 30: 100.00% uptime, 16 checks
Aug 31: 100.00% uptime, 32 checks
Sep 1: 96.88% uptime, 32 checks
Sep 2: 100.00% uptime, 32 checks
Sep 3: 100.00% uptime, 32 checks
Sep 4: 100.00% uptime, 29 checks
Sep 5: 100.00% uptime, 21 checks
Sep 6: 100.00% uptime, 31 checks
Sep 7: 100.00% uptime, 32 checks
Sep 8: 100.00% uptime, 24 checks
Sep 9: 100.00% uptime, 32 checks
Sep 10: 100.00% uptime, 8 checks
Aug 12 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
109ms
DNS 20ms TCP 2ms TLS 20ms TTFB 89ms
arn
164ms
DNS 108ms TCP 1ms TLS 11ms TTFB 156ms
nrt
231ms
DNS 17ms TCP 4ms TLS 65ms TTFB 211ms
ord
175ms
DNS 50ms TCP 1ms TLS 61ms TTFB 158ms
sin
231ms
DNS 158ms TCP 1ms TLS 9ms TTFB 224ms
sjc
63ms
DNS 6ms TCP 0ms TLS 12ms TTFB 54ms
syd
861ms
DNS 809ms TCP 0ms TLS 7ms TTFB 852ms
yyz
249ms
DNS 80ms TCP 11ms TLS 41ms TTFB 198ms

What Checkly does

Checkly is a synthetic monitoring platform for developers. It runs API checks, browser checks scripted in Playwright, multistep checks and heartbeat checks from managed or private locations, then alerts when one fails. Teams wire it into deployment pipelines so a bad release trips a check before customers notice, which makes it a dependency for release confidence.

What an outage looks like

The clearest sign is silence. Checks stop reporting and alerts stop arriving, which looks identical to everything being healthy. Checkly separates Check Scheduler from the individual runtimes, so scheduling can stall while the Browser, API, Multistep, Playwright and Heartbeat runtimes are fine. Public Dashboards and Alerting are their own components, so a hosted status page can go dark on its own.

What to do about it

Check is.checkly.online, which publishes per-component uptime next to the current state. Match the failing row to what you depend on: Alerting down means nobody is being paged even though checks still run, and Check Scheduler down means nothing is running at all. Treat the window as unmonitored rather than healthy, and confirm production separately before trusting a quiet dashboard.

Is it down for everyone, or just you?

If this page says Checkly is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Datadog
Datadog
New Relic
New Relic
Sentry
Sentry
Grafana Cloud
Grafana Cloud

Checkly outage FAQ

My Checkly dashboard is all green. Could Checkly itself be down?
Yes, and this is the failure mode worth understanding. If Check Scheduler stalls, checks stop running rather than failing, so the last known state stays on screen and looks like health. Read is.checkly.online rather than your own dashboard during any suspected incident, and treat a period with no new results as unmonitored time.
Does a Checkly outage mean my alerts stopped?
It can, independently of whether checks are running. Checkly reports Alerting as a component separate from the check runtimes, so checks can execute and record failures while notifications do not go out. If the Alerting row is the affected one, watch your check results directly for the duration instead of waiting to be paged.
Only some of my checks are failing. Is that a Checkly problem?
Look at which runtime they use. Checkly reports Browser check runtime, API Check Runtime, Multistep check runtime, Playwright check runtime and Heartbeat check as separate components, so an incident can affect browser checks while API checks run normally. Group your failing checks by type first, because a single-runtime incident looks like a targeted application fault.
Do private locations keep working during a Checkly outage?
Private Location is its own component on the status page, tracked apart from the hosted runtimes, so the two can diverge. Checks running from your own infrastructure still depend on Checkly for scheduling and for recording results, so a Check Scheduler incident affects them as well even though the runner is yours.
Is my Checkly-hosted status page affected too?
Public Dashboards is reported as a separate component, so a status page you publish through Checkly can be unavailable while your checks keep running normally, or the reverse. If you point customers at a Checkly-hosted dashboard, check that row specifically during an incident, because your own outage communication may be the part that is down.

How we measure this

  • We request Checkly's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Checkly publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Checkly goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required