subnet.im

2401:3300:ff::/48

Drik ICT LtdAS55828

At a glance

Subnets

65,536 × /64

/48 block

Visibility

16%

10 of 62 vantage points

RPKI

Invalid

Registry

APNICBD

Allocated 15th June 2011

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 2401:3300:ff::/48 as seen from Singapore, read outward from the origin: AS55828 → AS58682 → AS9498 → AS6939 → AS132337. Each hop is listed with its network name beneath the graph.AS55828Drik ICT LtdOriginAS58682Level3 Carrier Lt…AS9498Bharti Airtel Ltd.AS6939Hurricane Electri…AS132337Axclusive

Seen from Singapore

  1. 1AS55828Drik ICT LtdBDOrigin
    Peer of AS55828seen on 1,090 paths from 90 vantage points
  2. 2AS58682Level3 Carrier Ltd.BD
    Peer of AS58682seen on 16,037 paths from 141 vantage points
  3. 3AS9498Bharti Airtel Ltd.IN
    Peer of AS9498seen on 184,654 paths from 67 vantage points
  4. 4AS6939Hurricane Electric LLCUS
    Peer of AS6939seen on 320,794 paths from 2 vantage points
  5. 5AS132337AxclusiveSGVantage 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. Amsterdam558285868294986939213151This path
  2. Singapore558285868294986939132337Shown above
  3. London, UK558285868294986939419133428851907This 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. A heavier line in the graph means more vantage points reach the prefix that same way.

Route visibility

16%

Seen by 10 of 62 full-feed vantage points

Seen by few vantage points

Observed at 3 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
Bangladesh
Allocated
15th June 2011
Allocation block
2401:3300::/32
Status
allocated
Origin validation
Invalid

A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.

ROAs covering this prefix

Route Origin Authorisations covering 2401:3300:ff::/48
ROA prefixAuthorised originMax length
2401:3300::/40AS55828/40
2401:3300::/39AS55828/39
2401:3300::/38AS55828/38
2401:3300::/37AS55828/37
2401:3300::/36AS55828/36
2401:3300::/35AS55828/35
2401:3300::/34AS55828/34
2401:3300::/33AS55828/33
2401:3300::/32AS55828/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

No prefix of the same length in the same parent block is announced.

History

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