subnet.im

62.169.153.0/24

At a glance

Addresses

256

/24 block

Visibility

99%

75 of 76 vantage points

RPKI

Valid

Registry

RIPE NCCDE

Allocated 1st August 2000

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 62.169.153.0/24 as seen from Amsterdam, read outward from the origin: AS218824 → AS207483 → AS60446 → AS208972 → AS6204 → AS8298. Each hop is listed with its network name beneath the graph.AS218824SOLTANTECH TEKNOL…OriginAS207483Netvia Bilisim Ya…AS60446Datema Bilisim Ti…AS208972GIBIRNet IletisimAS6204INTERKVM HOST SRLAS8298IPng Networks GmbH

Seen from Amsterdam

  1. Peer of AS218824seen on 151 paths from 76 vantage points
  2. Peer of AS207483seen on 1,024 paths from 139 vantage points
  3. Peer of AS60446seen on 6,177 paths from 116 vantage points
  4. Peer of AS208972seen on 40,034 paths from 134 vantage points
  5. Peer of AS6204seen on 1,499 paths from 2 vantage points
  6. 6AS8298IPng 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. Amsterdam2188242074836044620897262048298Shown above
  2. London, UK2188242074836044620897262048529This path
  3. Sao Paulo218824207483604462089726204291435280This path
  4. Singapore218824207483604462089726204291423673This path
  5. Oregon, US218824207483604462089726204174855142013This 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

99%

Seen by 75 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
Germany
Allocated
1st August 2000
Allocation block
62.169.152.0/23
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 62.169.153.0/24
ROA prefixAuthorised originMax length
62.169.153.0/24AS207483/24
62.169.153.0/24AS218824/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 62.169.153.0/24
PrefixAddressesOriginVisibility
62.169.152.0/24256AS51202NUXOA GmbH76/76

History

  1. AS2188244th October 2026 — present
  2. AS20748312th August 2026 — 6th 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 62.169.153.0/24 in the calculator/24 reference

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