SUBNET.IM

72.96.0.0/11

Verizon BusinessAS22394

At a glance

Addresses

2,097,152

/11 block

Visibility

98%

78 of 80 vantage points

RPKI

Valid

Registry

ARINUS

Allocated 28th June 2005

AS paths to this prefix

One real path per vantage point, fanning out from the origin. Where two reach the prefix the same way, those hops are drawn once. Open a path to follow it hop by hop.

OriginVantage points
AS path graph: 5 observed paths to 72.96.0.0/11, fanning out from AS22394 toward the vantage points that see it. Each path is written out in full beneath the graph.AS22394Verizon BusinessOriginAS701Verizon BusinessAS1299Arelion (fka. Tel…AS8529Zain Omantel Inte…AS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…AS132337AxclusiveAS6939Hurricane Electri…AS20130Depaul UniversityAS174Cogent Communicat…AS34549meerfarbig GmbH &…AS213151Christian Elsen
  1. London, UK2239470112998529This path
  2. Sao Paulo223947013356266213This path
  3. Singapore223947011299132337This path
  4. Oregon, US22394701693920130This path
  5. Amsterdam2239470117434549213151This 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
28th June 2005
Allocation block
72.96.0.0/11
Status
allocated
Origin validation
Valid

A ROA exists that authorises this origin AS to announce this prefix at this length.

ROAs covering this prefix

Route Origin Authorisations covering 72.96.0.0/11
ROA prefixAuthorised originMax length
72.96.0.0/11AS22394/11

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 72.96.0.0/11: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.72.96.0.0/11AS22394This prefix72.109.192.0/18AS616772.110.0.0/18AS616772.110.128.0/18AS616772.110.192.0/18AS616772.109.64.0/19AS6167+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. AS2239412th 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 72.96.0.0/11 in the calculator/11 reference

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