bgpreport

Network · data from 2026-11-12

AS202753 GLOBALGRID

Registry name: GLOBALGRID-NETWORK GLOBALGRID SASU, FR · PeeringDB

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

Announced routes

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

154.7.4.0/22 Invalid: origin None 2 0%low visibility 2
154.7.5.0/24 Invalid: origin None 2 0%low visibility 2
154.7.6.0/24 Invalid: origin None 2 0%low visibility 2
2a06:9801:61::/48 No ROA RIR databaseRIPE 634 100% 68
2a0f:85c1:e1a::/48 No ROA RIR databaseRIPE 4 1%low visibility 3
2a06:9801:60::/48 No ROA RIR databaseRIPE 3 0%low visibility 3

AS-SET

PeeringDB's irr_as_set for AS202753: AS202753:AS-GLOBALGRID. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS202753 isn't in the set, or no route object for AS202753 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS202753 in itNot covered
AS202753:AS-GLOBALGRID RIPE 8433 Yes 3

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

  • ROA: origin3
  • ROA: none3
  • Route object: none3
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: origin154.7.4.0/22An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS202753 should announce it, add a ROA for AS202753.2 of 673
Route object: none154.7.4.0/22No route object for it. Add a route object with origin AS202753 in the RIR database for the space.2 of 673
ROA: origin154.7.5.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS202753 should announce it, add a ROA for AS202753.2 of 673
Route object: none154.7.5.0/24No route object for it. Add a route object with origin AS202753 in the RIR database for the space.2 of 673
ROA: origin154.7.6.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS202753 should announce it, add a ROA for AS202753.2 of 673
Route object: none154.7.6.0/24No route object for it. Add a route object with origin AS202753 in the RIR database for the space.2 of 673
ROA: none2a06:9801:61::/48No ROA covers it. Add a ROA for AS202753, maxLength 48.634 of 636
ROA: none2a0f:85c1:e1a::/48No ROA covers it. Add a ROA for AS202753, maxLength 48.4 of 636
ROA: none2a06:9801:60::/48No ROA covers it. Add a ROA for AS202753, maxLength 48.3 of 636

Route objects not announced

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

2a06:9801:60::/44RIPENo ROA
2a06:9801:63::/48RIPENo ROA
2a06:9801:64::/48RIPENo ROA
2a06:9801:65::/48RIPENo ROA
2a06:9801:66::/48RIPENo ROA
2a06:9801:67::/48RIPENo ROA
2a06:9801:68::/48RIPENo ROA
2a06:9801:69::/48RIPENo 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.