Network · data from 2026-11-12
AS40630 GridFury
Registry name: GRIDFURY-AS - GridFury, LLC, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS40630, 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.
| 204.13.88.0/24 | Valid | Nonecovered by 204.13.88.0/23 | 673 100% |
| 2607:ff18:8000::/35 | Valid | Nonecovered by 2607:ff18::/32 | 635 100% |
| 2607:ff18:80::/48 | Valid | Nonecovered by 2607:ff18::/32 | 632 99% |
| 204.13.89.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 204.13.90.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 204.13.88.0/22 | Valid | RIR databaseALTDB, ARIN, RADB | 671 100% |
| 208.94.116.0/22 | Valid | RIR databaseALTDB, ARIN, RADB | 671 100% |
| 2607:ff18::/32 | Valid | RIR databaseALTDB, ARIN, RADB | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS40630: ARIN::AS40630:AS-ALL. 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 (AS40630 isn't in the set, or no route object for AS40630 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 | AS40630 in it | Not covered |
|---|---|---|---|---|---|
| ARIN::AS40630:AS-ALL | ARIN | 3 | 3 | No | 8 |
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 11 are in fix.csv.
- Route object: none3
- Route object: RIR2
- AS-SET: own ASN1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 204.13.88.0/24 | No route object for it. A route object for 204.13.88.0/23 with origin AS40630 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40630 in the RIR database for the space. |
| Route object: none | 2607:ff18:8000::/35 | No route object for it. A route object for 2607:ff18::/32 with origin AS40630 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40630 in the RIR database for the space. |
| Route object: none | 2607:ff18:80::/48 | No route object for it. A route object for 2607:ff18::/32 with origin AS40630 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40630 in the RIR database for the space. |
| Route object: RIR | 204.13.89.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 204.13.90.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: own ASN | ARIN::AS40630:AS-ALL | AS40630 isn't in AS40630:AS-ALL (ARIN) once expanded. Add AS40630 to it. |
Route objects not announced
Route objects with origin AS40630 whose prefix no peer sees AS40630 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 204.13.88.0/23 | RADB | Valid |
| 204.13.90.0/23 | RADB | Valid |
| 204.13.91.0/24 | RADB | Valid |
| 2607:ff18:8000::/40 | ALTDB, RADB | Valid |
| 2607:ff18:ffff::/48 | ALTDB, RADB | 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.