subnet.im

2a12:de40::/32

Ferdinand Zink trading as Tube-HostingAS49581

At a glance

Subnets

4,294,967,296 × /64

/32 block

Visibility

97%

60 of 62 vantage points

RPKI

No ROA

Registry

RIPE NCCDE

Allocated 29th April 2022

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 2a12:de40::/32 as seen from Sao Paulo, read outward from the origin: AS49581 → AS6939 → AS32590. Each hop is listed with its network name beneath the graph.AS49581Ferdinand Zink tr…OriginAS6939Hurricane Electri…AS32590Valve Corporation

Seen from Sao Paulo

  1. 1AS49581Ferdinand Zink trading as Tube-HostingDEOrigin
    Peer of AS49581seen on 5,865 paths from 55 vantage points
  2. 2AS6939Hurricane Electric LLCUS
    Peer of AS6939seen on 335,352 paths from 8 vantage points
  3. 3AS32590Valve 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. Amsterdam495816939213151This path
  2. London, UK49581693951907This path
  3. Sao Paulo49581693932590Shown above
  4. Singapore495816939132337This 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
Germany
Allocated
29th April 2022
Allocation block
2a12:de40::/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 2a12:de40::/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.2a12:de40::/32AS49581This prefix2a12:de40:200::/…AS2160632a12:de40:300::/…AS2149282a12:de40:9::/48AS2076952a12:de40:20::/48AS2160632a12:de40:21::/48AS216063+5 more

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.

Sibling prefixes

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

History

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