subnet.im

2a0a:3e45:3::/48

Not announced at this prefix length

We do not see 2a0a:3e45:3::/48 announced as its own route. The most specific announcement covering it is 2a0a:3e40::/29, originated by AS210152 (Jon Vanvik trading as Vanvik Internet). Traffic to addresses in this block follows that route.

At a glance

Subnets

65,536 × /64

/48 block

Visibility

Unknown

RPKI

Unknown

Registry

RIPE NCCNO

Allocated 3rd February 2026

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
Norway
Allocated
3rd February 2026
Allocation block
2a0a:3e40::/29
Status
allocated
Origin validation
Unknown

ROAs covering this prefix

Route Origin Authorisations covering 2a0a:3e45:3::/48
ROA prefixAuthorised originMax length
2a0a:3e45::/40AS215295/48
2a0a:3e40::/29AS210152/32

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 2a0a:3e45:3::/48: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.2a0a:3e40::/29AS2101522a0a:3e45:3::/48This prefix

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 2a0a:3e45:3::/48
PrefixAddressesOriginVisibility
2a0a:3e40::/2934.4B × /64AS210152Jon Vanvik trading as Vanvik Internet62/63

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. AS21529512th October 2026 — 25th 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.