SUBNET.IM

2a0f:f4c1::/32

Digital Telecom IX LLCAS43380

At a glance

Subnets

4,294,967,296 × /64

/32 block

Visibility

100%

62 of 62 vantage points

RPKI

Valid

Registry

RIPE NCCUA

Allocated 17th December 2019

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:f4c1::/32, fanning out from AS43380 toward the vantage points that see it. Each path is written out in full beneath the graph.AS43380Digital Telecom I…OriginAS3326Datagroup PJSCAS213151Christian ElsenAS51907Kanton ZugAS132337AxclusiveAS7195EdgeUnoAS32590Valve Corporation
  1. Amsterdam433803326213151This path
  2. London, UK43380332651907This path
  3. Singapore433803326132337This path
  4. Sao Paulo433803326719532590This 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
RIPE NCC — Europe, Middle East, Central Asia
Country
Ukraine
Allocated
17th December 2019
Allocation block
2a0f:f4c0::/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:f4c1::/32
ROA prefixAuthorised originMax length
2a0f:f4c1::/32AS43380/64

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 2a0f:f4c1::/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.2a0f:f4c1::/32AS43380This prefix2a0f:f4c1:2::/48AS36040

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 2a0f:f4c1::/32
PrefixAddressesOriginVisibility
2a0f:f4c1:2::/4865.5k × /64AS36040Google (Global Cache)62/62

Sibling prefixes

Prefixes of the same length sharing a parent block with 2a0f:f4c1::/32
PrefixAddressesOriginVisibility
2a0f:f4c0::/324.3B × /64AS43380Digital Telecom IX LLC62/62

History

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