subnet.im

217.64.32.0/20

Mediam Group OyAS39324

At a glance

Addresses

4,096

/20 block

Visibility

99%

79 of 80 vantage points

RPKI

No ROA

Registry

RIPE NCCFI

Allocated 12th May 2010

AS paths to this prefix

One real path per vantage point, fanning out from the origin. Where two reach the prefix the same way, those hops are drawn once. Open a path to follow it hop by hop.

OriginVantage points
AS path graph: 5 observed paths to 217.64.32.0/20, fanning out from AS39324 toward the vantage points that see it. Each path is written out in full beneath the graph.AS39324Mediam Group OyOriginAS47605FNE-Finland OyAS213151Christian ElsenAS8529Zain Omantel Inte…AS132337AxclusiveAS16086DNA OyjAS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…AS6939Hurricane Electri…AS20130Depaul University
  1. Amsterdam3932447605213151This path
  2. London, UK39324476058529This path
  3. Singapore3932447605132337This path
  4. Sao Paulo39324160863356266213This path
  5. Oregon, US3932447605693920130This 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

99%

Seen by 79 of 80 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
Finland
Allocated
12th May 2010
Allocation block
217.64.32.0/20
Status
allocated
Origin validation
No ROA

No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.

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 217.64.32.0/20
PrefixAddressesOriginVisibility
217.64.48.0/204.1kAS29513Foliateam Operateur SAS80/80

History

  1. AS3932412th 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 217.64.32.0/20 in the calculator/20 reference

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