elele.DNS

showing last 24 hours

fixed range

Friction

Most blocking is invisible: a name is refused once and the client moves on. This is the part that was not: where something asked again, and again, because it did not get what it wanted.

Blocked lookups
0

after fan-out

Accepted first time
0

95.9% of episodes

Retries
0

across 225 episodes

Longest episode
0×

consecutive lookups, one name

asked once, dropped
5,227 · 95.9%
asked twice
205 · 3.8%
three times or more
20 · 0.4%
5,733 blocked lookups, gathered into 5,452 episodes. 95.9% were asked for once and never mentioned again and cost nothing: that is the filtering working invisibly. The rest were asked again within 20 seconds, which means something did not accept the answer. Every blocked row is in the explorer; the ranking below is only the part that was fought over.

Fought over

28 names retried across 8 devices

Ranked by retries: the number of times a client asked again after being refused. Each row opens the worst episode it produced, at the second it happened.

Which things are doing it

One misbehaving client and a blocklist that is too aggressive look identical in a total. They look nothing alike here, and they have different answers: reinstall the app, or reconsider the rule.

How this is measured

One name resolved by one device produces several rows: A, AAAA and often HTTPS, milliseconds apart. Rows within 300ms of each other are counted as one lookup. On this store that removes about two rows in five, so without it every figure here would be close to double.

Consecutive lookups of the same name by the same device, each within 20s of the last, are one episode. Everything past the first lookup in an episode is a retry. A retry means a client did not accept the answer. It does not, on its own, mean a person was waiting on it.