SUBNET.IM

2a0c:4f41:3000::/38

Wildanet LtdAS210258

At a glance

Subnets

67,108,864 × /64

/38 block

Visibility

61%

38 of 62 vantage points

RPKI

Valid

Registry

RIPE NCCGB

Allocated 10th April 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:4f41:3000::/38, fanning out from AS210258 toward the vantage points that see it. Each path is written out in full beneath the graph.AS210258Wildanet LtdOriginAS51907Kanton ZugAS132337AxclusiveAS34549meerfarbig GmbH &…AS213151Christian ElsenAS7195EdgeUnoAS32590Valve Corporation
  1. London, UK21025851907This path
  2. Singapore210258132337This path
  3. Amsterdam21025834549213151This path
  4. Sao Paulo210258719532590This 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

61%

Seen by 38 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
United Kingdom
Allocated
10th April 2018
Allocation block
2a0c:4f40::/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:4f41:3000::/38
ROA prefixAuthorised originMax length
2a0c:4f40::/29AS210258/38

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 2a0c:4f41:3000::/38: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.2a0c:4f40::/29AS2102582a0c:4f41:3000::…AS210258This prefix2a0c:4f41:3400::…AS210258

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 2a0c:4f41:3000::/38
PrefixAddressesOriginVisibility
2a0c:4f40::/2934.4B × /64AS210258Wildanet Ltd60/62

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 2a0c:4f41:3000::/38
PrefixAddressesOriginVisibility
2a0c:4f41:3400::/3867.1M × /64AS210258Wildanet Ltd38/62

History

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