subnet.im

5.175.167.0/24

Tier 4 Cloud ServicesAS146943

209, Laxmi PlazaAS132005

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

96%

78 of 81 vantage points

RPKI

Valid

Registry

RIPE NCCDE

Allocated 2nd August 2012

AS paths to this prefix

One real path per vantage point, fanning out from the origin. Where two reach the prefix the same way, those hops are drawn once. Open a path to follow it hop by hop.

OriginVantage points
AS path graph: 5 observed paths to 5.175.167.0/24, fanning out from AS132005, AS146943 toward the vantage points that see it. Each path is written out in full beneath the graph.AS146943Tier 4 Cloud Serv…OriginAS13335Cloudflare, Inc.AS8298IPng Networks GmbHAS35280F5 Networks SARLAS132337AxclusiveAS132005209, Laxmi PlazaOriginAS146943Tier 4 Cloud Serv…AS8966Etisalat (E&)AS35280F5 Networks SARLAS23352DEFT.COMAS20130Depaul University
  1. Amsterdam146943133358298This path
  2. Sao Paulo1469431333535280This path
  3. Singapore14694313335132337This path
  4. London, UK132005146943896635280This path
  5. Oregon, US146943133352335220130This 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

96%

Seen by 78 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.167.0/24
ROA prefixAuthorised originMax length
5.175.167.0/24AS132005/24
5.175.167.0/24AS146943/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.167.0/24
PrefixAddressesOriginVisibility
5.175.166.0/24256AS213250Dominic Scholz trading as ITP-Solutions GmbH & Co. KG81/81

History

  1. AS13200512th August 2026 — present
  2. AS14694322nd September 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 5.175.167.0/24 in the calculator/24 reference

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