SUBNET.IM

192.58.128.0/24

At a glance

Addresses

256

/24 block

Visibility

23%

18 of 80 vantage points

RPKI

Valid

Registry

ARINUS

Allocated 30th November 2000

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 192.58.128.0/24 as seen from Amsterdam, read outward from the origin: AS397197 → AS7342 → AS213151. Each hop is listed with its network name beneath the graph.AS397197Verisign Anycast …OriginAS7342VeriSign Infrastr…AS213151Christian Elsen

Seen from Amsterdam

  1. Peer of AS397197seen on 723 paths from 68 vantage points
  2. Peer of AS7342seen on 34 paths from 2 vantage points
  3. 3AS213151Christian ElsenDEVantage 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. Amsterdam3971977342213151Shown above
  2. Sao Paulo39665926415266213This path
  3. Singapore39672926415132337This path
  4. London, UK39668226415429618529This path
  5. Oregon, US39670226415693920130This 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

23%

Seen by 18 of 80 full-feed vantage points

Seen by few vantage points

Observed at 2 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
ARIN — North America
Country
United States
Allocated
30th November 2000
Allocation block
192.58.128.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 192.58.128.0/24
ROA prefixAuthorised originMax length
192.58.128.0/24AS10515/24
192.58.128.0/24AS19836/24
192.58.128.0/24AS20172/24
192.58.128.0/24AS20362/24
192.58.128.0/24AS20431/24
192.58.128.0/24AS211369/24
192.58.128.0/24AS21313/24
192.58.128.0/24AS22547/24
192.58.128.0/24AS25485/24
192.58.128.0/24AS26415/24
192.58.128.0/24AS27544/24
192.58.128.0/24AS32651/24
192.58.128.0/24AS36616/24
192.58.128.0/24AS36617/24
192.58.128.0/24AS36618/24
192.58.128.0/24AS36619/24
192.58.128.0/24AS36620/24
192.58.128.0/24AS36621/24
192.58.128.0/24AS36622/24
192.58.128.0/24AS36623/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.58.128.0/24
PrefixAddressesOriginVisibility
192.58.129.0/24256AS53902Fluxorus Networks80/80

History

  1. AS39654912th August 2026 present
  2. AS39657412th August 2026 present
  3. AS39672712th August 2026 present
  4. AS2254712th August 2026 present
  5. AS39658312th August 2026 present
  6. AS39670412th August 2026 present
  7. AS39673812th August 2026 present
  8. AS39665412th 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.58.128.0/24 in the calculator/24 reference

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