bgpreport

Network · data from 2026-11-12

AS40575 STRATOS - Stratos Global Communications

Registry name: STRATOS - Stratos Global Communications, CA · not in PeeringDB

7IPv4 routes 71.4% RPKI valid · 28.6% with a route object
2IPv6 routes 0.0% RPKI valid · 50.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
4No ROA 6 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS40575, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS40575, 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.
2601:400e:c000::/44 No ROA Other origin onlycovered by 2601:400e:c000::/36 635 100% 70
216.129.172.0/24 No ROA Other IRR onlyRADB 673 100% 67
216.129.173.0/24 No ROA Other IRR onlyRADB 673 100% 67
2601:400e:c010::/44 No ROA Other IRR onlyRADB 635 100% 70
209.128.59.0/24 Valid Other origin only 671 100% 67
209.128.60.0/24 Valid Other origin only 671 100% 67
209.128.61.0/24 Valid Other origin only 671 100% 67
209.128.62.0/24 Valid Other origin only 671 100% 67
209.128.63.0/24 Valid Other origin only 671 100% 67

AS-SET

AS40575 isn't in PeeringDB, where networks name their 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 14 are in fix.csv.

  • ROA: none4
  • Route object: none6
  • Route object: RIR3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2601:400e:c000::/44No ROA covers it. Add a ROA for AS40575, maxLength 44.635 of 636
Route object: none2601:400e:c000::/44Route objects for it name AS812. A route object for 2601:400e:c000::/36 with origin AS40575 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40575 in the RIR database for the space.635 of 636
ROA: none216.129.172.0/24No ROA covers it. Add a ROA for AS40575, maxLength 24.673 of 673
Route object: RIR216.129.172.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none216.129.173.0/24No ROA covers it. Add a ROA for AS40575, maxLength 24.673 of 673
Route object: RIR216.129.173.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none2601:400e:c010::/44No ROA covers it. Add a ROA for AS40575, maxLength 44.635 of 636
Route object: RIR2601:400e:c010::/44Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: none209.128.59.0/24Route objects for it name AS855. Add a route object with origin AS40575 in the RIR database for the space.671 of 673
Route object: none209.128.60.0/24Route objects for it name AS855. Add a route object with origin AS40575 in the RIR database for the space.671 of 673
Route object: none209.128.61.0/24Route objects for it name AS855. Add a route object with origin AS40575 in the RIR database for the space.671 of 673
Route object: none209.128.62.0/24Route objects for it name AS855. Add a route object with origin AS40575 in the RIR database for the space.671 of 673
Route object: none209.128.63.0/24Route objects for it name AS855. Add a route object with origin AS40575 in the RIR database for the space.671 of 673

Route objects not announced

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

2601:400e:c000::/36RADBNo ROA

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.