subnet.im

166.1.232.0/24

DDOS PROTECTION LTDAS213840

FASTNET DATA INCAS8796

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

56%

43 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 Sao Paulo.

OriginVantage point · Sao Paulo
One AS path to 166.1.232.0/24 as seen from Sao Paulo, read outward from the origin: AS8796 → AS2914 → AS35280. Each hop is listed with its network name beneath the graph.AS8796FASTNET DATA INCOriginAS2914NTT America, Inc.AS35280F5 Networks SARL

Seen from Sao Paulo

  1. Peer of AS8796seen on 15,645 paths from 76 vantage points
  2. Peer of AS2914seen on 453,595 paths from 6 vantage points
  3. 3AS35280F5 Networks SARLFRVantage 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, UK879612998529This path
  2. Sao Paulo8796291435280Shown above
  3. Amsterdam21384010021374098298This path
  4. Singapore213840100213740923673This path
  5. Oregon, US2138401002137409693920130This 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

56%

Seen by 43 of 77 full-feed vantage points

Partially 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.232.0/24
ROA prefixAuthorised originMax length
166.1.232.0/24AS213840/24
166.1.232.0/24AS395886/24
166.1.232.0/24AS7488/24
166.1.232.0/24AS8796/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.232.0/24
PrefixAddressesOriginVisibility
166.1.233.0/24256AS3257GTT Communications Inc.77/77

History

  1. AS879620th October 2026 — present
  2. AS21384023rd September 2026 — present
  3. AS879625th September 2026 — 6th October 2026
  4. AS879612th August 2026 — 25th September 2026
  5. AS21384022nd September 2026 — 22nd September 2026
  6. AS748812th August 2026 — 21st September 2026
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.232.0/24 in the calculator/24 reference

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