Network · data from 2026-11-12
AS26606 Cia de Proc. de Dado do Município de Porto Alegre
Registry name: AS26606 - Cia de Proc. de Dado do Municipio de Porto Alegre, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS26606, 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.
| 187.110.193.0/24 | Valid | Nonecovered by 187.110.192.0/20 | 672 100% |
| 187.110.194.0/24 | Valid | Nonecovered by 187.110.192.0/20 | 672 100% |
| 187.110.195.0/24 | Valid | Nonecovered by 187.110.192.0/20 | 672 100% |
| 187.110.196.0/24 | Valid | Nonecovered by 187.110.192.0/20 | 672 100% |
| 187.110.203.0/24 | Valid | Nonecovered by 187.110.192.0/20 | 672 100% |
| 187.110.205.0/24 | Valid | Nonecovered by 187.110.192.0/20 | 672 100% |
| 200.169.16.0/24 | Valid | Nonecovered by 200.169.16.0/20 | 672 100% |
| 201.7.128.0/24 | Valid | Nonecovered by 201.7.128.0/20 | 672 100% |
| 201.7.130.0/24 | Valid | Nonecovered by 201.7.128.0/20 | 672 100% |
| 201.7.131.0/24 | Valid | Nonecovered by 201.7.128.0/20 | 672 100% |
| 201.7.132.0/24 | Valid | Nonecovered by 201.7.128.0/20 | 672 100% |
| 201.7.133.0/24 | Valid | Nonecovered by 201.7.128.0/20 | 672 100% |
| 201.7.134.0/24 | Valid | Nonecovered by 201.7.128.0/20 | 672 100% |
| 201.7.135.0/24 | Valid | Nonecovered by 201.7.128.0/20 | 672 100% |
| 201.7.137.0/24 | Valid | Nonecovered by 201.7.128.0/20 | 672 100% |
| 201.7.138.0/24 | Valid | Nonecovered by 201.7.128.0/20 | 672 100% |
| 201.7.139.0/24 | Valid | Nonecovered by 201.7.128.0/20 | 672 100% |
| 201.7.140.0/24 | Valid | Nonecovered by 201.7.128.0/20 | 672 100% |
| 201.7.141.0/24 | Valid | Nonecovered by 201.7.128.0/20 | 672 100% |
| 201.7.142.0/24 | Valid | Nonecovered by 201.7.128.0/20 | 672 100% |
| 200.169.19.0/24 | Valid | Nonecovered by 200.169.16.0/20 | 671 100% |
| 200.169.20.0/24 | Valid | Nonecovered by 200.169.16.0/20 | 671 100% |
| 200.169.21.0/24 | Valid | Nonecovered by 200.169.16.0/20 | 671 100% |
| 200.169.24.0/24 | Valid | Nonecovered by 200.169.16.0/20 | 671 100% |
| 200.169.25.0/24 | Valid | Nonecovered by 200.169.16.0/20 | 671 100% |
| 200.169.26.0/24 | Valid | Nonecovered by 200.169.16.0/20 | 671 100% |
| 200.169.27.0/24 | Valid | Nonecovered by 200.169.16.0/20 | 671 100% |
| 200.169.28.0/24 | Valid | Nonecovered by 200.169.16.0/20 | 671 100% |
| 200.169.29.0/24 | Valid | Nonecovered by 200.169.16.0/20 | 671 100% |
| 200.169.30.0/24 | Valid | Nonecovered by 200.169.16.0/20 | 671 100% |
| 200.169.31.0/24 | Valid | Nonecovered by 200.169.16.0/20 | 671 100% |
| 200.169.22.0/24 | Valid | Nonecovered by 200.169.16.0/20 | 670 100% |
| 187.110.192.0/20 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 200.169.16.0/20 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 201.7.128.0/20 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 2804:f4::/32 | Valid | Other IRR onlyRADB, TC | 634 100% |
AS-SET
AS26606'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 36 are in fix.csv.
- Route object: none32
- Route object: RIR4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 187.110.193.0/24 | No route object for it. A route object for 187.110.192.0/20 with origin AS26606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26606 in the RIR database for the space. |
| Route object: none | 187.110.194.0/24 | No route object for it. A route object for 187.110.192.0/20 with origin AS26606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26606 in the RIR database for the space. |
| Route object: none | 187.110.195.0/24 | No route object for it. A route object for 187.110.192.0/20 with origin AS26606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26606 in the RIR database for the space. |
| Route object: none | 187.110.196.0/24 | No route object for it. A route object for 187.110.192.0/20 with origin AS26606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26606 in the RIR database for the space. |
| Route object: none | 187.110.203.0/24 | No route object for it. A route object for 187.110.192.0/20 with origin AS26606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26606 in the RIR database for the space. |
| Route object: none | 187.110.205.0/24 | No route object for it. A route object for 187.110.192.0/20 with origin AS26606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26606 in the RIR database for the space. |
| Route object: none | 200.169.16.0/24 | No route object for it. A route object for 200.169.16.0/20 with origin AS26606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26606 in the RIR database for the space. |
| Route object: none | 201.7.128.0/24 | No route object for it. A route object for 201.7.128.0/20 with origin AS26606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26606 in the RIR database for the space. |
| Route object: none | 201.7.130.0/24 | No route object for it. A route object for 201.7.128.0/20 with origin AS26606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26606 in the RIR database for the space. |
| Route object: none | 201.7.131.0/24 | No route object for it. A route object for 201.7.128.0/20 with origin AS26606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26606 in the RIR database for the space. |
| Route object: none | 201.7.132.0/24 | No route object for it. A route object for 201.7.128.0/20 with origin AS26606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26606 in the RIR database for the space. |
| Route object: none | 201.7.133.0/24 | No route object for it. A route object for 201.7.128.0/20 with origin AS26606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26606 in the RIR database for the space. |
| Route object: none | 201.7.134.0/24 | No route object for it. A route object for 201.7.128.0/20 with origin AS26606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26606 in the RIR database for the space. |
| Route object: none | 201.7.135.0/24 | No route object for it. A route object for 201.7.128.0/20 with origin AS26606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26606 in the RIR database for the space. |
| Route object: none | 201.7.137.0/24 | No route object for it. A route object for 201.7.128.0/20 with origin AS26606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26606 in the RIR database for the space. |
| Route object: none | 201.7.138.0/24 | No route object for it. A route object for 201.7.128.0/20 with origin AS26606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26606 in the RIR database for the space. |
| Route object: none | 201.7.139.0/24 | No route object for it. A route object for 201.7.128.0/20 with origin AS26606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26606 in the RIR database for the space. |
| Route object: none | 201.7.140.0/24 | No route object for it. A route object for 201.7.128.0/20 with origin AS26606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26606 in the RIR database for the space. |
| Route object: none | 201.7.141.0/24 | No route object for it. A route object for 201.7.128.0/20 with origin AS26606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26606 in the RIR database for the space. |
| Route object: none | 201.7.142.0/24 | No route object for it. A route object for 201.7.128.0/20 with origin AS26606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26606 in the RIR database for the space. |
| Route object: none | 200.169.19.0/24 | No route object for it. A route object for 200.169.16.0/20 with origin AS26606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26606 in the RIR database for the space. |
| Route object: none | 200.169.20.0/24 | No route object for it. A route object for 200.169.16.0/20 with origin AS26606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26606 in the RIR database for the space. |
| Route object: none | 200.169.21.0/24 | No route object for it. A route object for 200.169.16.0/20 with origin AS26606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26606 in the RIR database for the space. |
| Route object: none | 200.169.24.0/24 | No route object for it. A route object for 200.169.16.0/20 with origin AS26606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26606 in the RIR database for the space. |
| Route object: none | 200.169.25.0/24 | No route object for it. A route object for 200.169.16.0/20 with origin AS26606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26606 in the RIR database for the space. |
| Route object: none | 200.169.26.0/24 | No route object for it. A route object for 200.169.16.0/20 with origin AS26606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26606 in the RIR database for the space. |
| Route object: none | 200.169.27.0/24 | No route object for it. A route object for 200.169.16.0/20 with origin AS26606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26606 in the RIR database for the space. |
| Route object: none | 200.169.28.0/24 | No route object for it. A route object for 200.169.16.0/20 with origin AS26606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26606 in the RIR database for the space. |
| Route object: none | 200.169.29.0/24 | No route object for it. A route object for 200.169.16.0/20 with origin AS26606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26606 in the RIR database for the space. |
| Route object: none | 200.169.30.0/24 | No route object for it. A route object for 200.169.16.0/20 with origin AS26606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26606 in the RIR database for the space. |
| Route object: none | 200.169.31.0/24 | No route object for it. A route object for 200.169.16.0/20 with origin AS26606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26606 in the RIR database for the space. |
| Route object: none | 200.169.22.0/24 | No route object for it. A route object for 200.169.16.0/20 with origin AS26606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26606 in the RIR database for the space. |
| Route object: RIR | 187.110.192.0/20 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.169.16.0/20 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 201.7.128.0/20 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:f4::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS26606 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.