subnet.im

109.65.172.0/22

At a glance

Addresses

1,024

/22 block

Visibility

100%

76 of 76 vantage points

RPKI

Valid

Registry

RIPE NCCIL

Allocated 10th August 2009

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 109.65.172.0/22 as seen from Amsterdam, read outward from the origin: AS12083 → AS6939 → AS8298. Each hop is listed with its network name beneath the graph.AS12083WideOpenWest Fina…OriginAS6939Hurricane Electri…AS8298IPng Networks GmbH

Seen from Amsterdam

  1. Peer of AS12083seen on 23,625 paths from 99 vantage points
  2. Peer of AS6939seen on 131,297 paths from 2 vantage points
  3. 3AS8298IPng 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. Amsterdam1208369398298Shown above
  2. London, UK1208312998529This path
  3. Sao Paulo12083693935280This path
  4. Singapore12083693923673This path
  5. Oregon, US120831299855142013This 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 76 of 76 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
Israel
Allocated
10th August 2009
Allocation block
109.64.0.0/14
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 109.65.172.0/22
ROA prefixAuthorised originMax length
109.65.172.0/22AS12083/24
109.65.172.0/22AS7029/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 109.65.172.0/22
PrefixAddressesOriginVisibility
109.65.168.0/221kAS12083WideOpenWest Finance LLC76/76

History

  1. AS1208316th October 2026 — present
  2. AS70295th October 2026 — 16th October 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 109.65.172.0/22 in the calculator/22 reference

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