bgpreport

Network · data from 2026-11-12

AS61626 Anel de Conectividade - Infovia Paraná

Registry name: AS61626 - UNIVERSIDADE ESTADUAL DE PONTA GROSSA, BR · PeeringDB

34IPv4 routes 85.3% RPKI valid · 8.8% with a route object
2IPv6 routes 100.0% RPKI valid · 50.0% with a route object
5RPKI invalid 5 origin · 0 maxLength
0No ROA 32 with no route object for this origin
6Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS61626, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS61626, 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.

45.184.146.0/23 Invalid: origin None 1 0%low visibility 1
45.186.143.0/24 Invalid: origin Other origin only 1 0%low visibility 1
187.16.201.0/24 Invalid: origin None 1 0%low visibility 1
187.16.208.0/20 Invalid: origin None 1 0%low visibility 1
200.219.144.0/24 Invalid: origin None 1 0%low visibility 1
200.201.13.0/24 Valid Nonecovered by 200.201.8.0/21 671 100% 66
200.201.10.0/24 Valid Nonecovered by 200.201.8.0/21 669 99% 67
200.201.39.0/24 Valid Nonecovered by 200.201.32.0/21 669 99% 67
2804:1f5e:ffff::/48 Valid Nonecovered by 2804:1f5e::/32 631 99% 68
200.201.9.0/24 Valid Nonecovered by 200.201.8.0/21 206 31% 56
200.201.11.0/24 Valid Nonecovered by 200.201.8.0/21 206 31% 56
200.201.12.0/24 Valid Nonecovered by 200.201.8.0/21 206 31% 56
200.201.17.0/24 Valid Nonecovered by 200.201.16.0/20 206 31% 56
200.201.18.0/24 Valid Nonecovered by 200.201.16.0/20 206 31% 56
200.201.19.0/24 Valid Nonecovered by 200.201.16.0/20 206 31% 56
200.201.20.0/24 Valid Nonecovered by 200.201.16.0/20 206 31% 56
200.201.21.0/24 Valid Nonecovered by 200.201.16.0/20 206 31% 56
200.201.22.0/24 Valid Nonecovered by 200.201.16.0/20 206 31% 56
200.201.23.0/24 Valid Nonecovered by 200.201.16.0/20 206 31% 56
200.201.24.0/24 Valid Nonecovered by 200.201.16.0/20 206 31% 56
200.201.25.0/24 Valid Nonecovered by 200.201.16.0/20 206 31% 56
200.201.26.0/24 Valid Nonecovered by 200.201.16.0/20 206 31% 56
200.201.27.0/24 Valid Nonecovered by 200.201.16.0/20 206 31% 56
200.201.28.0/24 Valid Nonecovered by 200.201.16.0/20 206 31% 56
200.201.29.0/24 Valid Nonecovered by 200.201.16.0/20 206 31% 56
200.201.30.0/24 Valid Nonecovered by 200.201.16.0/20 206 31% 56
200.201.31.0/24 Valid Nonecovered by 200.201.16.0/20 206 31% 56
200.201.32.0/24 Valid Nonecovered by 200.201.32.0/21 206 31% 56
200.201.33.0/24 Valid Nonecovered by 200.201.32.0/21 206 31% 56
200.201.34.0/24 Valid Nonecovered by 200.201.32.0/21 206 31% 56
200.201.35.0/24 Valid Nonecovered by 200.201.32.0/21 206 31% 56
177.93.124.0/24 Valid None 1 0%low visibility 1
200.201.16.0/20 Valid Other IRR onlyRADB, TC 669 99% 67
200.201.32.0/21 Valid Other IRR onlyRADB, TC 669 99% 67
200.201.8.0/21 Valid Other IRR onlyRADB, TC 668 99% 67
2804:1f5e::/32 Valid Other IRR onlyRADB, TC 636 100% 70

AS-SET

AS61626'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 41 are in fix.csv.

  • ROA: origin5
  • Route object: none32
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
ROA: origin45.184.146.0/23An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS61626 should announce it, add a ROA for AS61626.1 of 673
Route object: none45.184.146.0/23No route object for it. Add a route object with origin AS61626 in the RIR database for the space.1 of 673
ROA: origin45.186.143.0/24ROAs covering it name AS61600, not AS61626. If AS61626 should announce it, add a ROA for AS61626.1 of 673
Route object: none45.186.143.0/24Route objects for it name AS61600. Add a route object with origin AS61626 in the RIR database for the space.1 of 673
ROA: origin187.16.201.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS61626 should announce it, add a ROA for AS61626.1 of 673
Route object: none187.16.201.0/24No route object for it. Add a route object with origin AS61626 in the RIR database for the space.1 of 673
ROA: origin187.16.208.0/20An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS61626 should announce it, add a ROA for AS61626.1 of 673
Route object: none187.16.208.0/20No route object for it. Add a route object with origin AS61626 in the RIR database for the space.1 of 673
ROA: origin200.219.144.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS61626 should announce it, add a ROA for AS61626.1 of 673
Route object: none200.219.144.0/24No route object for it. Add a route object with origin AS61626 in the RIR database for the space.1 of 673
Route object: none200.201.13.0/24No route object for it. A route object for 200.201.8.0/21 with origin AS61626 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61626 in the RIR database for the space.671 of 673
Route object: none200.201.10.0/24No route object for it. A route object for 200.201.8.0/21 with origin AS61626 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61626 in the RIR database for the space.669 of 673
Route object: none200.201.39.0/24No route object for it. A route object for 200.201.32.0/21 with origin AS61626 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61626 in the RIR database for the space.669 of 673
Route object: none2804:1f5e:ffff::/48No route object for it. A route object for 2804:1f5e::/32 with origin AS61626 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61626 in the RIR database for the space.631 of 636
Route object: none200.201.9.0/24No route object for it. A route object for 200.201.8.0/21 with origin AS61626 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61626 in the RIR database for the space.206 of 673
Route object: none200.201.11.0/24No route object for it. A route object for 200.201.8.0/21 with origin AS61626 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61626 in the RIR database for the space.206 of 673
Route object: none200.201.12.0/24No route object for it. A route object for 200.201.8.0/21 with origin AS61626 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61626 in the RIR database for the space.206 of 673
Route object: none200.201.17.0/24No route object for it. A route object for 200.201.16.0/20 with origin AS61626 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61626 in the RIR database for the space.206 of 673
Route object: none200.201.18.0/24No route object for it. A route object for 200.201.16.0/20 with origin AS61626 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61626 in the RIR database for the space.206 of 673
Route object: none200.201.19.0/24No route object for it. A route object for 200.201.16.0/20 with origin AS61626 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61626 in the RIR database for the space.206 of 673
Route object: none200.201.20.0/24No route object for it. A route object for 200.201.16.0/20 with origin AS61626 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61626 in the RIR database for the space.206 of 673
Route object: none200.201.21.0/24No route object for it. A route object for 200.201.16.0/20 with origin AS61626 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61626 in the RIR database for the space.206 of 673
Route object: none200.201.22.0/24No route object for it. A route object for 200.201.16.0/20 with origin AS61626 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61626 in the RIR database for the space.206 of 673
Route object: none200.201.23.0/24No route object for it. A route object for 200.201.16.0/20 with origin AS61626 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61626 in the RIR database for the space.206 of 673
Route object: none200.201.24.0/24No route object for it. A route object for 200.201.16.0/20 with origin AS61626 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61626 in the RIR database for the space.206 of 673
Route object: none200.201.25.0/24No route object for it. A route object for 200.201.16.0/20 with origin AS61626 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61626 in the RIR database for the space.206 of 673
Route object: none200.201.26.0/24No route object for it. A route object for 200.201.16.0/20 with origin AS61626 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61626 in the RIR database for the space.206 of 673
Route object: none200.201.27.0/24No route object for it. A route object for 200.201.16.0/20 with origin AS61626 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61626 in the RIR database for the space.206 of 673
Route object: none200.201.28.0/24No route object for it. A route object for 200.201.16.0/20 with origin AS61626 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61626 in the RIR database for the space.206 of 673
Route object: none200.201.29.0/24No route object for it. A route object for 200.201.16.0/20 with origin AS61626 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61626 in the RIR database for the space.206 of 673
Route object: none200.201.30.0/24No route object for it. A route object for 200.201.16.0/20 with origin AS61626 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61626 in the RIR database for the space.206 of 673
Route object: none200.201.31.0/24No route object for it. A route object for 200.201.16.0/20 with origin AS61626 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61626 in the RIR database for the space.206 of 673
Route object: none200.201.32.0/24No route object for it. A route object for 200.201.32.0/21 with origin AS61626 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61626 in the RIR database for the space.206 of 673
Route object: none200.201.33.0/24No route object for it. A route object for 200.201.32.0/21 with origin AS61626 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61626 in the RIR database for the space.206 of 673
Route object: none200.201.34.0/24No route object for it. A route object for 200.201.32.0/21 with origin AS61626 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61626 in the RIR database for the space.206 of 673
Route object: none200.201.35.0/24No route object for it. A route object for 200.201.32.0/21 with origin AS61626 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61626 in the RIR database for the space.206 of 673
Route object: none177.93.124.0/24No route object for it. Add a route object with origin AS61626 in the RIR database for the space.1 of 673
Route object: RIR200.201.16.0/20Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR200.201.32.0/21Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR200.201.8.0/21Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:1f5e::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636

Route objects not announced

Every route object with origin AS61626 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.