IsItMe

Appearance

Quick start ​

Name a site. Read the card. That's the whole product.

1. Open the chat ​

The chat is the home page of the app.

No account, no sign-up

Your device gets a random id in localStorage, and that id owns your history, watches and alerts. Clear your browser storage and you start fresh.

2. Ask one question ​

Type it the way you'd say it. These three are the starter buttons on an empty chat:

  • Is github.com down?
  • Why is my bank site slow?
  • Watch example.com every 5 minutes

You don't have to phrase it as a question, and you don't have to paste a full URL — github.com, https://github.com/explore and "is github down for everyone" all work.

3. Watch it work ​

A card appears straight away and fills in as each step finishes. There are eleven steps:

StepWhat it is
DNS lookupthe name, via 1.1.1.1 and 8.8.8.8
Cloudflare edgean HTTP GET from the data centre nearest you
5 regionsthe same GET from US west, US east, Europe, Asia and Oceania
Outside probesthe same GET from volunteer probes outside Cloudflare (Globalping)
Cloudflare Radarknown outages and routing trouble for your network and the site's
Hosting providerwho hosts it, and whether their other sites are failing too
Status pagethe site's own status page, if it has one
Your browseryour own machine tries to load it
Crowd reportswhat other IsItMe users saw for this site recently
Verdictthe rules read the evidence and pick one of twelve answers
Explanationthe AI writes the paragraph

A whole check takes about 5–15 seconds on the hosted demo, and longer when the site itself is slow to answer — each probe allows 8 seconds, and 15 more if it has to retry. Steps that have nothing to report are marked skipped, not failed.

4. Read the card ​

github.com10.4s Healthy 95%

It's up. Not you, not them.

  • Cloudflare's edge (MXP) got HTTP 200 in 46ms
  • 5/5 regions reachable (median 61ms)
  • DNS resolved to 1 address in 2ms
  • Your browser could reach it in 495ms
  • 5 checks in the last 10 min, 0 failing
  • No ongoing Radar outages or anomalies for your network
  • All 5 outside probes reached it

The site is reachable from all locations. Your browser could reach it in 495ms. All outside probes and regions also reached it successfully.

Full report

A real run against the hosted demo, 5 October 2026.

Top to bottom:

The host and the clock. What was checked, and how long it took.

The verdict chip. One of twelve, with a confidence percentage: Healthy 95% . Some verdicts add a subtype — DNS failure · domain doesn't exist95% — which says which kind. All twelve are on Understanding results.

The headline. The verdict in one sentence. Note the honesty here: "It's up. Not you, not them." only appears when your own browser reached the site too. If the browser step didn't run, the headline is "It's up from everywhere we checked" instead — it won't claim anything about you that it didn't measure.

The signals. The plain-language facts the rules actually used, most important first. This is the part to read when you don't trust the verdict: it shows you the same evidence the rules saw, so you can disagree.

Why 95% confidence. A fold-out list of what moved the number up and down. In the run above, four agreeing vantage points and Radar data being available pushed it to the 0.95 ceiling — the highest the number is ever allowed to go.

The 24-hour sparkline. Edge response time for this host over the last day, from everyone's checks. Red ticks are failing checks; the dashed line is the usual latency, which is what "slow" gets measured against.

The explanation. Written by Llama 3.3, from the finished verdict and the evidence. It ends in two or three concrete next steps that fit the verdict — page-level fixes for a healthy site, network fixes only when the problem looks like your network. The AI never picks the verdict and is filtered for anything it invented.

The buttons.

ButtonWhat it does
Copy share linka public link to the full report, good for 30 days
Send check linka link that makes someone else's browser run the test, and shows you their result
Copy for supportthe whole thing as plain text, for pasting into a ticket
.txtthe same bundle as a file
Status badgea Markdown snippet for an always-current status badge
Stepsre-show the eleven steps
Evidencethe raw evidence table: every vantage, every answer

Sharing covers the links and the badge.

5. Try one here ​

This box calls the hosted demo's public API directly from your browser. If the call fails — a rate limit, a host it refuses — it shows the recorded example instead, and says so.

Where to go next ​