SUBNET.IM

66.225.192.0/18

DEFT.COMAS23352

At a glance

Addresses

16,384

/18 block

Visibility

98%

78 of 80 vantage points

RPKI

No ROA

Registry

ARINUS

Allocated 10th June 2003

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to London, UK.

OriginVantage point · London, UK
One AS path to 66.225.192.0/18 as seen from London, UK, read outward from the origin: AS23352 → AS6461 → AS8529. Each hop is listed with its network name beneath the graph.AS23352DEFT.COMOriginAS6461Zayo BandwidthAS8529Zain Omantel Inte…

Seen from London, UK

  1. 1AS23352DEFT.COMUSOrigin
    Peer of AS23352seen on 15,784 paths from 118 vantage points
  2. 2AS6461Zayo BandwidthUS
    Peer of AS6461seen on 45,651 paths from 2 vantage points
  3. 3AS8529Zain Omantel International FZ-LLCAEVantage point

One path, hop by hop, from the origin outward to the vantage point that saw it. Counts beside each step are how often we see that pair adjacent anywhere in the table, not how often this path was used — BGP carries no traffic figures.

Every path we see

  1. Oregon, US2335220130This path
  2. London, UK2335264618529Shown above
  3. Amsterdam23352646134549213151This path
  4. Sao Paulo2335264613356266213This path
  5. Singapore2335264618966132337This path

Each row is one path genuinely present in the routing table at our last snapshot, read outward from the origin to the vantage point that saw it. Open a row to follow that one path hop by hop. A heavier line in the graph means more vantage points reach the prefix that same way.

Route visibility

98%

Seen by 78 of 80 full-feed vantage points

Globally propagated

Observed at 5 of our collectors.

What this percentage counts

The denominator counts only full-feed peers — peers carrying a substantially complete routing table at the moment of the snapshot. IXP route-server peers usually feed partial tables and are excluded, because including them would make a normally propagated prefix look as though half the internet could not see it.

It measures how widely an announcement has spread across the networks we can observe. It says nothing about whether the prefix is reachable from any particular place, or how it performs.

Registry and RPKI

RIR
ARIN — North America
Country
United States
Allocated
10th June 2003
Allocation block
66.225.192.0/18
Status
allocated
Origin validation
No ROA

No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

CoveringMore specific
Prefix hierarchy for 66.225.192.0/18: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.66.225.192.0/18AS23352This prefix66.225.216.0/22AS2335266.225.194.0/23AS3635266.225.206.0/23AS39371366.225.210.0/23AS2335266.225.228.0/23AS19318+19 more

Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.

Covering announcements

No less specific announcement covers this prefix.

Sibling prefixes

No prefix of the same length in the same parent block is announced.

History

  1. AS2335212th August 2026 — present
Why these dates start where they do

A first-seen date is the first time we saw that origin, not the first time it appeared in BGP. Our history is forward-only with no backfill, so it says nothing about the period before we started collecting — treat the earliest dates with suspicion.

Open 66.225.192.0/18 in the calculator/18 reference

Routing data derived from RouteViews MRT archives and public registry data.