SUBNET.IM

2a02:850:ffe6::/48

ipcom GmbHAS1921

At a glance

Subnets

65,536 × /64

/48 block

Visibility

97%

60 of 62 vantage points

RPKI

Valid

Registry

RIPE NCCAT

Allocated 7th January 2009

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 2a02:850:ffe6::/48 as seen from Sao Paulo, read outward from the origin: AS1921 → AS20473 → AS32590. Each hop is listed with its network name beneath the graph.AS1921ipcom GmbHOriginAS20473The Constant Comp…AS32590Valve Corporation

Seen from Sao Paulo

  1. 1AS1921ipcom GmbHATOrigin
    Peer of AS1921seen on 549 paths from 83 vantage points
  2. 2AS20473The Constant Company, LLCUS
    Peer of AS20473seen on 1,043 paths from 5 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. Amsterdam192144066213151This path
  2. London, UK19214406651907This path
  3. Sao Paulo19212047332590Shown above
  4. Singapore1921199524132337This 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
Austria
Allocated
7th January 2009
Allocation block
2a02:850::/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 2a02:850:ffe6::/48
ROA prefixAuthorised originMax length
2a02:850:ffe6::/48AS1921/48
2a02:850:ffe6::/48AS201612/48
2a02:850:ffe6::/48AS207021/48

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

Prefixes of the same length sharing a parent block with 2a02:850:ffe6::/48
PrefixAddressesOriginVisibility
2a02:850:ffe7::/4865.5k × /64AS1921ipcom GmbH11/62
2a02:850:ffe7::/4865.5k × /64AS207021ipcom GmbH50/62

History

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