subnet.im

166.1.144.0/24

AntiDDoS Networks LTDAS218239

EdgeSec Technologies LimitedAS216039

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

72%

55 of 76 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 London, UK.

OriginVantage point · London, UK
One AS path to 166.1.144.0/24 as seen from London, UK, read outward from the origin: AS218239 → AS199522 → AS137409 → AS8529. Each hop is listed with its network name beneath the graph.AS218239AntiDDoS Networks…OriginAS199522LA FATTORIA DEL M…AS137409GSL Networks Pty …AS8529Zain Omantel Inte…

Seen from London, UK

  1. 1AS218239AntiDDoS Networks LTDGBOrigin
    Peer of AS218239seen on 221 paths from 75 vantage points
  2. 2AS199522LA FATTORIA DEL MOLISE DI SARPI FILIPPO S.A.SIT
    Peer of AS199522seen on 221 paths from 75 vantage points
  3. 3AS137409GSL Networks Pty LTDAU
    Peer of AS137409seen on 36,550 paths from 6 vantage points
  4. 4AS8529Zain Omantel International FZ-LLCAEVantage 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. Amsterdam2182391995221374098298This path
  2. London, UK2182391995221374098529Shown above
  3. Sao Paulo21823919952213740935280This path
  4. Singapore21603921923613740923673This path
  5. Oregon, US218239199522137409855142013This 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

72%

Seen by 55 of 76 full-feed vantage points

Partially propagated

Observed at 4 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.144.0/24
ROA prefixAuthorised originMax length
166.1.144.0/24AS216039/24
166.1.144.0/24AS218239/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.144.0/24
PrefixAddressesOriginVisibility
166.1.145.0/24256AS6079Astound (fka. RCN)76/76

History

  1. AS21603912th August 2026 — present
  2. AS21823910th November 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.144.0/24 in the calculator/24 reference

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