SUBNET.IM

2a0f:1cc5:2640::/45

At a glance

Subnets

524,288 × /64

/45 block

Visibility

98%

61 of 62 vantage points

RPKI

Valid

Registry

RIPE NCCUS

Allocated 22nd October 2025

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:1cc5:2640::/45, fanning out from AS202335 toward the vantage points that see it. Each path is written out in full beneath the graph.AS202335Zhanrui TianOriginAS207529NYANLOLI LTDAS6939Hurricane Electri…AS213151Christian ElsenAS51907Kanton ZugAS132337AxclusiveAS44324MoeDove LLCAS216211CYBERVERSE LLCAS3356Lumen (Level 3)AS32590Valve Corporation
  1. Amsterdam2023352075296939213151This path
  2. London, UK202335207529693951907This path
  3. Singapore2023352075296939132337This path
  4. Sao Paulo20233544324216211335632590This 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

98%

Seen by 61 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
United States
Allocated
22nd October 2025
Allocation block
2a0f:1cc0::/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:1cc5:2640::/45
ROA prefixAuthorised originMax length
2a0f:1cc5:2600::/40AS202335/48
2a0f:1cc5:2600::/40AS40929/48
2a0f:1cc5:2600::/40AS44324/48
2a0f:1cc5:2600::/40AS53808/48

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 2a0f:1cc5:2640::/45: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.2a0f:1cc5:2640::…AS2023352a0f:1cc5:2640::…AS202335This prefix

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 2a0f:1cc5:2640::/45
PrefixAddressesOriginVisibility
2a0f:1cc5:2640::/424.2M × /64AS202335Zhanrui Tian61/62

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

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

History

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