Network · data from 2026-11-12
AS31251 Falco Networks
Registry name: NETGUARD-AS Falco IPR BV, NL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS31251, 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.
| 85.203.0.0/22 | Valid | Nonecovered by 85.203.0.0/18 | 671 100% |
| 85.203.0.0/24 | Valid | Nonecovered by 85.203.0.0/18 | 671 100% |
| 85.203.2.0/24 | Valid | Nonecovered by 85.203.0.0/18 | 671 100% |
| 85.203.3.0/24 | Valid | Nonecovered by 85.203.0.0/18 | 671 100% |
| 85.203.6.0/24 | Valid | Nonecovered by 85.203.0.0/18 | 671 100% |
| 85.203.12.0/24 | Valid | Nonecovered by 85.203.0.0/18 | 671 100% |
| 2a03:60c0::/29 | Valid | None | 635 100% |
| 85.203.5.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 2a02:a10::/29 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS31251's PeeringDB record names no 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 10 are in fix.csv.
- Route object: none7
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 85.203.0.0/22 | No route object for it. A route object for 85.203.0.0/18 with origin AS31251 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31251 in the RIR database for the space. |
| Route object: none | 85.203.0.0/24 | No route object for it. A route object for 85.203.0.0/18 with origin AS31251 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31251 in the RIR database for the space. |
| Route object: none | 85.203.2.0/24 | No route object for it. A route object for 85.203.0.0/18 with origin AS31251 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31251 in the RIR database for the space. |
| Route object: none | 85.203.3.0/24 | No route object for it. A route object for 85.203.0.0/18 with origin AS31251 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31251 in the RIR database for the space. |
| Route object: none | 85.203.6.0/24 | No route object for it. A route object for 85.203.0.0/18 with origin AS31251 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31251 in the RIR database for the space. |
| Route object: none | 85.203.12.0/24 | No route object for it. A route object for 85.203.0.0/18 with origin AS31251 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31251 in the RIR database for the space. |
| Route object: none | 2a03:60c0::/29 | No route object for it. Add a route object with origin AS31251 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS31251 whose prefix no peer sees AS31251 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 85.203.0.0/18 | RIPE | No ROA |
| 85.203.11.0/24 | RIPE | No ROA |
| 2a03:60c1::/32 | RIPE | Invalid: maxLength |
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.