subnet.im

178.211.159.0/24

At a glance

Addresses

256

/24 block

Visibility

99%

81 of 82 vantage points

RPKI

Valid

Registry

RIPE NCCLT

Allocated 25th January 2022

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 178.211.159.0/24, fanning out from AS20724 toward the vantage points that see it. Each path is written out in full beneath the graph.AS20724GlobalTeleHost Co…OriginAS63023GTHostAS8298IPng Networks GmbHAS132337AxclusiveAS6939Hurricane Electri…AS20130Depaul UniversityAS174Cogent Communicat…AS1299Arelion (fka. Tel…AS35280F5 Networks SARLAS6453TATA Communicatio…AS35280F5 Networks SARL
  1. Amsterdam20724630238298This path
  2. Singapore2072463023132337This path
  3. Oregon, US2072463023693920130This path
  4. London, UK2072463023174129935280This path
  5. Sao Paulo2072463023174645335280This 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 81 of 82 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
Lithuania
Allocated
25th January 2022
Allocation block
178.211.159.0/24
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 178.211.159.0/24
ROA prefixAuthorised originMax length
178.211.159.0/24AS20724/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 178.211.159.0/24
PrefixAddressesOriginVisibility
178.211.158.0/24256AS210393EV Group GmbH82/82

History

  1. AS2072422nd September 2026 — present
  2. AS6445712th 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 178.211.159.0/24 in the calculator/24 reference

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