Network · data from 2026-11-12
AS41765 IPGarde
Registry name: IPGARDE-AS IPGarde SAS, FR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS41765, 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.
| 185.233.48.10/32 | Valid | Nonecovered by 185.233.48.0/24 | 3 0%low visibility |
| 31.172.164.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 82.138.64.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.4.63.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.84.112.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.233.48.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.65.168.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 193.33.46.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 193.37.150.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.8.233.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.8.234.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.8.235.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.57.96.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2a02:2288::/29 | Valid | RIR databaseRIPE | 634 100% |
| 2a0c:d500::/29 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS41765: AS-IPGARDE-CUST. 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 (AS41765 isn't in the set, or no route object for AS41765 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.
| Name | Database | ASNs | Sets | AS41765 in it | Not covered |
|---|---|---|---|---|---|
| AS-IPGARDE-CUST | RIPE | 4 | 1 | Yes | 1 |
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 4 are in fix.csv.
- Route object: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 185.233.48.10/32 | No route object for it. A route object for 185.233.48.0/24 with origin AS41765 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS41765 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS41765 whose prefix no peer sees AS41765 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.233.48.0/22 | RIPE | Valid |
| 185.233.50.0/23 | RIPE | Valid |
| 2a02:2288::/32 | RIPE | Valid |
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.