subnet.im

2001:5f8:fe02::/48

Aureon Network ServicesAS5056

At a glance

Subnets

65,536 × /64

/48 block

Visibility

33%

21 of 64 vantage points

RPKI

No ROA

Registry

ARINUS

Allocated 9th May 2003

AS paths to this prefix

All paths

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

OriginVantage point · Singapore
One AS path to 2001:5f8:fe02::/48 as seen from Singapore, read outward from the origin: AS5056 → AS6939 → AS132337. Each hop is listed with its network name beneath the graph.AS5056Aureon Network Se…OriginAS6939Hurricane Electri…AS132337Axclusive

Seen from Singapore

  1. 1AS5056Aureon Network ServicesUSOrigin
    Peer of AS5056seen on 46,330 paths from 122 vantage points
  2. 2AS6939Hurricane Electric LLCUS
    Peer of AS6939seen on 478,416 paths from 2 vantage points
  3. 3AS132337AxclusiveSGVantage 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. Singapore50566939132337Shown above

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

33%

Seen by 21 of 64 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
ARIN — North America
Country
United States
Allocated
9th May 2003
Allocation block
2001:5f8::/32
Status
allocated
Origin validation
No ROA

No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 2001:5f8:fe02::/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.2001:5f8::/32AS50562001:5f8:fe02::/…AS5056This prefix2001:5f8:fe03::/…AS5056

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 2001:5f8:fe02::/48
PrefixAddressesOriginVisibility
2001:5f8::/324.3B × /64AS5056Aureon Network Services64/64

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 2001:5f8:fe02::/48
PrefixAddressesOriginVisibility
2001:5f8:fe03::/4865.5k × /64AS5056Aureon Network Services21/64

History

  1. AS505622nd October 2026 — present
  2. AS505612th August 2026 — 16th 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.