SUBNET.IM

192.42.177.0/24

At a glance

Addresses

256

/24 block

Visibility

31%

25 of 80 vantage points

RPKI

Valid

Registry

ARINUS

Allocated 17th September 2013

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Sao Paulo.

OriginVantage point · Sao Paulo
One AS path to 192.42.177.0/24 as seen from Sao Paulo, read outward from the origin: AS396555 → AS7342 → AS3356 → AS266213. Each hop is listed with its network name beneath the graph.AS396555Verisign Anycast …OriginAS7342VeriSign Infrastr…AS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…

Seen from Sao Paulo

  1. Peer of AS396555seen on 87 paths from 8 vantage points
  2. Peer of AS7342seen on 4,611 paths from 142 vantage points
  3. Peer of AS3356seen on 997,311 paths from 2 vantage points

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. Amsterdam3971977342213151This path
  2. London, UK39719773428529This path
  3. Singapore3965497342132337This path
  4. Sao Paulo39655573423356266213Shown above
  5. Oregon, US3965557342693920130This 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

31%

Seen by 25 of 80 full-feed vantage points

Seen by few vantage points

Observed at 4 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
17th September 2013
Allocation block
192.42.176.0/23
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.42.177.0/24
ROA prefixAuthorised originMax length
192.42.177.0/24AS10515/24
192.42.177.0/24AS19836/24
192.42.177.0/24AS20172/24
192.42.177.0/24AS20362/24
192.42.177.0/24AS20431/24
192.42.177.0/24AS211369/24
192.42.177.0/24AS21313/24
192.42.177.0/24AS22547/24
192.42.177.0/24AS25485/24
192.42.177.0/24AS27544/24
192.42.177.0/24AS32651/24
192.42.177.0/24AS36616/24
192.42.177.0/24AS36617/24
192.42.177.0/24AS36618/24
192.42.177.0/24AS36619/24
192.42.177.0/24AS36620/24
192.42.177.0/24AS36621/24
192.42.177.0/24AS36622/24
192.42.177.0/24AS36623/24
192.42.177.0/24AS36624/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.

History

  1. AS39654612th August 2026 present
  2. AS1051512th August 2026 present
  3. AS39654912th August 2026 present
  4. AS39656312th August 2026 present
  5. AS39654412th August 2026 present
  6. AS39655512th August 2026 present
  7. AS39659912th August 2026 present
  8. AS39719712th 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.42.177.0/24 in the calculator/24 reference

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