subnet.im

2a12:be40::/48

sector7 GmbHAS208545

At a glance

Subnets

65,536 × /64

/48 block

Visibility

98%

61 of 62 vantage points

RPKI

Valid

Registry

RIPE NCCDE

Allocated 1st April 2022

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to London, UK.

OriginVantage point · London, UK
One AS path to 2a12:be40::/48 as seen from London, UK, read outward from the origin: AS208545 → AS8881 → AS51907. Each hop is listed with its network name beneath the graph.AS208545sector7 GmbHOriginAS88811&1 Versatel GmbHAS51907Kanton Zug

Seen from London, UK

  1. 1AS208545sector7 GmbHDEOrigin
    Peer of AS208545seen on 560 paths from 140 vantage points
  2. 2AS88811&1 Versatel GmbHDE
    Peer of AS8881seen on 995 paths from 2 vantage points
  3. 3AS51907Kanton ZugCHVantage 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. Amsterdam2085458881213151This path
  2. London, UK208545888151907Shown above
  3. Singapore2085458881132337This path
  4. Sao Paulo2085458881719532590This 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
Germany
Allocated
1st April 2022
Allocation block
2a12:be40::/29
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 2a12:be40::/48
ROA prefixAuthorised originMax length
2a12:be40::/48AS208545/48
2a12:be40::/29AS208545/29

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

CoveringMore specific
Prefix hierarchy for 2a12:be40::/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.2a12:be40::/29AS2085452a12:be40::/48AS208545This prefix2a12:be40:1::/48AS208545

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 2a12:be40::/48
PrefixAddressesOriginVisibility
2a12:be40::/2934.4B × /64AS208545sector7 GmbH61/62

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 2a12:be40::/48
PrefixAddressesOriginVisibility
2a12:be40:1::/4865.5k × /64AS208545sector7 GmbH61/62

History

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