EchelonGraph Radar
Public Beta
PROBING · 1 REGION
Verified crawler
Observer
Signal
State
Window
Domains tracked
6,467
in the last 720h
Answered
99.40%
of 141,115 probes · not uptime · refusals included
Active incidents
open now · not live · lags probing by days
see the records ↓
Median TTFB
321ms
p95 1497 ms
Certs expiring ≤14d
271
of 5,721 domains with a certificate read · 6,467 tracked

Showing 141,115 probes across 6,467 domains, most recent 12 minutes 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

27 buckets · all observers
2026-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-10-29 — 2xx 49912026-10-30 — 2xx 49922026-10-31 — 2xx 50542026-11-01 — 2xx 47632026-11-02 — 2xx 47792026-11-03 — 2xx 49942026-11-04 — 2xx 47822026-11-05 — 2xx 47722026-11-06 — 2xx 48002026-11-07 — 2xx 47712026-11-08 — 2xx 47962026-11-09 — 2xx 47962026-11-10 — 2xx 48172026-11-11 — 2xx 47622026-11-12 — 2xx 43812026-11-13 — 2xx 222026-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-10-29 — 3xx 12026-10-30 — 3xx 12026-10-31 — 3xx 12026-11-01 — 3xx 12026-11-02 — 3xx 12026-11-03 — 3xx 12026-11-04 — 3xx 12026-11-05 — 3xx 12026-11-06 — 3xx 12026-11-07 — 3xx 12026-11-08 — 3xx 12026-11-09 — 3xx 02026-11-10 — 3xx 02026-11-11 — 3xx 02026-11-12 — 3xx 02026-11-13 — 3xx 02026-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-10-29 — 4xx 6302026-10-30 — 4xx 6652026-10-31 — 4xx 5832026-11-01 — 4xx 6282026-11-02 — 4xx 5932026-11-03 — 4xx 6172026-11-04 — 4xx 6382026-11-05 — 4xx 5952026-11-06 — 4xx 5822026-11-07 — 4xx 5922026-11-08 — 4xx 5822026-11-09 — 4xx 5762026-11-10 — 4xx 6082026-11-11 — 4xx 6102026-11-12 — 4xx 5652026-11-13 — 4xx 32026-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-10-29 — 5xx 152026-10-30 — 5xx 122026-10-31 — 5xx 162026-11-01 — 5xx 112026-11-02 — 5xx 152026-11-03 — 5xx 142026-11-04 — 5xx 162026-11-05 — 5xx 202026-11-06 — 5xx 152026-11-07 — 5xx 142026-11-08 — 5xx 152026-11-09 — 5xx 172026-11-10 — 5xx 172026-11-11 — 5xx 182026-11-12 — 5xx 162026-11-13 — 5xx 12026-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 332026-10-29 — unreached 432026-10-30 — unreached 422026-10-31 — unreached 382026-11-01 — unreached 322026-11-02 — unreached 312026-11-03 — unreached 442026-11-04 — unreached 232026-11-05 — unreached 192026-11-06 — unreached 292026-11-07 — unreached 212026-11-08 — unreached 242026-11-09 — unreached 232026-11-10 — unreached 232026-11-11 — unreached 202026-11-12 — unreached 272026-11-13 — unreached 0
2026-10-172026-10-192026-10-202026-10-212026-10-222026-10-232026-10-242026-10-252026-10-262026-10-272026-10-282026-10-292026-10-302026-10-312026-11-012026-11-022026-11-032026-11-042026-11-052026-11-062026-11-072026-11-082026-11-092026-11-102026-11-112026-11-122026-11-13

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,365 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-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
2026-10-294,99116301543
2026-10-304,99216651242
2026-10-315,05415831638
2026-11-014,76316281132
2026-11-024,77915931531
2026-11-034,99416171444
2026-11-044,78216381623
2026-11-054,77215952019
2026-11-064,80015821529
2026-11-074,77115921421
2026-11-084,79615821524
2026-11-094,79605761723
2026-11-104,81706081723
2026-11-114,76206101820
2026-11-124,38105651627
2026-11-13220310
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: 12 of 18 probes got a response.

Answered67% of 18

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 certificate43d left · GlobalSign Atlas R3 OV TLS CA 2026 Q2
TLS version1.3
Last probe46 h ago · 2026-11-11 07:05:38 UTC
Security headers
HSTSNo mixed content · not measuredSecure cookies · not measuredGrade F
Open time by observer
us-east1
3178ms
Exposure checknot measured
Domain registration2130d 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

13 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-0836RAEB
consentmanager.netanswered our probe with a server error on at least 9 consecutive probes≥92026-11-04 06:11:05 UTC9 d2026-11-12 06:13:15 UTC503Open
EGR-YWZWVCQX
avjb.comanswered our probe with a server error on at least 11 consecutive probes≥112026-11-02 06:03:19 UTC11 d2026-11-12 06:04:52 UTC500Open
EGR-VP9886H2
sexneka.comanswered our probe with a server error on at least 3 consecutive probes≥32026-10-06 06:50:11 UTC38 d2026-10-08 06:50:28 UTC521Open
EGR-ER1R4QZ1
clickr.proanswered our probe with a server error on at least 11 consecutive probes≥112026-09-11 06:01:13 UTC63 d2026-11-12 06:12:05 UTC523Open
EGR-DXJQCXSA
vix-content.netanswered our probe with a server error on at least 20 consecutive probes≥202026-09-09 07:07:25 UTC65 d2026-11-12 07:13:32 UTC521Open
EGR-8KQZA56Q
usa.govanswered our probe with a server error on at least 41 consecutive probes≥412026-09-09 07:05:43 UTC65 d2026-11-11 07:11:47 UTC503Open
EGR-0WAMY83M
otzovik.comanswered our probe with a server error on at least 23 consecutive probes≥232026-09-09 06:44:25 UTC65 d2026-10-08 06:41:32 UTC507Open
EGR-1HA53VCA
llamarpc.comanswered our probe with a server error on at least 20 consecutive probes≥202026-09-09 06:34:02 UTC65 d2026-11-12 06:39:02 UTC526Open
EGR-PJD3YR49
joporn.nameanswered our probe with a server error on at least 49 consecutive probes≥492026-09-09 06:29:54 UTC65 d2026-11-12 06:35:07 UTC503Open
EGR-AXT0SSNT
hottrumpnews.icuanswered our probe with a server error on at least 47 consecutive probes≥472026-09-09 06:25:34 UTC65 d2026-11-12 06:30:54 UTC520Open
EGR-XME8CTVX
camsite26.lolanswered our probe with a server error on at least 15 consecutive probes≥152026-09-09 06:00:48 UTC65 d2026-11-12 06:10:06 UTC520Open
EGR-RQBGQ8P8
breakingtrumpnews.icuanswered our probe with a server error on at least 48 consecutive probes≥482026-09-09 05:59:26 UTC65 d2026-11-12 06:08:51 UTC520Open
EGR-TPAWVS8N
lothar.comanswered our probe with a server error on at least 56 consecutive probes≥562026-09-07 20:48:28 UTC66 d2026-11-13 05:05:42 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-east12xx
67%
12313 ms43d12 F46 h ago
vodafone.ptus-east12xx
95%
9998 ms90dno F22 h ago
consentmanager.netus-east15xx
100%
9583 ms143d4 F23 h ago
architecturaldigest.comus-east12xx
100%
9423 ms109dno F23 h ago
directv.comus-east12xx
33%
9398 ms104d2 F10 d ago
tui.co.ukus-east1refused
100%
all refusals
9367 ms99dnot measured18 d ago
webempresa.euus-east15xx
92%
9287 ms98d20 F22 h ago
hilton.comus-east1refused
44%
all refusals
9284 ms88dnot measured10 d ago
creditkarma.comus-east12xx
100%
9151 ms160d26 F23 h ago
unifi-ai.comus-east15xx
100%
9120 ms58d1 F4 d ago
lenta.techus-east15xx
100%
8766 ms13d12 F23 h ago
news-medical.netus-east12xx
85%
8304 ms31dno F23 h ago
ikman.lkus-east12xx
96%
8068 ms31d24 F23 h ago
goal.comus-east12xx
100%
7886 ms170dno F47 h ago
fang.comus-east12xx
88%
7561 ms93d22 F23 h ago
dvr163.comus-east12xx
100%
7555 msnot measured25 F23 h ago
dcbprotect.comus-east12xx
33%
7316 ms47dno F4 d ago
clarivate.comus-east12xx
100%
7155 ms30dno F23 h ago
miui.comus-east12xx
96%
7147 ms114d25 F23 h ago
minhchinh.comus-east12xx
100%
7106 ms51d26 F23 h ago
csdn.netus-east15xx
100%
6834 ms12dnot measured23 h ago
hvg.huus-east12xx
96%
6764 ms104d25 F23 h ago
iubenda.comus-east12xx
100%
6644 ms80d26 F23 h ago
ico.org.ukus-east12xx
100%
6608 ms130dno F23 h ago
pavietnam.netus-east12xx
100%
6561 ms93d17 F22 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.