SUBNET.IM

2a06:a001:a010::/44

ColocaTel Inc.AS213438

At a glance

Subnets

1,048,576 × /64

/44 block

Visibility

98%

61 of 62 vantage points

RPKI

No ROA

Registry

RIPE NCCUS

Allocated 15th October 2015

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 2a06:a001:a010::/44, fanning out from AS213438 toward the vantage points that see it. Each path is written out in full beneath the graph.AS213438ColocaTel Inc.OriginAS44592SkyLink Data Cent…AS132337AxclusiveAS6453TATA Communicatio…AS6939Hurricane Electri…AS213151Christian ElsenAS3257GTT Communication…AS9002RETN LimitedAS51907Kanton ZugAS3356Lumen (Level 3)AS32590Valve Corporation
  1. Singapore21343844592132337This path
  2. Amsterdam21343864536939213151This path
  3. London, UK2134383257900251907This path
  4. Sao Paulo2134386453335632590This 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
15th October 2015
Allocation block
2a06:a000::/29
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.

Covering announcements

No less specific announcement covers this prefix.

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. AS21343812th 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.