subnet.im

166.1.246.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

77 of 77 vantage points

RPKI

Valid

Registry

ARINUS

Allocated 10th July 2012

AS paths to this prefix

All paths

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

OriginVantage point · Amsterdam
One AS path to 166.1.246.0/24 as seen from Amsterdam, read outward from the origin: AS7488 → AS3257 → AS25091 → AS8298. Each hop is listed with its network name beneath the graph.AS7488CNServer LLCOriginAS3257GTT Communication…AS25091IP-Max SAAS8298IPng Networks GmbH

Seen from Amsterdam

  1. Peer of AS7488seen on 1,685 paths from 53 vantage points
  2. Peer of AS3257seen on 43,545 paths from 5 vantage points
  3. Peer of AS25091seen on 663,872 paths from 2 vantage points
  4. 4AS8298IPng Networks GmbHCHVantage 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, UK748869398529This path
  2. Sao Paulo7488291435280This path
  3. Singapore7488291423673This path
  4. Oregon, US7488693920130This path
  5. Amsterdam74883257250918298Shown 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

100%

Seen by 77 of 77 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 July 2012
Allocation block
166.0.0.0/15
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 166.1.246.0/24
ROA prefixAuthorised originMax length
166.1.246.0/24AS7488/24

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

Prefixes of the same length sharing a parent block with 166.1.246.0/24
PrefixAddressesOriginVisibility
166.1.247.0/24256AS7488CNServer LLC77/77

History

  1. AS748822nd September 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 166.1.246.0/24 in the calculator/24 reference

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