subnet.im

5.175.132.0/24

At a glance

Addresses

256

/24 block

Visibility

99%

80 of 81 vantage points

RPKI

Valid

Registry

RIPE NCCDE

Allocated 2nd August 2012

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 5.175.132.0/24 as seen from Amsterdam, read outward from the origin: AS211066 → AS207252 → AS50629 → AS8298. Each hop is listed with its network name beneath the graph.AS211066Simon MariacherOriginAS207252Felix GassanAS50629LWLcom GmbHAS8298IPng Networks GmbH

Seen from Amsterdam

  1. Peer of AS211066seen on 609 paths from 144 vantage points
  2. Peer of AS207252seen on 3,252 paths from 143 vantage points
  3. Peer of AS50629seen on 231 paths from 2 vantage points
  4. 4AS8298IPng 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. Amsterdam211066207252506298298Shown above
  2. London, UK2110662072525062935280This path
  3. Sao Paulo21106620725250629335635280This path
  4. Singapore2110662072525062950263132337This path
  5. Oregon, US21106620725250629693920130This 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 80 of 81 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
2nd August 2012
Allocation block
5.175.128.0/17
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 5.175.132.0/24
ROA prefixAuthorised originMax length
5.175.132.0/24AS211066/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 5.175.132.0/24
PrefixAddressesOriginVisibility
5.175.133.0/24256AS12586GHOSTnet GmbH80/81

History

  1. AS21106622nd September 2026 — present
  2. AS1258612th 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 5.175.132.0/24 in the calculator/24 reference

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