subnet.im

2403:bc00:8000::/48

AIMS Data Centre Sdn BhdAS45668

At a glance

Subnets

65,536 × /64

/48 block

Visibility

100%

62 of 62 vantage points

RPKI

Valid

Registry

APNICMY

Allocated 14th January 2010

AS paths to this prefix

All paths

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

OriginVantage point · Sao Paulo
One AS path to 2403:bc00:8000::/48 as seen from Sao Paulo, read outward from the origin: AS45668 → AS2914 → AS12956 → AS32590. Each hop is listed with its network name beneath the graph.AS45668AIMS Data Centre …OriginAS2914NTT America, Inc.AS12956Telxius (Telefoni…AS32590Valve Corporation

Seen from Sao Paulo

  1. 1AS45668AIMS Data Centre Sdn BhdMYOrigin
    Peer of AS45668seen on 1,307 paths from 110 vantage points
  2. 2AS2914NTT America, Inc.US
    Peer of AS2914seen on 136,245 paths from 8 vantage points
  3. 3AS12956Telxius (Telefonica Global)ES
    Peer of AS12956seen on 476,587 paths from 4 vantage points
  4. 4AS32590Valve CorporationUSVantage 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. Amsterdam456689930213151This path
  2. London, UK45668993051907This path
  3. Singapore456689930132337This path
  4. Sao Paulo4566829141295632590Shown 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. A heavier line in the graph means more vantage points reach the prefix that same way.

Route visibility

100%

Seen by 62 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
APNIC — Asia-Pacific
Country
Malaysia
Allocated
14th January 2010
Allocation block
2403:bc00::/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 2403:bc00:8000::/48
ROA prefixAuthorised originMax length
2403:bc00:8000::/48AS45668/48
2403:bc00::/32AS45668/32

Prefix hierarchy

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

Covering announcements

No less specific announcement covers this prefix.

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 2403:bc00:8000::/48
PrefixAddressesOriginVisibility
2403:bc00:8001::/4865.5k × /64AS45668AIMS Data Centre Sdn Bhd62/62

History

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