subnet.im

2a0d:c7c7:400::/38

Huanjie ZhuAS205610

At a glance

Subnets

67,108,864 × /64

/38 block

Visibility

37%

23 of 62 vantage points

RPKI

Valid

Registry

RIPE NCCDE

Allocated 15th October 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 2a0d:c7c7:400::/38, fanning out from AS205610 toward the vantage points that see it. Each path is written out in full beneath the graph.AS205610Huanjie ZhuOriginAS10111Zeofast NetworkAS6939Hurricane Electri…AS213151Christian ElsenAS32590Valve CorporationAS132337AxclusiveAS41913Computerline GmbHAS34288Kantonsschule ZugAS51907Kanton Zug
  1. Amsterdam205610101116939213151This path
  2. Sao Paulo20561010111693932590This path
  3. Singapore205610101116939132337This path
  4. London, UK205610101116939419133428851907This 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

37%

Seen by 23 of 62 full-feed vantage points

Seen by few vantage points

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
15th October 2018
Allocation block
2a0d:c7c0::/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 2a0d:c7c7:400::/38
ROA prefixAuthorised originMax length
2a0d:c7c7::/32AS205610/48
2a0d:c7c0::/29AS3204/48
2a0d:c7c0::/29AS3214/48
2a0d:c7c0::/29AS3258/48
2a0d:c7c0::/29AS4785/48
2a0d:c7c0::/29AS6233/48
2a0d:c7c0::/29AS8888/48
2a0d:c7c0::/29AS9312/48
2a0d:c7c0::/29AS949/48

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 2a0d:c7c7:400::/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.2a0d:c7c7:400::/…AS205610This prefix2a0d:c7c7:600::/…AS205610

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

No less specific announcement covers this prefix.

More specific announcements

Announcements contained within 2a0d:c7c7:400::/38
PrefixAddressesOriginVisibility
2a0d:c7c7:600::/3933.6M × /64AS205610Huanjie Zhu23/62

Sibling prefixes

No prefix of the same length in the same parent block is announced.

History

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