SUBNET.IM

72.192.0.0/11

Cox Communications Inc.AS22773

At a glance

Addresses

2,097,152

/11 block

Visibility

99%

79 of 80 vantage points

RPKI

Valid

Registry

ARINUS

Allocated 3rd August 2005

AS paths to this prefix

All paths

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

OriginVantage point · Singapore
One AS path to 72.192.0.0/11 as seen from Singapore, read outward from the origin: AS22773 → AS1299 → AS132337. Each hop is listed with its network name beneath the graph.AS22773Cox Communication…OriginAS1299Arelion (fka. Tel…AS132337Axclusive

Seen from Singapore

  1. 1AS22773Cox Communications Inc.USOrigin
    Peer of AS22773seen on 313,275 paths from 142 vantage points
  2. 2AS1299Arelion (fka. Telia Carrier)SE
    Peer of AS1299seen on 165,750 paths from 2 vantage points
  3. 3AS132337AxclusiveSGVantage 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. London, UK2277312998529This path
  2. Singapore227731299132337Shown above
  3. Oregon, US22773693920130This path
  4. Amsterdam22773325734549213151This path
  5. Sao Paulo2277312993356266213This 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

99%

Seen by 79 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
3rd August 2005
Allocation block
72.192.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.192.0.0/11
ROA prefixAuthorised originMax length
72.192.0.0/11AS22773/11

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 72.192.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.192.0.0/11AS22773This prefix72.193.0.0/16AS2277372.197.0.0/16AS2277372.199.0.0/16AS2277372.201.0.0/16AS2277372.208.0.0/16AS22773+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. AS2277312th 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.192.0.0/11 in the calculator/11 reference

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