subnet.im

2a13:a5c3:3200::/40

Not announced at this prefix length

We do not see 2a13:a5c3:3200::/40 announced as its own route. The most specific announcement covering it is 2a13:a5c3:3000::/36, originated by AS44324 (MoeDove LLC). Traffic to addresses in this block follows that route.

At a glance

Subnets

16,777,216 × /64

/40 block

Visibility

Unknown

RPKI

Unknown

Registry

RIPE NCCGB

Allocated 8th August 2023

AS paths to this prefix

No AS paths are stored for this prefix. We keep the full path from one reference peer per collector rather than from every peer, so a prefix only has paths here once it has been seen by one of those peers.

Registry and RPKI

RIR
RIPE NCC — Europe, Middle East, Central Asia
Country
United Kingdom
Allocated
8th August 2023
Allocation block
2a13:a5c0::/29
Status
allocated
Origin validation
Unknown

ROAs covering this prefix

Route Origin Authorisations covering 2a13:a5c3:3200::/40
ROA prefixAuthorised originMax length
2a13:a5c3::/32AS44324/48

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 2a13:a5c3:3200::/40: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.2a13:a5c3:3000::…AS443242a13:a5c3:3200::…This prefix2a13:a5c3:3300::…AS443242a13:a5c3:32e0::…AS44324

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 2a13:a5c3:3200::/40
PrefixAddressesOriginVisibility
2a13:a5c3:3000::/36268M × /64AS44324MoeDove LLC62/63

More specific announcements

Announcements contained within 2a13:a5c3:3200::/40
PrefixAddressesOriginVisibility
2a13:a5c3:32e0::/441M × /64AS44324MoeDove LLC38/63

Sibling prefixes

Prefixes of the same length sharing a parent block with 2a13:a5c3:3200::/40
PrefixAddressesOriginVisibility
2a13:a5c3:3300::/4016.8M × /64AS44324MoeDove LLC63/63

History

  1. AS4432417th October 2026 — 26th October 2026
  2. AS4432412th August 2026 — 15th October 2026
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.