subnet.im

2400:dce0::/48

MUX BROADBAND (PRIVATE) LIMITEDAS141421

At a glance

Subnets

65,536 × /64

/48 block

Visibility

98%

61 of 62 vantage points

RPKI

Valid

Registry

APNICPK

Allocated 8th February 2023

AS paths to this prefix

All paths

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

OriginVantage point · London, UK
One AS path to 2400:dce0::/48 as seen from London, UK, read outward from the origin: AS141421 → AS141023 → AS17557 → AS51907. Each hop is listed with its network name beneath the graph.AS141421MUX BROADBAND (PR…OriginAS141023HG TELECOMMUNICAT…AS17557Pakistan Telecomm…AS51907Kanton Zug

Seen from London, UK

  1. 1AS141421MUX BROADBAND (PRIVATE) LIMITEDPKOrigin
    Peer of AS141421seen on 141 paths from 141 vantage points
  2. 2AS141023HG TELECOMMUNICATION PRIVATE LIMITEDPK
    Peer of AS141023seen on 522 paths from 141 vantage points
  3. 3AS17557Pakistan Telecommunication Company LimitedPK
    Peer of AS17557seen on 4,464 paths from 2 vantage points
  4. 4AS51907Kanton ZugCHVantage 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. Amsterdam14142114102317557213151This path
  2. London, UK1414211410231755751907Shown above
  3. Singapore141421141023175576939132337This path
  4. Sao Paulo14142114102317557852913740932590This 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

98%

Seen by 61 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
Pakistan
Allocated
8th February 2023
Allocation block
2400:dce0::/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 2400:dce0::/48
ROA prefixAuthorised originMax length
2400:dce0::/48AS141421/48

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 2400:dce0::/48
PrefixAddressesOriginVisibility
2400:dce0:1::/4865.5k × /64AS141421MUX BROADBAND (PRIVATE) LIMITED62/62

History

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