subnet.im

142.202.95.0/24

AS19969 is not currently observed originating this prefix. The origins we do see are listed above.

At a glance

Addresses

256

/24 block

Visibility

100%

81 of 81 vantage points

RPKI

Valid

Registry

ARINUS

Allocated 26th June 2024

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 142.202.95.0/24 as seen from Sao Paulo, read outward from the origin: AS25731 → AS19969 → AS174 → AS6453 → AS35280. Each hop is listed with its network name beneath the graph.AS25731Knox Box NetworksOriginAS19969CyberCloud Profes…AS174Cogent Communicat…AS6453TATA Communicatio…AS35280F5 Networks SARL

Seen from Sao Paulo

  1. Peer of AS25731seen on 386 paths from 143 vantage points
  2. Peer of AS19969seen on 1,295 paths from 104 vantage points
  3. Peer of AS174seen on 657,396 paths from 64 vantage points
  4. Peer of AS6453seen on 640,965 paths from 6 vantage points
  5. 5AS35280F5 Networks SARLFRVantage 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. Amsterdam257311996969398298This path
  2. London, UK2573119969646135280This path
  3. Singapore25731199696939132337This path
  4. Oregon, US2573119969693920130This path
  5. Sao Paulo2573119969174645335280Shown above

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 81 of 81 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
ARIN — North America
Country
United States
Allocated
26th June 2024
Allocation block
142.202.95.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 142.202.95.0/24
ROA prefixAuthorised originMax length
142.202.95.0/24AS25731/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 142.202.95.0/24
PrefixAddressesOriginVisibility
142.202.94.0/24256AS397585Tech and Networks Solutions, LLC81/81

History

  1. AS2573112th August 2026 — present
  2. AS1996925th September 2026 — 25th 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 142.202.95.0/24 in the calculator/24 reference

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