SUBNET.IM

2a01:7680::/32

Valor Information Technologies, S.L.AS39639

At a glance

Subnets

4,294,967,296 × /64

/32 block

Visibility

98%

61 of 62 vantage points

RPKI

Valid

Registry

RIPE NCCES

Allocated 20th June 2011

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Sao Paulo.

OriginVantage point · Sao Paulo
One AS path to 2a01:7680::/32 as seen from Sao Paulo, read outward from the origin: AS39639 → AS39640 → AS15954 → AS6939 → AS32590. Each hop is listed with its network name beneath the graph.AS39639Valor Information…OriginAS39640Valor Information…AS15954Tecnocratica Cent…AS6939Hurricane Electri…AS32590Valve Corporation

Seen from Sao Paulo

  1. 1AS39639Valor Information Technologies, S.L.ESOrigin
    Peer of AS39639seen on 61 paths from 61 vantage points
  2. 2AS39640Valor Information Technologies, S.L.ES
    Peer of AS39640seen on 1,222 paths from 140 vantage points
  3. 3AS15954Tecnocratica Centro de Datos, S.L.ES
    Peer of AS15954seen on 142 paths from 14 vantage points
  4. 4AS6939Hurricane Electric LLCUS
    Peer of AS6939seen on 335,352 paths from 8 vantage points
  5. 5AS32590Valve 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. Amsterdam39639396401595434549213151This path
  2. London, UK3963939640159542911951907This path
  3. Sao Paulo396393964015954693932590Shown above
  4. Singapore39639396401595429119132337This 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
20th June 2011
Allocation block
2a01:7680::/32
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 2a01:7680::/32
ROA prefixAuthorised originMax length
2a01:7680::/32AS39639/32

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

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

History

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