bgpreport

Network · data from 2026-11-12

AS398378 DISH-WIRELESS

Registry name: BOOST-MOBILE - Boost Mobile, US · PeeringDB

27IPv4 routes 88.9% RPKI valid · 85.2% with a route object
4IPv6 routes 50.0% RPKI valid · 50.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
5No ROA 6 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
5Route objects not announced registered with origin AS398378, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS398378, 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.

204.76.128.0/24 No ROA None 673 100% 67
204.76.130.0/24 No ROA None 673 100% 67
216.234.179.0/24 No ROA Nonecovered by 216.234.176.0/21 671 100% 67
2605:c540:c001::/48 No ROA None 635 100% 68
2605:c540:c002::/48 No ROA None 635 100% 68
206.204.93.0/24 Valid None 673 100% 67
35.33.128.0/21 Valid Other IRR onlyRADB 673 100% 68
35.33.136.0/21 Valid Other IRR onlyRADB 673 100% 68
35.33.144.0/21 Valid Other IRR onlyRADB 673 100% 69
35.33.152.0/21 Valid Other IRR onlyRADB 673 100% 69
35.33.160.0/21 Valid Other IRR onlyRADB 673 100% 69
35.33.168.0/21 Valid Other IRR onlyRADB 673 100% 69
35.33.176.0/21 Valid Other IRR onlyRADB 673 100% 69
35.33.184.0/21 Valid Other IRR onlyRADB 673 100% 69
35.33.192.0/21 Valid Other IRR onlyRADB 673 100% 68
35.33.200.0/21 Valid Other IRR onlyRADB 673 100% 68
35.33.208.0/21 Valid Other IRR onlyRADB 673 100% 68
35.33.216.0/21 Valid Other IRR onlyRADB 673 100% 68
35.33.224.0/21 Valid Other IRR onlyRADB 673 100% 68
35.33.232.0/21 Valid Other IRR onlyRADB 673 100% 68
35.33.240.0/21 Valid Other IRR onlyRADB 673 100% 68
35.33.248.0/21 Valid Other IRR onlyRADB 673 100% 68
35.39.96.0/21 Valid Other IRR onlyRADB 673 100% 68
35.39.104.0/21 Valid Other IRR onlyRADB 673 100% 68
35.39.112.0/21 Valid Other IRR onlyRADB 673 100% 69
161.188.128.0/23 Valid Other IRR onlyRADB 673 100% 68
161.188.130.0/23 Valid Other IRR onlyRADB 673 100% 69
192.189.196.0/24 Valid Other IRR onlyRADB 673 100% 68
2605:c540:8c00::/48 Valid Other IRR onlyRADB 636 100% 69
2605:c540:8c01::/48 Valid Other IRR onlyRADB 635 100% 68
216.234.183.0/24 Valid RIR databaseARIN, RADB 673 100% 69

AS-SET

AS398378'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 40 are in fix.csv.

  • ROA: none5
  • Route object: none6
  • Route object: RIR24
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none204.76.128.0/24No ROA covers it. Add a ROA for AS398378, maxLength 24.673 of 673
Route object: none204.76.128.0/24No route object for it. Add a route object with origin AS398378 in the RIR database for the space.673 of 673
ROA: none204.76.130.0/24No ROA covers it. Add a ROA for AS398378, maxLength 24.673 of 673
Route object: none204.76.130.0/24No route object for it. Add a route object with origin AS398378 in the RIR database for the space.673 of 673
ROA: none216.234.179.0/24No ROA covers it. Add a ROA for AS398378, maxLength 24.671 of 673
Route object: none216.234.179.0/24No route object for it. A route object for 216.234.176.0/21 with origin AS398378 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398378 in the RIR database for the space.671 of 673
ROA: none2605:c540:c001::/48No ROA covers it. Add a ROA for AS398378, maxLength 48.635 of 636
Route object: none2605:c540:c001::/48No route object for it. Add a route object with origin AS398378 in the RIR database for the space.635 of 636
ROA: none2605:c540:c002::/48No ROA covers it. Add a ROA for AS398378, maxLength 48.635 of 636
Route object: none2605:c540:c002::/48No route object for it. Add a route object with origin AS398378 in the RIR database for the space.635 of 636
Route object: none206.204.93.0/24No route object for it. Add a route object with origin AS398378 in the RIR database for the space.673 of 673
Route object: RIR35.33.128.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR35.33.136.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR35.33.144.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR35.33.152.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR35.33.160.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR35.33.168.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR35.33.176.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR35.33.184.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR35.33.192.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR35.33.200.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR35.33.208.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR35.33.216.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR35.33.224.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR35.33.232.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR35.33.240.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR35.33.248.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR35.39.96.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR35.39.104.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR35.39.112.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR161.188.128.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR161.188.130.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR192.189.196.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR2605:c540:8c00::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2605:c540:8c01::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

35.39.121.0/24RADBValid
161.188.150.0/23RADBValid
216.234.176.0/21RADBNo ROA
216.234.181.0/24RADBNo ROA
2605:c540:8c00::/42ARINValid

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.