bgpreport

Network · data from 2026-11-12

AS29169 Gandi

Registry name: GANDI-AS GANDI SAS, FR · PeeringDB

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

Announced routes

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

155.133.128.0/18 No ROA RIR databaseRIPE 672 100% 67
2001:4b98:e01::/48 Valid Nonecovered by 2001:4b98::/32 636 100% 68
46.226.108.0/22 Valid RIR databaseRIPE 672 100% 67
173.246.96.0/20 Valid RIR databaseARIN 672 100% 67
185.26.124.0/22 Valid RIR databaseRIPE 672 100% 67
213.167.228.0/22 Valid RIR databaseRIPE 672 100% 67
213.167.240.0/20 Valid RIR databaseRIPE 672 100% 67
217.70.176.0/20 Valid RIR databaseRIPE 669 99% 67
217.70.184.0/24 Valid RIR databaseRIPE 668 99% 67
2604:3400::/32 Valid RIR databaseARIN 635 100% 68
2604:3400:800::/48 Valid RIR databaseARIN 634 100% 68
2001:4b98::/32 Valid RIR databaseRIPE 632 99% 68

AS-SET

PeeringDB's irr_as_set for AS29169: AS-GANDI. 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 (AS29169 isn't in the set, or no route object for AS29169 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 objectsAS29169 in itNot covered
AS-GANDI RIPElists itself further down 7138429 Yes 0

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

  • ROA: none1
  • Route object: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none155.133.128.0/18No ROA covers it. Add a ROA for AS29169, maxLength 18.672 of 673
Route object: none2001:4b98:e01::/48No route object for it. A route object for 2001:4b98::/32 with origin AS29169 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29169 in the RIR database for the space.636 of 636

Route objects not announced

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

46.226.104.0/21RIPEValid
192.69.248.0/21ARINValid
2001:4b99::/48RIPEValid

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.