SUBNET.IM

2a0c:b641:641::/48

At a glance

Subnets

65,536 × /64

/48 block

Visibility

82%

51 of 62 vantage points

RPKI

Valid

Registry

RIPE NCCBE

Allocated 15th May 2018

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 2a0c:b641:641::/48, fanning out from AS207306 toward the vantage points that see it. Each path is written out in full beneath the graph.AS207306Everia OyOriginAS208453Johan Karlsson (S…AS6939Hurricane Electri…AS213151Christian ElsenAS32590Valve CorporationAS3399Obenet ABAS132337AxclusiveAS174Cogent Communicat…AS3356Lumen (Level 3)AS9002RETN LimitedAS51907Kanton Zug
  1. Amsterdam2073062084536939213151This path
  2. Sao Paulo207306208453693932590This path
  3. Singapore2073062084533399132337This path
  4. London, UK20730620845333991743356900251907This 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

82%

Seen by 51 of 62 full-feed vantage points

Partially 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
Belgium
Allocated
15th May 2018
Allocation block
2a0c:b640::/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 2a0c:b641:641::/48
ROA prefixAuthorised originMax length
2a0c:b641:640::/44AS207306/128

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 2a0c:b641:641::/48
PrefixAddressesOriginVisibility
2a0c:b641:640::/4865.5k × /64AS207306Everia Oy61/62

History

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