subnet.im

2a07:2486:4e01::/48

SharedServ LtdAS204464

At a glance

Subnets

65,536 × /64

/48 block

Visibility

32%

20 of 63 vantage points

RPKI

Valid

Registry

RIPE NCCDE

Allocated 23rd January 2024

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: 1 observed path to 2a07:2486:4e01::/48, fanning out from AS204464 toward the vantage points that see it. Each path is written out in full beneath the graph.AS204464SharedServ LtdOriginAS219157Global Capital Se…AS204464SharedServ LtdAS205941Lungu Stefan Gabr…AS400587Ryamer, LLCAS35133Eranium B.V.AS6939Hurricane Electri…AS132337Axclusive
  1. Singapore204464219157204464205941400587351336939132337This 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.

Route visibility

32%

Seen by 20 of 63 full-feed vantage points

Seen by few vantage points

Observed at 1 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
Germany
Allocated
23rd January 2024
Allocation block
2a07:2480::/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 2a07:2486:4e01::/48
ROA prefixAuthorised originMax length
2a07:2486:4e01::/48AS204464/48
2a07:2486:4e00::/40AS204464/40

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 2a07:2486:4e01::/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.2a07:2486:4e00::…AS2044642a07:2486:4e01::…AS204464This 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 2a07:2486:4e01::/48
PrefixAddressesOriginVisibility
2a07:2486:4e00::/4016.8M × /64AS204464SharedServ Ltd20/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. AS2044645th November 2026 — present
  2. AS20446430th October 2026 — 3rd November 2026
  3. AS20446427th October 2026 — 30th October 2026
  4. AS20446416th October 2026 — 16th October 2026
  5. AS20446412th August 2026 — 12th 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.