bgpreport

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

35IPv4 routes 100.0% RPKI valid · 8.6% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 32 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS26606, seen from no peer

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% 66
187.110.194.0/24 Valid Nonecovered by 187.110.192.0/20 672 100% 66
187.110.195.0/24 Valid Nonecovered by 187.110.192.0/20 672 100% 66
187.110.196.0/24 Valid Nonecovered by 187.110.192.0/20 672 100% 66
187.110.203.0/24 Valid Nonecovered by 187.110.192.0/20 672 100% 66
187.110.205.0/24 Valid Nonecovered by 187.110.192.0/20 672 100% 66
200.169.16.0/24 Valid Nonecovered by 200.169.16.0/20 672 100% 66
201.7.128.0/24 Valid Nonecovered by 201.7.128.0/20 672 100% 66
201.7.130.0/24 Valid Nonecovered by 201.7.128.0/20 672 100% 66
201.7.131.0/24 Valid Nonecovered by 201.7.128.0/20 672 100% 66
201.7.132.0/24 Valid Nonecovered by 201.7.128.0/20 672 100% 66
201.7.133.0/24 Valid Nonecovered by 201.7.128.0/20 672 100% 66
201.7.134.0/24 Valid Nonecovered by 201.7.128.0/20 672 100% 66
201.7.135.0/24 Valid Nonecovered by 201.7.128.0/20 672 100% 66
201.7.137.0/24 Valid Nonecovered by 201.7.128.0/20 672 100% 66
201.7.138.0/24 Valid Nonecovered by 201.7.128.0/20 672 100% 66
201.7.139.0/24 Valid Nonecovered by 201.7.128.0/20 672 100% 66
201.7.140.0/24 Valid Nonecovered by 201.7.128.0/20 672 100% 66
201.7.141.0/24 Valid Nonecovered by 201.7.128.0/20 672 100% 66
201.7.142.0/24 Valid Nonecovered by 201.7.128.0/20 672 100% 66
200.169.19.0/24 Valid Nonecovered by 200.169.16.0/20 671 100% 66
200.169.20.0/24 Valid Nonecovered by 200.169.16.0/20 671 100% 66
200.169.21.0/24 Valid Nonecovered by 200.169.16.0/20 671 100% 66
200.169.24.0/24 Valid Nonecovered by 200.169.16.0/20 671 100% 66
200.169.25.0/24 Valid Nonecovered by 200.169.16.0/20 671 100% 66
200.169.26.0/24 Valid Nonecovered by 200.169.16.0/20 671 100% 66
200.169.27.0/24 Valid Nonecovered by 200.169.16.0/20 671 100% 66
200.169.28.0/24 Valid Nonecovered by 200.169.16.0/20 671 100% 66
200.169.29.0/24 Valid Nonecovered by 200.169.16.0/20 671 100% 66
200.169.30.0/24 Valid Nonecovered by 200.169.16.0/20 671 100% 66
200.169.31.0/24 Valid Nonecovered by 200.169.16.0/20 671 100% 66
200.169.22.0/24 Valid Nonecovered by 200.169.16.0/20 670 100% 66
187.110.192.0/20 Valid Other IRR onlyRADB, TC 672 100% 66
200.169.16.0/20 Valid Other IRR onlyRADB, TC 672 100% 66
201.7.128.0/20 Valid Other IRR onlyRADB, TC 672 100% 66
2804:f4::/32 Valid Other IRR onlyRADB, TC 634 100% 67

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
ChangePrefix or setDetailFull-table peers
Route object: none187.110.193.0/24No 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.672 of 673
Route object: none187.110.194.0/24No 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.672 of 673
Route object: none187.110.195.0/24No 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.672 of 673
Route object: none187.110.196.0/24No 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.672 of 673
Route object: none187.110.203.0/24No 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.672 of 673
Route object: none187.110.205.0/24No 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.672 of 673
Route object: none200.169.16.0/24No 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.672 of 673
Route object: none201.7.128.0/24No 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.672 of 673
Route object: none201.7.130.0/24No 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.672 of 673
Route object: none201.7.131.0/24No 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.672 of 673
Route object: none201.7.132.0/24No 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.672 of 673
Route object: none201.7.133.0/24No 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.672 of 673
Route object: none201.7.134.0/24No 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.672 of 673
Route object: none201.7.135.0/24No 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.672 of 673
Route object: none201.7.137.0/24No 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.672 of 673
Route object: none201.7.138.0/24No 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.672 of 673
Route object: none201.7.139.0/24No 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.672 of 673
Route object: none201.7.140.0/24No 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.672 of 673
Route object: none201.7.141.0/24No 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.672 of 673
Route object: none201.7.142.0/24No 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.672 of 673
Route object: none200.169.19.0/24No 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.671 of 673
Route object: none200.169.20.0/24No 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.671 of 673
Route object: none200.169.21.0/24No 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.671 of 673
Route object: none200.169.24.0/24No 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.671 of 673
Route object: none200.169.25.0/24No 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.671 of 673
Route object: none200.169.26.0/24No 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.671 of 673
Route object: none200.169.27.0/24No 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.671 of 673
Route object: none200.169.28.0/24No 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.671 of 673
Route object: none200.169.29.0/24No 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.671 of 673
Route object: none200.169.30.0/24No 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.671 of 673
Route object: none200.169.31.0/24No 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.671 of 673
Route object: none200.169.22.0/24No 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.670 of 673
Route object: RIR187.110.192.0/20Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR200.169.16.0/20Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR201.7.128.0/20Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:f4::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636

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.