subnet.im

2c0f:1e40::/32

At a glance

Subnets

4,294,967,296 × /64

/32 block

Visibility

92%

57 of 62 vantage points

RPKI

Valid

Registry

AFRINICSD

Allocated 17th October 2023

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to London, UK.

OriginVantage point · London, UK
One AS path to 2c0f:1e40::/32 as seen from London, UK, read outward from the origin: AS329344 → AS174 → AS15576 → AS51907. Each hop is listed with its network name beneath the graph.AS329344Wave internetOriginAS174Cogent Communicat…AS15576NTS workspace AGAS51907Kanton Zug

Seen from London, UK

  1. Peer of AS329344seen on 430 paths from 136 vantage points
  2. Peer of AS174seen on 147,033 paths from 3 vantage points
  3. Peer of AS15576seen on 442,038 paths from 2 vantage points
  4. 4AS51907Kanton ZugCHVantage point

One path, hop by hop, from the origin outward to the vantage point that saw it. Counts beside each step are how often we see that pair adjacent anywhere in the table, not how often this path was used — BGP carries no traffic figures.

Every path we see

  1. Singapore329344174132337This path
  2. Amsterdam32934417434549213151This path
  3. London, UK3293441741557651907Shown above
  4. Sao Paulo3293441741295632590This 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

92%

Seen by 57 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
AFRINIC — Africa
Country
Sudan
Allocated
17th October 2023
Allocation block
2c0f:1e40::/32
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 2c0f:1e40::/32
ROA prefixAuthorised originMax length
2c0f:1e40::/32AS329344/48

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 2c0f:1e40::/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.2c0f:1e40::/32AS329344This prefix2c0f:1e40:1::/48AS329344

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 2c0f:1e40::/32
PrefixAddressesOriginVisibility
2c0f:1e40:1::/4865.5k × /64AS329344Wave internet 57/62

Sibling prefixes

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

History

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