subnet.im

162.141.13.0/24

At a glance

Addresses

256

/24 block

Visibility

93%

71 of 76 vantage points

RPKI

Valid

Registry

RIPE NCCUS

Allocated 8th December 1992

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 162.141.13.0/24 as seen from Amsterdam, read outward from the origin: AS137410 → AS63199 → AS3257 → AS25091 → AS8298. Each hop is listed with its network name beneath the graph.AS137410MiM Digital Marke…OriginAS63199CDS Global Cloud …AS3257GTT Communication…AS25091IP-Max SAAS8298IPng Networks GmbH

Seen from Amsterdam

  1. Peer of AS137410seen on 482 paths from 76 vantage points
  2. Peer of AS63199seen on 6,258 paths from 118 vantage points
  3. Peer of AS3257seen on 39,215 paths from 5 vantage points
  4. Peer of AS25091seen on 664,395 paths from 2 vantage points
  5. 5AS8298IPng 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. Singapore93043862323673This path
  2. Amsterdam137410631993257250918298Shown above
  3. London, UK13741063199325764538529This path
  4. Sao Paulo137410631993257645335280This path
  5. Oregon, US13741063199174855142013This 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

93%

Seen by 71 of 76 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
RIPE NCC — Europe, Middle East, Central Asia
Country
United States
Allocated
8th December 1992
Allocation block
162.141.0.0/16
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 162.141.13.0/24
ROA prefixAuthorised originMax length
162.141.13.0/24AS137410/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 162.141.13.0/24
PrefixAddressesOriginVisibility
162.141.12.0/24256AS20473The Constant Company, LLC76/76

History

  1. AS1374102nd November 2026 — present
  2. AS930412th August 2026 — present
  3. AS2519830th September 2026 — 30th October 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 162.141.13.0/24 in the calculator/24 reference

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