EchelonGraph Radar
Public Beta
PROBING · 1 REGION
Verified crawler
Observer
Signal
State
Window
Domains tracked
7,133
in the last 720h
Answered
99.29%
of 41,358 probes · not uptime · refusals included
Active incidents
open now · not live · lags probing by days
see the records ↓
Median TTFB
353ms
p95 1525 ms
Certs expiring ≤14d
164
of 6,194 domains with a certificate read · 7,133 tracked

Showing 41,358 probes across 7,133 domains, most recent 8 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

13 buckets · all observers
2026-09-07 — 2xx 262026-09-08 — 2xx 7542026-09-09 — 2xx 64172026-09-10 — 2xx 1632026-09-11 — 2xx 56102026-09-12 — 2xx 7292026-09-13 — 2xx 56902026-09-14 — 2xx 5862026-09-15 — 2xx 53702026-09-16 — 2xx 55992026-09-17 — 2xx 1662026-09-18 — 2xx 55272026-09-19 — 2xx 262026-09-07 — 3xx 02026-09-08 — 3xx 02026-09-09 — 3xx 12026-09-10 — 3xx 02026-09-11 — 3xx 02026-09-12 — 3xx 02026-09-13 — 3xx 02026-09-14 — 3xx 02026-09-15 — 3xx 02026-09-16 — 3xx 12026-09-17 — 3xx 02026-09-18 — 3xx 22026-09-19 — 3xx 02026-09-07 — 4xx 32026-09-08 — 4xx 02026-09-09 — 4xx 10462026-09-10 — 4xx 132026-09-11 — 4xx 7582026-09-12 — 4xx 982026-09-13 — 4xx 6262026-09-14 — 4xx 592026-09-15 — 4xx 4882026-09-16 — 4xx 5852026-09-17 — 4xx 82026-09-18 — 4xx 5782026-09-19 — 4xx 12026-09-07 — 5xx 12026-09-08 — 5xx 02026-09-09 — 5xx 292026-09-10 — 5xx 22026-09-11 — 5xx 212026-09-12 — 5xx 52026-09-13 — 5xx 192026-09-14 — 5xx 52026-09-15 — 5xx 182026-09-16 — 5xx 142026-09-17 — 5xx 22026-09-18 — 5xx 182026-09-19 — 5xx 12026-09-07 — unreached 02026-09-08 — unreached 12026-09-09 — unreached 532026-09-10 — unreached 22026-09-11 — unreached 442026-09-12 — unreached 82026-09-13 — unreached 492026-09-14 — unreached 32026-09-15 — unreached 472026-09-16 — unreached 402026-09-17 — unreached 12026-09-18 — unreached 452026-09-19 — unreached 0
2026-09-072026-09-082026-09-092026-09-102026-09-112026-09-122026-09-132026-09-142026-09-152026-09-162026-09-172026-09-182026-09-19

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 6,417 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-07260310
2026-09-087540001
2026-09-096,41711,0462953
2026-09-1016301322
2026-09-115,61007582144
2026-09-1272909858
2026-09-135,69006261949
2026-09-1458605953
2026-09-155,37004881847
2026-09-165,59915851440
2026-09-171660821
2026-09-185,52725781845
2026-09-19260110
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

webempresa.eu
W
webempresa.eu
no response
Answered83% of 6
TLS certificatenot measured
TLS versionnot measured
Last probe22 h ago · 2026-09-18 07:03:49 UTC
Security headers
HSTSNo mixed contentSecure cookiesGrade
Open time by observer
us-central1
10007ms
Exposure checknot measured
Full detailopen ↗

Most recently probed

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

Open incidents

18 listed · not live · lags probing by days
IncidentDomainWhat we measuredFailuresOpen sinceDurationLast failureNewest failing statusState
EGR-GM98KC96a2hosting.comanswered our probe with a server error on at least 2 consecutive probes≥22026-09-16 05:49:40 UTC3 d2026-09-17 05:49:42 UTC521Open
EGR-9HJR2Y6Epconline.com.cnanswered our probe with a server error on at least 3 consecutive probes≥32026-09-15 06:37:18 UTC4 d2026-09-18 06:41:48 UTC503Open
EGR-ER1R4QZ1clickr.proanswered our probe with a server error on at least 3 consecutive probes≥32026-09-11 06:01:13 UTC8 d2026-09-15 05:56:38 UTC521Open
EGR-C7MTMJFWamazon.com.mxanswered our probe with a server error on at least 6 consecutive probes≥62026-09-11 05:50:55 UTC8 d2026-09-18 05:51:22 UTC503Open
EGR-DXJQCXSAvix-content.netanswered our probe with a server error on at least 4 consecutive probes≥42026-09-09 07:07:25 UTC10 d2026-09-15 06:58:23 UTC521Open
EGR-8KQZA56Qusa.govanswered our probe with a server error on at least 6 consecutive probes≥62026-09-09 07:05:43 UTC10 d2026-09-18 07:01:10 UTC503Open
EGR-6H87DF6Btribalfusion.comanswered our probe with a server error on at least 6 consecutive probes≥62026-09-09 07:02:37 UTC10 d2026-09-18 06:58:02 UTC503Open
EGR-0CFY2HHVspot.imanswered our probe with a server error on at least 6 consecutive probes≥62026-09-09 06:56:47 UTC10 d2026-09-18 06:52:26 UTC502Open
EGR-0WAMY83Motzovik.comanswered our probe with a server error on at least 6 consecutive probes≥62026-09-09 06:44:25 UTC10 d2026-09-18 06:40:33 UTC507Open
EGR-1HA53VCAllamarpc.comanswered our probe with a server error on at least 4 consecutive probes≥42026-09-09 06:34:02 UTC10 d2026-09-15 06:26:03 UTC526Open
EGR-PJD3YR49joporn.nameanswered our probe with a server error on at least 6 consecutive probes≥62026-09-09 06:29:54 UTC10 d2026-09-18 06:26:28 UTC503Open
EGR-YZ6HFN5Zintentiq.comanswered our probe with a server error on at least 6 consecutive probes≥62026-09-09 06:27:59 UTC10 d2026-09-18 06:24:37 UTC500Open
EGR-AXT0SSNThottrumpnews.icuanswered our probe with a server error on at least 6 consecutive probes≥62026-09-09 06:25:34 UTC10 d2026-09-18 06:22:05 UTC520Open
EGR-XPEP5D2Ygeoipcheck.comanswered our probe with a server error on at least 6 consecutive probes≥62026-09-09 06:17:11 UTC10 d2026-09-18 06:13:48 UTC502Open
EGR-W10BTDPFcsdn.netanswered our probe with a server error on at least 6 consecutive probes≥62026-09-09 06:05:37 UTC10 d2026-09-18 06:03:02 UTC521Open
EGR-XME8CTVXcamsite26.lolanswered our probe with a server error on at least 3 consecutive probes≥32026-09-09 06:00:48 UTC10 d2026-09-13 05:59:20 UTC520Open
EGR-RQBGQ8P8breakingtrumpnews.icuanswered our probe with a server error on at least 6 consecutive probes≥62026-09-09 05:59:26 UTC10 d2026-09-18 05:57:43 UTC520Open
EGR-TPAWVS8Nlothar.comanswered our probe with a server error on at least 11 consecutive probes≥112026-09-07 20:48:28 UTC11 d2026-09-19 04:55:39 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.

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; reload to re-read it.

Select for monitoringRegionAction
webempresa.euus-central12xx
83%
14611 ms154d5 F22 h ago
youdao.comus-central12xx
100%
10068 ms43d6 F22 h ago
kemenag.go.idus-central12xx
100%
10032 ms139dno F23 h ago
hexun.comus-central12xx
100%
9891 ms182dno F23 h ago
sexindrag.comus-central12xx
100%
9799 ms75d6 F22 h ago
directv.comus-central12xx
100%
9621 ms147d5 F23 h ago
hilton.comus-central1refused
50%
all refusals
9485 ms131dnot measured23 h ago
shorturl.atus-central12xx
100%
9441 ms31dno F22 h ago
lastpass.comus-central12xx
100%
9367 ms36dno F23 h ago
lilithgame.comus-central12xx
100%
9365 ms28d6 F23 h ago
miui.comus-central12xx
100%
9118 ms169d5 F22 h ago
udyamregistration.gov.inus-central12xx
100%
8988 msnot measured5 F22 h ago
gismeteo.kzus-central12xx
100%
8621 ms166d2 F6 d ago
thinkingdata.cnus-central12xx
100%
8578 ms48d6 F22 h ago
farfetch.comus-central12xx
75%
8327 ms160dno F23 h ago
hatena.ne.jpus-central12xx
100%
8197 ms164d6 F23 h ago
ctvnews.caus-central12xx
100%
8182 ms62dno F23 h ago
cwi.nlus-central12xx
100%
8090 ms142dno F23 h ago
amazonaws.com.cnus-central12xx
100%
7829 ms69d7 F23 h ago
telangana.gov.inus-central12xx
100%
7790 ms63dno F22 h ago
creditkarma.comus-central12xx
100%
7748 ms33d6 F23 h ago
ushmm.orgus-central12xx
100%
7737 ms170dno F22 h ago
carwale.comus-central12xx
100%
7569 ms53dno F23 h ago
annas-archive.glus-central12xx
100%
7494 ms36dno F23 h ago
sandai.netus-central12xx
100%
7389 ms90d6 F22 h ago
◆ Live data · one region · scheduled probing pausedActive 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.