bgpreport

Network · data from 2026-11-12

AS139922 DISH MEDIA NETWORK PUBLIC LIMITED

Registry name: DMNPL-AS-AP - DISH MEDIA NETWORK PUBLIC LIMITED, NP · PeeringDB

31IPv4 routes 100.0% RPKI valid · 100.0% with a route object
26IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
22Route objects not announced registered with origin AS139922, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS139922, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

103.174.168.0/23 Valid RIR databaseAPNIC 673 100% 66
103.174.168.0/24 Valid RIR databaseAPNIC 673 100% 66
103.191.130.0/23 Valid RIR databaseAPNIC 673 100% 66
103.123.61.0/24 Valid RIR databaseAPNIC 672 100% 66
103.139.152.0/24 Valid RIR databaseAPNIC 672 100% 67
103.147.62.0/24 Valid RIR databaseAPNIC 672 100% 67
103.156.97.0/24 Valid RIR databaseAPNIC 672 100% 67
103.174.169.0/24 Valid RIR databaseAPNIC 672 100% 67
103.180.240.0/23 Valid RIR databaseAPNIC 672 100% 66
103.180.240.0/24 Valid RIR databaseAPNIC 672 100% 66
103.180.241.0/24 Valid RIR databaseAPNIC 672 100% 66
103.181.226.0/24 Valid RIR databaseAPNIC 672 100% 67
103.181.227.0/24 Valid RIR databaseAPNIC 672 100% 66
103.182.174.0/24 Valid RIR databaseAPNIC 672 100% 67
103.190.40.0/24 Valid RIR databaseAPNIC 672 100% 67
103.190.41.0/24 Valid RIR databaseAPNIC 672 100% 67
103.191.130.0/24 Valid RIR databaseAPNIC 672 100% 66
103.191.131.0/24 Valid RIR databaseAPNIC 672 100% 67
160.250.254.0/24 Valid RIR databaseAPNIC 672 100% 67
160.250.255.0/24 Valid RIR databaseAPNIC 672 100% 67
103.123.60.0/23 Valid RIR databaseAPNIC 671 100% 66
103.147.62.0/23 Valid RIR databaseAPNIC 671 100% 66
103.174.84.0/23 Valid RIR databaseAPNIC 671 100% 66
103.174.84.0/24 Valid RIR databaseAPNIC 671 100% 67
103.181.226.0/23 Valid RIR databaseAPNIC 671 100% 66
103.182.175.0/24 Valid RIR databaseAPNIC 671 100% 66
103.190.40.0/23 Valid RIR databaseAPNIC 671 100% 66
160.250.254.0/23 Valid RIR databaseAPNIC 671 100% 66
103.123.60.0/24 Valid RIR databaseAPNIC 669 99% 67
103.147.63.0/24 Valid RIR databaseAPNIC 669 99% 67
103.174.85.0/24 Valid RIR databaseAPNIC 669 99% 67
2001:df7:cc80::/48 Valid RIR databaseAPNIC 636 100% 70
2405:acc0:4::/48 Valid RIR databaseAPNIC 636 100% 70
2405:acc0:1306::/48 Valid RIR databaseAPNIC 636 100% 70
2405:acc0:1510::/48 Valid RIR databaseAPNIC 636 100% 70
2405:acc0::/32 Valid RIR databaseAPNIC 635 100% 70
2405:acc0:7::/48 Valid RIR databaseAPNIC 635 100% 70
2405:acc0:1210::/48 Valid RIR databaseAPNIC 635 100% 70
2405:acc0:1304::/48 Valid RIR databaseAPNIC 635 100% 70
2405:acc0:1307::/48 Valid RIR databaseAPNIC 635 100% 70
2405:acc0:1410::/48 Valid RIR databaseAPNIC 635 100% 70
2001:df7:be80::/48 Valid RIR databaseAPNIC 634 100% 69
2405:acc0:1::/48 Valid RIR databaseAPNIC 634 100% 69
2405:acc0:169::/48 Valid RIR databaseAPNIC 634 100% 69
2405:acc0:1100::/40 Valid RIR databaseAPNIC 634 100% 69
2405:acc0:1204::/48 Valid RIR databaseAPNIC 634 100% 69
2405:acc0:1207::/48 Valid RIR databaseAPNIC 634 100% 69
2405:acc0:1504::/48 Valid RIR databaseAPNIC 634 100% 69
2405:acc0:1505::/48 Valid RIR databaseAPNIC 634 100% 69
2405:acc0:6::/48 Valid RIR databaseAPNIC 633 100% 69
2405:acc0:8::/48 Valid RIR databaseAPNIC 633 100% 69
2405:acc0:9::/48 Valid RIR databaseAPNIC 633 100% 69
2405:acc0:a::/48 Valid RIR databaseAPNIC 633 100% 69
2405:acc0:b::/48 Valid RIR databaseAPNIC 633 100% 69
2405:acc0:c::/48 Valid RIR databaseAPNIC 633 100% 69
2405:acc0:1205::/48 Valid RIR databaseAPNIC 633 100% 69
2405:acc0:1310::/48 Valid RIR databaseAPNIC 633 100% 69

AS-SET

AS139922's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 22 are in fix.csv.

  • Route object: not announced22

Route objects not announced

Route objects with origin AS139922 whose prefix no peer sees AS139922 announce. Many are kept on purpose (backup routes, space announced only in some places).

103.182.174.0/23APNICValid
204.115.248.0/22APNICValid
204.115.248.0/23APNICValid
204.115.248.0/24APNICValid
204.115.249.0/24APNICValid
204.115.250.0/23APNICValid
204.115.250.0/24APNICValid
204.115.251.0/24APNICValid
2001:df0:6240::/48APNICValid
2001:df0:7dc0::/48APNICValid
2001:df0:8140::/48APNICValid
2001:df0:8180::/48APNICValid
2001:df0:e440::/48APNICValid
2001:df1:2c0::/48APNICValid
2001:df2:32c0::/48APNICValid
2405:acc0::/48APNICValid
2405:acc0:1000::/40APNICValid
2405:acc0:1200::/48APNICValid
2405:acc0:1206::/48APNICValid
2405:acc0:1300::/48APNICValid
2405:acc0:1305::/48APNICValid
2405:acc0:1400::/48APNICValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.