SUBNET.IM

192.40.72.0/24

At a glance

Addresses

256

/24 block

Visibility

99%

79 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCFI

Allocated 24th November 1998

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 192.40.72.0/24, fanning out from AS5420 toward the vantage points that see it. Each path is written out in full beneath the graph.AS5420Kemira OyjOriginAS16086DNA OyjAS3356Lumen (Level 3)AS8529Zain Omantel Inte…AS266213PLANETCLICK TELEC…AS174Cogent Communicat…AS132337AxclusiveAS6939Hurricane Electri…AS20130Depaul UniversityAS34549meerfarbig GmbH &…AS213151Christian Elsen
  1. London, UK54201608633568529This path
  2. Sao Paulo5420160863356266213This path
  3. Singapore542016086174132337This path
  4. Oregon, US542016086693920130This path
  5. Amsterdam54201608617434549213151This 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 79 of 80 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
Finland
Allocated
24th November 1998
Allocation block
192.40.72.0/21
Status
assigned
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 192.40.72.0/24
ROA prefixAuthorised originMax length
192.40.72.0/24AS5420/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 192.40.72.0/24
PrefixAddressesOriginVisibility
192.40.73.0/24256AS5420Kemira Oyj79/80

History

  1. AS542012th August 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 192.40.72.0/24 in the calculator/24 reference

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