subnet.im

2a09:3f00:5f10::/44

Ben KlinkeAS198590

At a glance

Subnets

1,048,576 × /64

/44 block

Visibility

98%

63 of 64 vantage points

RPKI

Valid

Registry

RIPE NCCDE

Allocated 4th June 2026

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 2a09:3f00:5f10::/44 as seen from Amsterdam, read outward from the origin: AS198590 → AS207252 → AS50629 → AS32590. Each hop is listed with its network name beneath the graph.AS198590Ben KlinkeOriginAS207252Felix GassanAS50629LWLcom GmbHAS32590Valve Corporation

Seen from Amsterdam

  1. 1AS198590Ben KlinkeDEOrigin
    Peer of AS198590seen on 648 paths from 144 vantage points
  2. 2AS207252Felix GassanDE
    Peer of AS207252seen on 3,252 paths from 143 vantage points
  3. 3AS50629LWLcom GmbHDE
    Peer of AS50629seen on 428 paths from 2 vantage points
  4. 4AS32590Valve CorporationUSVantage 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. Amsterdam1985902072525062932590Shown above
  2. London, UK1985902072525062935280This path
  3. Singapore19859020725250629132337This path
  4. Sao Paulo19859020725250629174645335280This 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

98%

Seen by 63 of 64 full-feed vantage points

Globally propagated

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
RIPE NCC — Europe, Middle East, Central Asia
Country
Germany
Allocated
4th June 2026
Allocation block
2a09:3f00::/29
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 2a09:3f00:5f10::/44
ROA prefixAuthorised originMax length
2a09:3f00:5f10::/44AS198590/44

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 2a09:3f00:5f10::/44
PrefixAddressesOriginVisibility
2a09:3f00:5f00::/441M × /64AS198590Ben Klinke63/64

History

  1. AS19859022nd September 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.

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