subnet.im

2a11:1400:5042::/48

Juri UitAS219436

At a glance

Subnets

65,536 × /64

/48 block

Visibility

97%

60 of 62 vantage points

RPKI

No ROA

Registry

RIPE NCCNL

Allocated 8th July 2021

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: 4 observed paths to 2a11:1400:5042::/48, fanning out from AS219436 toward the vantage points that see it. Each path is written out in full beneath the graph.AS219436Juri UitOriginAS49581Ferdinand Zink tr…AS6939Hurricane Electri…AS32590Valve CorporationAS44592SkyLink Data Cent…AS132337AxclusiveAS6424EDGOO NETWORKSAS213151Christian ElsenAS51907Kanton Zug
  1. Sao Paulo21943649581693932590This path
  2. Singapore2194364958144592132337This path
  3. Amsterdam21943649581445926424213151This path
  4. London, UK2194364958144592642451907This 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

97%

Seen by 60 of 62 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
Netherlands
Allocated
8th July 2021
Allocation block
2a11:1400::/29
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 2a11:1400:5042::/48
PrefixAddressesOriginVisibility
2a11:1400:5043::/4865.5k × /64AS219436Juri Uit62/62

History

  1. AS21943612th 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.

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