Network · data from 2026-11-12
AS27987 NODOCOOP Federación de Cooperativas
Registry name: AS27987 - NODOCOOP Federacion de Cooperativas Ltda., AR · PeeringDB
28IPv4 routes
100.0% RPKI valid · 14.3% with a route object
1IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
24 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
9Route objects not announced
registered with origin AS27987, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS27987, 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.
| 181.189.168.0/24 | Valid | Nonecovered by 181.189.168.0/23 | 668 99% |
| 181.189.169.0/24 | Valid | Nonecovered by 181.189.168.0/23 | 668 99% |
| 181.189.174.0/24 | Valid | Nonecovered by 181.189.174.0/23 | 668 99% |
| 181.189.175.0/24 | Valid | Nonecovered by 181.189.174.0/23 | 668 99% |
| 186.190.176.0/24 | Valid | Nonecovered by 186.190.176.0/22 | 668 99% |
| 186.190.177.0/24 | Valid | Nonecovered by 186.190.176.0/22 | 668 99% |
| 186.190.178.0/24 | Valid | Nonecovered by 186.190.176.0/22 | 668 99% |
| 186.190.179.0/24 | Valid | Nonecovered by 186.190.176.0/22 | 668 99% |
| 186.190.182.0/24 | Valid | Nonecovered by 186.190.182.0/23 | 668 99% |
| 186.190.183.0/24 | Valid | Nonecovered by 186.190.182.0/23 | 668 99% |
| 186.190.184.0/24 | Valid | Nonecovered by 186.190.184.0/23 | 668 99% |
| 186.190.185.0/24 | Valid | Nonecovered by 186.190.184.0/23 | 668 99% |
| 186.190.190.0/24 | Valid | Nonecovered by 186.190.190.0/23 | 668 99% |
| 186.190.191.0/24 | Valid | Nonecovered by 186.190.190.0/23 | 668 99% |
| 190.103.192.0/24 | Valid | Nonecovered by 190.103.192.0/22 | 667 99% |
| 190.103.193.0/24 | Valid | Nonecovered by 190.103.192.0/22 | 667 99% |
| 190.103.194.0/24 | Valid | Nonecovered by 190.103.192.0/22 | 667 99% |
| 190.103.195.0/24 | Valid | Nonecovered by 190.103.192.0/22 | 667 99% |
| 190.103.198.0/24 | Valid | Nonecovered by 190.103.198.0/23 | 667 99% |
| 190.103.199.0/24 | Valid | Nonecovered by 190.103.198.0/23 | 667 99% |
| 190.103.200.0/24 | Valid | Nonecovered by 190.103.200.0/22 | 667 99% |
| 190.103.201.0/24 | Valid | Nonecovered by 190.103.200.0/22 | 667 99% |
| 190.103.202.0/24 | Valid | Nonecovered by 190.103.200.0/22 | 667 99% |
| 190.103.203.0/24 | Valid | Nonecovered by 190.103.200.0/22 | 667 99% |
| 168.227.206.0/24 | Valid | RIR databaseLACNIC | 672 100% |
| 181.189.171.0/24 | Valid | RIR databaseLACNIC | 668 99% |
| 190.103.204.0/24 | Valid | RIR databaseLACNIC | 667 99% |
| 190.103.207.0/24 | Valid | RIR databaseLACNIC | 667 99% |
| 2803:8500::/32 | Valid | RIR databaseLACNIC | 633 100% |
AS-SET
AS27987'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 33 are in fix.csv.
- Route object: none24
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 181.189.168.0/24 | No route object for it. A route object for 181.189.168.0/23 with origin AS27987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27987 in the RIR database for the space. |
| Route object: none | 181.189.169.0/24 | No route object for it. A route object for 181.189.168.0/23 with origin AS27987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27987 in the RIR database for the space. |
| Route object: none | 181.189.174.0/24 | No route object for it. A route object for 181.189.174.0/23 with origin AS27987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27987 in the RIR database for the space. |
| Route object: none | 181.189.175.0/24 | No route object for it. A route object for 181.189.174.0/23 with origin AS27987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27987 in the RIR database for the space. |
| Route object: none | 186.190.176.0/24 | No route object for it. A route object for 186.190.176.0/22 with origin AS27987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27987 in the RIR database for the space. |
| Route object: none | 186.190.177.0/24 | No route object for it. A route object for 186.190.176.0/22 with origin AS27987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27987 in the RIR database for the space. |
| Route object: none | 186.190.178.0/24 | No route object for it. A route object for 186.190.176.0/22 with origin AS27987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27987 in the RIR database for the space. |
| Route object: none | 186.190.179.0/24 | No route object for it. A route object for 186.190.176.0/22 with origin AS27987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27987 in the RIR database for the space. |
| Route object: none | 186.190.182.0/24 | No route object for it. A route object for 186.190.182.0/23 with origin AS27987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27987 in the RIR database for the space. |
| Route object: none | 186.190.183.0/24 | No route object for it. A route object for 186.190.182.0/23 with origin AS27987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27987 in the RIR database for the space. |
| Route object: none | 186.190.184.0/24 | No route object for it. A route object for 186.190.184.0/23 with origin AS27987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27987 in the RIR database for the space. |
| Route object: none | 186.190.185.0/24 | No route object for it. A route object for 186.190.184.0/23 with origin AS27987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27987 in the RIR database for the space. |
| Route object: none | 186.190.190.0/24 | No route object for it. A route object for 186.190.190.0/23 with origin AS27987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27987 in the RIR database for the space. |
| Route object: none | 186.190.191.0/24 | No route object for it. A route object for 186.190.190.0/23 with origin AS27987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27987 in the RIR database for the space. |
| Route object: none | 190.103.192.0/24 | No route object for it. A route object for 190.103.192.0/22 with origin AS27987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27987 in the RIR database for the space. |
| Route object: none | 190.103.193.0/24 | No route object for it. A route object for 190.103.192.0/22 with origin AS27987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27987 in the RIR database for the space. |
| Route object: none | 190.103.194.0/24 | No route object for it. A route object for 190.103.192.0/22 with origin AS27987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27987 in the RIR database for the space. |
| Route object: none | 190.103.195.0/24 | No route object for it. A route object for 190.103.192.0/22 with origin AS27987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27987 in the RIR database for the space. |
| Route object: none | 190.103.198.0/24 | No route object for it. A route object for 190.103.198.0/23 with origin AS27987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27987 in the RIR database for the space. |
| Route object: none | 190.103.199.0/24 | No route object for it. A route object for 190.103.198.0/23 with origin AS27987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27987 in the RIR database for the space. |
| Route object: none | 190.103.200.0/24 | No route object for it. A route object for 190.103.200.0/22 with origin AS27987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27987 in the RIR database for the space. |
| Route object: none | 190.103.201.0/24 | No route object for it. A route object for 190.103.200.0/22 with origin AS27987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27987 in the RIR database for the space. |
| Route object: none | 190.103.202.0/24 | No route object for it. A route object for 190.103.200.0/22 with origin AS27987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27987 in the RIR database for the space. |
| Route object: none | 190.103.203.0/24 | No route object for it. A route object for 190.103.200.0/22 with origin AS27987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27987 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS27987 whose prefix no peer sees AS27987 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 181.189.168.0/23 | LACNIC | Valid |
| 181.189.174.0/23 | LACNIC | Valid |
| 186.190.176.0/22 | LACNIC | Valid |
| 186.190.182.0/23 | LACNIC | Valid |
| 186.190.184.0/23 | LACNIC | Valid |
| 186.190.190.0/23 | LACNIC | Valid |
| 190.103.192.0/22 | LACNIC | Valid |
| 190.103.198.0/23 | LACNIC | Valid |
| 190.103.200.0/22 | LACNIC | 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.