SUBNET.IM

68.32.0.0/11

At a glance

Addresses

2,097,152

/11 block

Visibility

98%

78 of 80 vantage points

RPKI

Valid

Registry

ARINUS

Allocated 29th November 2001

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 68.32.0.0/11 as seen from Singapore, read outward from the origin: AS7922 → AS2914 → AS8966 → AS132337. Each hop is listed with its network name beneath the graph.AS7922Comcast Cable Com…OriginAS2914NTT America, Inc.AS8966Etisalat (E&)AS132337Axclusive

Seen from Singapore

  1. Peer of AS7922seen on 59,064 paths from 45 vantage points
  2. Peer of AS2914seen on 60,369 paths from 3 vantage points
  3. Peer of AS8966seen on 133,632 paths from 2 vantage points
  4. 4AS132337AxclusiveSGVantage 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, UK792212998529This path
  2. Sao Paulo79223356266213This path
  3. Oregon, US7922693920130This path
  4. Amsterdam792217434549213151This path
  5. Singapore792229148966132337Shown above

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
29th November 2001
Allocation block
68.32.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 68.32.0.0/11
ROA prefixAuthorised originMax length
68.32.0.0/11AS7922/11

Prefix hierarchy

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

Covering announcements

No less specific announcement covers this prefix.

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

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

History

  1. AS792212th 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 68.32.0.0/11 in the calculator/11 reference

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