subnet.im

2a0f:b240:7300::/40

Mitja HerbajAS59449

At a glance

Subnets

16,777,216 × /64

/40 block

Visibility

97%

61 of 63 vantage points

RPKI

Valid

Registry

RIPE NCCCA

Allocated 31st January 2024

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 2a0f:b240:7300::/40, fanning out from AS59449 toward the vantage points that see it. Each path is written out in full beneath the graph.AS59449Mitja HerbajOriginAS214757Jakub KrsaAS8298IPng Networks GmbHAS212895Johannes ErnstAS5405Inter.link GmbHAS35280F5 Networks SARLAS215828Tizian Maxime Wei…AS6939Hurricane Electri…AS35280F5 Networks SARLAS132337Axclusive
  1. Amsterdam594492147578298This path
  2. London, UK59449212895540535280This path
  3. Sao Paulo59449215828693935280This path
  4. Singapore594492158286939132337This 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 61 of 63 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
Canada
Allocated
31st January 2024
Allocation block
2a0f:b240::/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 2a0f:b240:7300::/40
ROA prefixAuthorised originMax length
2a0f:b240:7300::/40AS59449/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 2a0f:b240:7300::/40
PrefixAddressesOriginVisibility
2a0f:b240:7200::/4016.8M × /64AS206042Suhail Haris63/63

History

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