SUBNET.IM

2605:c0::/32

Rocket Connect LLCAS397019

At a glance

Subnets

4,294,967,296 × /64

/32 block

Visibility

100%

62 of 62 vantage points

RPKI

No ROA

Registry

ARINUS

Allocated 11th 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 2605:c0::/32, fanning out from AS397019 toward the vantage points that see it. Each path is written out in full beneath the graph.AS397019Rocket Connect LLCOriginAS22677Charter Communica…AS20115Charter Communica…AS6939Hurricane Electri…AS213151Christian ElsenAS51907Kanton ZugAS3356Lumen (Level 3)AS32590Valve CorporationAS132337Axclusive
  1. Amsterdam39701922677201156939213151This path
  2. London, UK3970192267720115693951907This path
  3. Sao Paulo3970192267720115335632590This path
  4. Singapore39701922677201156939132337This 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

100%

Seen by 62 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
ARIN — North America
Country
United States
Allocated
11th October 2018
Allocation block
2605:c0::/32
Status
allocated
Origin validation
No ROA

No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 2605:c0::/32: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.2605:c0::/32AS397019This prefix2605:c0::/34AS397019

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 2605:c0::/32
PrefixAddressesOriginVisibility
2605:c0::/341.1B × /64AS397019Rocket Connect LLC62/62

Sibling prefixes

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

History

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