bgpreport

Network · data from 2026-11-12

AS399454 GLS-NSH1-01 - Global Linking Solutions

Registry name: GLS-NSH1-01 - Global Linking Solutions, US · not in PeeringDB

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

Announced routes

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

209.136.246.0/24 No ROA None 673 100% 67
2602:f88c:1::/48 No ROA None 635 100% 68
2602:f88c::/40 No ROA None 283 44% 54

AS-SET

AS399454 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 6 are in fix.csv.

  • ROA: none3
  • Route object: none3
ChangePrefix or setDetailFull-table peers
ROA: none209.136.246.0/24No ROA covers it. Add a ROA for AS399454, maxLength 24.673 of 673
Route object: none209.136.246.0/24No route object for it. Add a route object with origin AS399454 in the RIR database for the space.673 of 673
ROA: none2602:f88c:1::/48No ROA covers it. Add a ROA for AS399454, maxLength 48.635 of 636
Route object: none2602:f88c:1::/48No route object for it. Add a route object with origin AS399454 in the RIR database for the space.635 of 636
ROA: none2602:f88c::/40No ROA covers it. Add a ROA for AS399454, maxLength 40.283 of 636
Route object: none2602:f88c::/40No route object for it. Add a route object with origin AS399454 in the RIR database for the space.283 of 636

Route objects not announced

Every route object with origin AS399454 is announced.

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.