SUBNET.IM

2a01:71c1::/32

Grupo Loading Systems, S.L.AS198066

At a glance

Subnets

4,294,967,296 × /64

/32 block

Visibility

98%

61 of 62 vantage points

RPKI

No ROA

Registry

RIPE NCCES

Allocated 21st June 2012

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 2a01:71c1::/32, fanning out from AS198066 toward the vantage points that see it. Each path is written out in full beneath the graph.AS198066Grupo Loading Sys…OriginAS29119AIRE NETWORKS DEL…AS51907Kanton ZugAS132337AxclusiveAS34549meerfarbig GmbH &…AS213151Christian ElsenAS12956Telxius (Telefoni…AS32590Valve Corporation
  1. London, UK1980662911951907This path
  2. Singapore19806629119132337This path
  3. Amsterdam1980662911934549213151This path
  4. Sao Paulo198066291191295632590This 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
21st June 2012
Allocation block
2a01:71c0::/31
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 2a01:71c1::/32: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.2a01:71c1::/32AS198066This prefix2a01:71c1:47::/48AS50926

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

No less specific announcement covers this prefix.

More specific announcements

Announcements contained within 2a01:71c1::/32
PrefixAddressesOriginVisibility
2a01:71c1:47::/4865.5k × /64AS50926AXARNET COMUNICACIONES, S.L.59/62

Sibling prefixes

Prefixes of the same length sharing a parent block with 2a01:71c1::/32
PrefixAddressesOriginVisibility
2a01:71c0::/324.3B × /64AS198066Grupo Loading Systems, S.L.61/62

History

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