SUBNET.IM

2a07:aa00:a::/48

Lumen (Level 3)AS3356

At a glance

Subnets

65,536 × /64

/48 block

Visibility

100%

62 of 62 vantage points

RPKI

No ROA

Registry

RIPE NCCGB

Allocated 1st July 2016

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 2a07:aa00:a::/48, fanning out from AS3356 toward the vantage points that see it. Each path is written out in full beneath the graph.AS3356Lumen (Level 3)OriginAS32590Valve CorporationAS6939Hurricane Electri…AS213151Christian ElsenAS15576NTS workspace AGAS51907Kanton ZugAS132337Axclusive
  1. Sao Paulo335632590This path
  2. Amsterdam33566939213151This path
  3. London, UK33561557651907This path
  4. Singapore33566939132337This 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 62 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
United Kingdom
Allocated
1st July 2016
Allocation block
2a07:aa00::/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.

CoveringMore specific
Prefix hierarchy for 2a07:aa00:a::/48: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.2a07:aa00::/29AS35492a07:aa00:a::/48AS3356This prefix2a07:aa00:b::/48AS3356

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 2a07:aa00:a::/48
PrefixAddressesOriginVisibility
2a07:aa00::/2934.4B × /64AS3549Lumen (fka. Global Crossing)61/62

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 2a07:aa00:a::/48
PrefixAddressesOriginVisibility
2a07:aa00:b::/4865.5k × /64AS3356Lumen (Level 3)62/62

History

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