Network · data from 2026-11-12
AS209377 FOURCONSULT 4Consult B.V.
Registry name: FOURCONSULT 4Consult B.V., NL · not in PeeringDB
2IPv4 routes
100.0% RPKI valid · 50.0% with a route object
11IPv6 routes
100.0% RPKI valid · 9.1% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
11 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS209377, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS209377, 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.
| 152.89.4.0/24 | Valid | Nonecovered by 152.89.4.0/22 | 673 100% |
| 2a09:2c40:a::/48 | Valid | Nonecovered by 2a09:2c40::/29 | 634 100% |
| 2a09:2c40:b::/48 | Valid | Nonecovered by 2a09:2c40::/29 | 634 100% |
| 2a09:2c40:c::/48 | Valid | Nonecovered by 2a09:2c40::/29 | 634 100% |
| 2a09:2c40:d::/48 | Valid | Nonecovered by 2a09:2c40::/29 | 634 100% |
| 2a09:2c40:e::/48 | Valid | Nonecovered by 2a09:2c40::/29 | 634 100% |
| 2a09:2c40:f::/48 | Valid | Nonecovered by 2a09:2c40::/29 | 634 100% |
| 2a09:2c40:10::/48 | Valid | Nonecovered by 2a09:2c40::/29 | 634 100% |
| 2a09:2c40:11::/48 | Valid | Nonecovered by 2a09:2c40::/29 | 634 100% |
| 2a09:2c40:12::/48 | Valid | Nonecovered by 2a09:2c40::/29 | 634 100% |
| 2a09:2c40:13::/48 | Valid | Nonecovered by 2a09:2c40::/29 | 634 100% |
| 152.89.4.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 2a09:2c40::/29 | Valid | RIR databaseRIPE | 633 100% |
AS-SET
AS209377 isn't in PeeringDB, where networks name their 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 11 are in fix.csv.
- Route object: none11
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 152.89.4.0/24 | No route object for it. A route object for 152.89.4.0/22 with origin AS209377 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209377 in the RIR database for the space. |
| Route object: none | 2a09:2c40:a::/48 | No route object for it. A route object for 2a09:2c40::/29 with origin AS209377 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209377 in the RIR database for the space. |
| Route object: none | 2a09:2c40:b::/48 | No route object for it. A route object for 2a09:2c40::/29 with origin AS209377 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209377 in the RIR database for the space. |
| Route object: none | 2a09:2c40:c::/48 | No route object for it. A route object for 2a09:2c40::/29 with origin AS209377 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209377 in the RIR database for the space. |
| Route object: none | 2a09:2c40:d::/48 | No route object for it. A route object for 2a09:2c40::/29 with origin AS209377 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209377 in the RIR database for the space. |
| Route object: none | 2a09:2c40:e::/48 | No route object for it. A route object for 2a09:2c40::/29 with origin AS209377 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209377 in the RIR database for the space. |
| Route object: none | 2a09:2c40:f::/48 | No route object for it. A route object for 2a09:2c40::/29 with origin AS209377 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209377 in the RIR database for the space. |
| Route object: none | 2a09:2c40:10::/48 | No route object for it. A route object for 2a09:2c40::/29 with origin AS209377 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209377 in the RIR database for the space. |
| Route object: none | 2a09:2c40:11::/48 | No route object for it. A route object for 2a09:2c40::/29 with origin AS209377 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209377 in the RIR database for the space. |
| Route object: none | 2a09:2c40:12::/48 | No route object for it. A route object for 2a09:2c40::/29 with origin AS209377 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209377 in the RIR database for the space. |
| Route object: none | 2a09:2c40:13::/48 | No route object for it. A route object for 2a09:2c40::/29 with origin AS209377 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209377 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS209377 is announced.
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.