subnet.im

161.0.67.0/24

At a glance

Addresses

256

/24 block

Visibility

99%

79 of 80 vantage points

RPKI

Valid

Registry

LACNICAR

Allocated 31st March 2014

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 161.0.67.0/24 as seen from London, UK, read outward from the origin: AS273947 → AS263774 → AS7303 → AS22927 → AS12956 → AS1299 → AS8529. Each hop is listed with its network name beneath the graph.AS273947CABLE VISION PUER…OriginAS263774MARANDU COMUNICAC…AS7303Telecom Argentina…AS22927Telefonica de Arg…AS12956Telxius (Telefoni…AS1299Arelion (fka. Tel…AS8529Zain Omantel Inte…

Seen from London, UK

  1. Peer of AS273947seen on 141 paths from 141 vantage points
  2. Peer of AS263774seen on 541 paths from 72 vantage points
  3. Peer of AS7303seen on 109,443 paths from 142 vantage points
  4. Peer of AS22927seen on 280,450 paths from 142 vantage points
  5. Peer of AS12956seen on 305,731 paths from 67 vantage points
  6. Peer of AS1299seen on 403,291 paths from 2 vantage points

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. Amsterdam2739472637742814561599213151This path
  2. Singapore2739472637742814561599132337This path
  3. Oregon, US27394726377452404693920130This path
  4. Sao Paulo273947263774281456159916735266213This path
  5. London, UK2739472637747303229271295612998529Shown 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

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
LACNIC — Latin America and the Caribbean
Country
Argentina
Allocated
31st March 2014
Allocation block
161.0.64.0/22
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 161.0.67.0/24
ROA prefixAuthorised originMax length
161.0.67.0/24AS273947/24
161.0.64.0/22AS262935/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 161.0.67.0/24
PrefixAddressesOriginVisibility
161.0.66.0/24256AS273969COOPERATIVA DE ELECTRICIDAD DE MONTECARLO LIMITADA79/80

History

  1. AS27394712th 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 161.0.67.0/24 in the calculator/24 reference

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