EchelonGraph Radar
Public Beta
PROBING · 1 REGION
Verified crawler
Observer
Signal
State
Window
Domains tracked
6,511
in the last 720h
Answered
99.29%
of 125,809 probes · not uptime · refusals included
Active incidents
open now · not live · lags probing by days
see the records ↓
Median TTFB
305ms
p95 1487 ms
Certs expiring ≤14d
303
of 5,768 domains with a certificate read · 6,511 tracked

Showing 125,809 probes across 6,511 domains, most recent 12 hours ago. Scheduled probing is live and the registry is still being walked, so this count rises between refreshes.

Cross-region latency

median TTFB · answering edge ▾ × observer ▸

This grid needs two axes and we have one. The columns are the regions we observe from, and one is deployed. The rows are where the answering address is announced, which nothing measures yet — that is #1735, and it is the only Radar data need that is genuinely unmeasured rather than merely unread.

It will say “answering edge” rather than “hosted”, because for a site behind a content delivery network those are different places and only one of them is true.

fastslow

Status-code distribution

22 buckets · all observers
2026-09-28 — 2xx 53972026-09-29 — 2xx 53942026-09-30 — 2xx 53812026-10-01 — 2xx 53592026-10-02 — 2xx 53862026-10-03 — 2xx 53772026-10-04 — 2xx 54202026-10-05 — 2xx 53872026-10-06 — 2xx 53732026-10-07 — 2xx 53952026-10-08 — 2xx 53842026-10-17 — 2xx 53652026-10-19 — 2xx 49612026-10-20 — 2xx 47872026-10-21 — 2xx 45452026-10-22 — 2xx 45642026-10-23 — 2xx 43802026-10-24 — 2xx 44172026-10-25 — 2xx 45832026-10-26 — 2xx 47192026-10-27 — 2xx 48102026-10-28 — 2xx 47872026-09-28 — 3xx 22026-09-29 — 3xx 12026-09-30 — 3xx 22026-10-01 — 3xx 22026-10-02 — 3xx 22026-10-03 — 3xx 12026-10-04 — 3xx 12026-10-05 — 3xx 12026-10-06 — 3xx 12026-10-07 — 3xx 12026-10-08 — 3xx 12026-10-17 — 3xx 12026-10-19 — 3xx 12026-10-20 — 3xx 12026-10-21 — 3xx 12026-10-22 — 3xx 12026-10-23 — 3xx 12026-10-24 — 3xx 12026-10-25 — 3xx 12026-10-26 — 3xx 12026-10-27 — 3xx 12026-10-28 — 3xx 12026-09-28 — 4xx 6272026-09-29 — 4xx 6132026-09-30 — 4xx 6312026-10-01 — 4xx 6392026-10-02 — 4xx 6142026-10-03 — 4xx 6342026-10-04 — 4xx 6032026-10-05 — 4xx 6262026-10-06 — 4xx 6212026-10-07 — 4xx 6202026-10-08 — 4xx 5772026-10-17 — 4xx 6302026-10-19 — 4xx 6032026-10-20 — 4xx 6082026-10-21 — 4xx 5802026-10-22 — 4xx 6072026-10-23 — 4xx 5842026-10-24 — 4xx 5642026-10-25 — 4xx 5872026-10-26 — 4xx 6232026-10-27 — 4xx 6132026-10-28 — 4xx 6172026-09-28 — 5xx 152026-09-29 — 5xx 172026-09-30 — 5xx 132026-10-01 — 5xx 152026-10-02 — 5xx 122026-10-03 — 5xx 142026-10-04 — 5xx 162026-10-05 — 5xx 132026-10-06 — 5xx 182026-10-07 — 5xx 162026-10-08 — 5xx 162026-10-17 — 5xx 172026-10-19 — 5xx 112026-10-20 — 5xx 112026-10-21 — 5xx 112026-10-22 — 5xx 112026-10-23 — 5xx 82026-10-24 — 5xx 112026-10-25 — 5xx 192026-10-26 — 5xx 132026-10-27 — 5xx 122026-10-28 — 5xx 122026-09-28 — unreached 522026-09-29 — unreached 472026-09-30 — unreached 392026-10-01 — unreached 512026-10-02 — unreached 412026-10-03 — unreached 402026-10-04 — unreached 382026-10-05 — unreached 482026-10-06 — unreached 372026-10-07 — unreached 412026-10-08 — unreached 432026-10-17 — unreached 402026-10-19 — unreached 342026-10-20 — unreached 332026-10-21 — unreached 362026-10-22 — unreached 422026-10-23 — unreached 382026-10-24 — unreached 312026-10-25 — unreached 452026-10-26 — unreached 512026-10-27 — unreached 302026-10-28 — unreached 33
2026-09-282026-09-292026-09-302026-10-012026-10-022026-10-032026-10-042026-10-052026-10-062026-10-072026-10-082026-10-172026-10-192026-10-202026-10-212026-10-222026-10-232026-10-242026-10-252026-10-262026-10-272026-10-28

Vertical scale is logarithmic, so a line twice as high is far more than twice as many — it is the only way 1 server error and 5,420 successes fit on one chart. The exact counts are in the table below; hovering the chart shows the same five numbers for whichever bucket is under the pointer.

Exact counts behind the chart, per bucket
bucket (UTC)2xx3xx4xx5xxunreached
2026-09-285,39726271552
2026-09-295,39416131747
2026-09-305,38126311339
2026-10-015,35926391551
2026-10-025,38626141241
2026-10-035,37716341440
2026-10-045,42016031638
2026-10-055,38716261348
2026-10-065,37316211837
2026-10-075,39516201641
2026-10-085,38415771643
2026-10-175,36516301740
2026-10-194,96116031134
2026-10-204,78716081133
2026-10-214,54515801136
2026-10-224,56416071142
2026-10-234,3801584838
2026-10-244,41715641131
2026-10-254,58315871945
2026-10-264,71916231351
2026-10-274,81016131230
2026-10-284,78716171233
2xx success3xx redirect4xx client5xx serverunreached

Unreached counts probes that produced no response at all, so the status columns do not sum to the probe count.

Domain detail

tencent.com
T
tencent.com
200

The most recent probe in this window answered 200. Answered below counts every probe in the window: 11 of 16 probes got a response.

Answered69% of 16

This says how often we got an answer, not whether the site works. A refusal is a response, so a refused probe counts as answered.

TLS certificate58d left · GlobalSign Atlas R3 OV TLS CA 2026 Q2
TLS version1.3
Last probe36 h ago · 2026-10-27 07:05:06 UTC
Security headers
HSTSNo mixed content · not measuredSecure cookies · not measuredGrade F
Open time by observer
us-central1 → us-east1
3531ms
Exposure checknot measured
Domain registration2146d left · MarkMonitor Information Technology (Shanghai) Co., Ltd.
Email recordsSPF hardfail · DMARC quarantine
Full detailopen ↗

Most recently probed

newest first · one line per domain
reading the newest probes…

Open incidents

14 listed · not live · lags probing by days

Re-check is under each open record's id. Re-checks are switched off on our main platform, which takes the request: it has its on-demand checks of the hosts we report on switched off, and keeps re-checks off while Radar's prober runs again, so the re-check button sends nothing. When re-checks are switched back on, a re-check sends the host one more probe from us, now, and records what it answers: if it answers without a server error the incident closes, and if it still answers with one the incident stays open. Nobody can close an incident by asking — only the probe's answer can. Anyone may ask for a re-check, but only of a host with an open incident here, and each host can be re-checked at most once an hour — and not within an hour of our ordinary probe of it: one hour shared by everyone asking, because the limit is there to protect the host.

IncidentDomainWhat we measuredFailuresOpen sinceDurationNewest failing scheduled probeNewest failing statusState
EGR-V3B8RN08
delegaciondelgobierno.gob.esanswered our probe with a server error on at least 3 consecutive probes≥32026-10-26 06:13:41 UTC3 d2026-10-28 06:13:43 UTC500Open
EGR-VP9886H2
sexneka.comanswered our probe with a server error on at least 3 consecutive probes≥32026-10-06 06:50:11 UTC23 d2026-10-08 06:50:28 UTC521Open
EGR-ER1R4QZ1
clickr.proanswered our probe with a server error on at least 3 consecutive probes≥32026-09-11 06:01:13 UTC48 d2026-09-15 05:56:38 UTC521Open
EGR-DXJQCXSA
vix-content.netanswered our probe with a server error on at least 5 consecutive probes≥52026-09-09 07:07:25 UTC50 d2026-10-28 07:13:06 UTC521Open
EGR-8KQZA56Q
usa.govanswered our probe with a server error on at least 27 consecutive probes≥272026-09-09 07:05:43 UTC50 d2026-10-28 07:11:16 UTC503Open
EGR-6H87DF6B
tribalfusion.comanswered our probe with a server error on at least 34 consecutive probes≥342026-09-09 07:02:37 UTC50 d2026-10-28 07:07:53 UTC503Open
EGR-0WAMY83M
otzovik.comanswered our probe with a server error on at least 23 consecutive probes≥232026-09-09 06:44:25 UTC50 d2026-10-08 06:41:32 UTC507Open
EGR-1HA53VCA
llamarpc.comanswered our probe with a server error on at least 5 consecutive probes≥52026-09-09 06:34:02 UTC50 d2026-10-28 06:38:41 UTC526Open
EGR-PJD3YR49
joporn.nameanswered our probe with a server error on at least 34 consecutive probes≥342026-09-09 06:29:54 UTC50 d2026-10-28 06:34:31 UTC503Open
EGR-AXT0SSNT
hottrumpnews.icuanswered our probe with a server error on at least 32 consecutive probes≥322026-09-09 06:25:34 UTC50 d2026-10-28 06:29:55 UTC520Open
EGR-XPEP5D2Y
geoipcheck.comanswered our probe with a server error on at least 34 consecutive probes≥342026-09-09 06:17:11 UTC50 d2026-10-28 06:23:39 UTC502Open
EGR-XME8CTVX
camsite26.lolanswered our probe with a server error on at least 3 consecutive probes≥32026-09-09 06:00:48 UTC50 d2026-09-13 05:59:20 UTC520Open
EGR-RQBGQ8P8
breakingtrumpnews.icuanswered our probe with a server error on at least 33 consecutive probes≥332026-09-09 05:59:26 UTC50 d2026-10-28 06:06:22 UTC520Open
EGR-TPAWVS8N
lothar.comanswered our probe with a server error on at least 40 consecutive probes≥402026-09-07 20:48:28 UTC51 d2026-10-28 05:02:36 UTC500Open

Each record is one thing we measured: the host answered our probe — one request, from one vantage point — with a server error on the stated number of consecutive probes. It says nothing about what anyone else sees from anywhere else.

The status is the HTTP status the host answered our newest failing probe of that run with — 503, say. It is that one response to that one request, not a summary of the run, and not the newest probe's status: a host that has since answered normally still shows the status of the last probe that failed. A record that reads "not recorded" was opened before we began keeping it and has not failed again since; that is an absence of a measurement, not a status of zero. The run is our scheduled probes: a re-check asked for from this page that fails is not added to it — not to the count, not to the newest failing probe, not to its status — and one that gets an answer closes the record.

Hosts we could not reach at all are not listed. Their incidents are recorded separately and not published here, because from one vantage point a host nobody can reach and a host refusing our prober look the same, and naming one as the other would be a false claim about a working site. So this list is a floor: it can only under-count.

Not live: an incident opens only after 2 failing probes in a row and the estate is swept in passes days apart, so a record appears here days after the errors begin, and a close appears only when a later probe succeeds.

This list is read when the page is rendered and does not follow the board's refresh; the page is rendered again once its copy is two minutes old, or as soon as a re-check made here closes a record, and a reload after that re-reads it.

Select for monitoringRegionAction
tencent.comus-central1 → us-east12xx
69%
12313 ms58d11 F36 h ago
bytedance.comus-central1 → us-east12xx
86%
11911 ms133dno F13 h ago
lazada.comus-central1 → us-east12xx
86%
9925 ms58dno F13 h ago
webempresa.euus-central1 → us-east12xx
95%
9702 ms112d21 F12 h ago
creditkarma.comus-central1 → us-east12xx
100%
9626 ms13d22 F13 h ago
consentmanager.netus-central1 → us-east12xx
100%
9583 ms143d14 F8 d ago
claro.com.brus-central1 → us-east12xx
90%
9513 ms62dno F13 h ago
miui.comus-central1 → us-east12xx
80%
9463 ms129d16 F13 h ago
directv.comus-central1 → us-east12xx
50%
9371 ms116d4 F3 d ago
tui.co.ukus-central1 → us-east1refused
60%
all refusals
9367 ms99dnot measured3 d ago
hilton.comus-central1 → us-east1refused
50%
all refusals
9273 ms97dnot measured3 d ago
farfetch.comus-central1 → us-east12xx
83%
3 refusals
9201 ms129dno F10 d ago
ctvnews.caus-central1 → us-east12xx
100%
8974 ms24dno F3 d ago
ziare.comus-central1 → us-east12xx
86%
8906 ms34d19 F12 h ago
surriel.comus-central1 → us-east12xx
100%
2 refusals
8476 ms55d15 F12 h ago
telangana.gov.inus-central1 → us-east12xx
50%
8119 ms43dno F12 h ago
fang.comus-central1 → us-east12xx
91%
7561 ms108d20 F13 h ago
dvr163.comus-central1 → us-east12xx
100%
7555 msnot measured21 F13 h ago
inkscape.orgus-central1 → us-east15xx
68%
7429 ms30d13 F13 h ago
architecturaldigest.comus-central1 → us-east12xx
100%
7423 ms124dno F13 h ago
hvg.huus-central1 → us-east12xx
95%
7165 ms119d18 F13 h ago
clarivate.comus-central1 → us-east12xx
100%
7155 ms30dno F13 h ago
kimi.comus-central1 → us-east12xx
100%
7144 ms36d21 F13 h ago
mogujie.comus-central1 → us-east12xx
88%
6884 ms164d7 F6 d ago
readthedocs.ious-central1 → us-east12xx
100%
6853 ms33d17 F12 h ago
◆ Live data · one region · scheduled probing liveActive probing only — EchelonGraph measures its own requests to public endpoints. No packet interception, no third-party traffic.Status is the family of each probe's final response. "refused" means every response over the last 30 days was 403 or 429 — an answer, not a failure to answer; we do not record what made it. "unreached" means no probe got a response. Answered is how often a probe got any response. A refusal is a response, so a refused probe counts as answered. It does not say whether the site works.