subnet.im

104.234.95.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

81 of 81 vantage points

RPKI

Valid

Registry

ARINCA

Allocated 27th October 2014

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 104.234.95.0/24 as seen from Amsterdam, read outward from the origin: AS16276 → AS8298. Each hop is listed with its network name beneath the graph.AS16276OVH SASOriginAS8298IPng Networks GmbH

Seen from Amsterdam

  1. Peer of AS16276seen on 1,105 paths from 2 vantage points
  2. 2AS8298IPng Networks GmbHCHVantage 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. Amsterdam162768298Shown above
  2. London, UK1627635280This path
  3. Sao Paulo1627635280This path
  4. Singapore16276132337This path
  5. Oregon, US16276693920130This 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

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
Canada
Allocated
27th October 2014
Allocation block
104.234.0.0/16
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 104.234.95.0/24
ROA prefixAuthorised originMax length
104.234.95.0/24AS16276/24

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

CoveringMore specific
Prefix hierarchy for 104.234.95.0/24: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.104.234.92.0/22AS22773104.234.95.0/24AS16276This prefix104.234.94.0/24AS16276

Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.

Covering announcements

Announcements that contain 104.234.95.0/24
PrefixAddressesOriginVisibility
104.234.92.0/221kAS22773Cox Communications Inc.81/81

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 104.234.95.0/24
PrefixAddressesOriginVisibility
104.234.94.0/24256AS16276OVH SAS81/81

History

  1. AS1627622nd September 2026 — present
  2. AS4067612th 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 104.234.95.0/24 in the calculator/24 reference

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