subnet.im

45.158.197.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

76 of 76 vantage points

RPKI

Valid

Registry

RIPE NCCSC

Allocated 30th September 2019

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 45.158.197.0/24, fanning out from AS218261 toward the vantage points that see it. Each path is written out in full beneath the graph.AS218261Dimitriev Evgeny …OriginAS16276OVH SASAS8298IPng Networks GmbHAS8529Zain Omantel Inte…AS35280F5 Networks SARLAS3356Lumen (Level 3)AS23673Cogetel Online, C…AS8551Bezeq Internation…AS42013Together Communic…
  1. Amsterdam218261162768298This path
  2. London, UK218261162768529This path
  3. Sao Paulo2182611627635280This path
  4. Singapore21826116276335623673This path
  5. Oregon, US21826116276855142013This 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

100%

Seen by 76 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
Seychelles
Allocated
30th September 2019
Allocation block
45.158.196.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 45.158.197.0/24
ROA prefixAuthorised originMax length
45.158.197.0/24AS218261/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 45.158.197.0/24
PrefixAddressesOriginVisibility
45.158.196.0/24256AS207461HOSTING INDUSTRY LIMITED75/76

History

  1. AS2182615th November 2026 — present
  2. AS2163347th November 2026 — 7th November 2026
  3. AS21633429th October 2026 — 5th November 2026
  4. AS21633412th 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 45.158.197.0/24 in the calculator/24 reference

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