SUBNET.IM

2405:acc0:1306::/48

DISH MEDIA NETWORK PUBLIC LIMITEDAS139922

At a glance

Subnets

65,536 × /64

/48 block

Visibility

100%

62 of 62 vantage points

RPKI

Valid

Registry

APNICNP

Allocated 3rd January 2020

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: 4 observed paths to 2405:acc0:1306::/48, fanning out from AS139922 toward the vantage points that see it. Each path is written out in full beneath the graph.AS139922DISH MEDIA NETWOR…OriginAS132799DISH MEDIA NETWOR…AS45650VIA NET COMMUNICA…AS9498Bharti Airtel Ltd.AS213151Christian ElsenAS51907Kanton ZugAS32590Valve CorporationAS132337Axclusive
  1. Amsterdam139922132799456509498213151This path
  2. London, UK13992213279945650949851907This path
  3. Sao Paulo13992213279945650949832590This path
  4. Singapore139922132799456509498132337This 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

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
Nepal
Allocated
3rd January 2020
Allocation block
2405:acc0::/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 2405:acc0:1306::/48
ROA prefixAuthorised originMax length
2405:acc0:1306::/48AS139922/48
2405:acc0::/32AS139922/32

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 2405:acc0:1306::/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.2405:acc0::/32AS1399222405:acc0:1306::…AS139922This prefix2405:acc0:1307::…AS139922

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 2405:acc0:1306::/48
PrefixAddressesOriginVisibility
2405:acc0::/324.3B × /64AS139922DISH MEDIA NETWORK PUBLIC LIMITED62/62

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 2405:acc0:1306::/48
PrefixAddressesOriginVisibility
2405:acc0:1307::/4865.5k × /64AS139922DISH MEDIA NETWORK PUBLIC LIMITED61/62

History

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