SUBNET.IM

2a11:ca00:101::/48

CATALUNYA TELECOM S.L.AS214954

At a glance

Subnets

65,536 × /64

/48 block

Visibility

98%

61 of 62 vantage points

RPKI

No ROA

Registry

RIPE NCCES

Allocated 22nd 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:ca00:101::/48, fanning out from AS214954 toward the vantage points that see it. Each path is written out in full beneath the graph.AS214954CATALUNYA TELECOM…OriginAS29119AIRE NETWORKS DEL…AS132337AxclusiveAS6939Hurricane Electri…AS213151Christian ElsenAS12956Telxius (Telefoni…AS32590Valve CorporationAS3356Lumen (Level 3)AS15576NTS workspace AGAS51907Kanton Zug
  1. Singapore21495429119132337This path
  2. Amsterdam214954291196939213151This path
  3. Sao Paulo214954291191295632590This path
  4. London, UK2149542911933561557651907This 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 61 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
Spain
Allocated
22nd July 2021
Allocation block
2a11:ca00::/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 2a11:ca00:101::/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.2a11:ca00::/29AS2149542a11:ca00:101::/…AS214954This prefix

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 2a11:ca00:101::/48
PrefixAddressesOriginVisibility
2a11:ca00::/2934.4B × /64AS214954CATALUNYA TELECOM S.L.61/62

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

No prefix of the same length in the same parent block is announced.

History

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