bgpreport

Network · data from 2026-11-12

AS61632 Zoopnet - Wellington Serrilho Soler ME

Registry name: AS61632 - Zoopnet - Wellington Serrilho Soler ME, BR · PeeringDB

21IPv4 routes 100.0% RPKI valid · 14.3% with a route object
7IPv6 routes 100.0% RPKI valid · 14.3% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 24 with no route object for this origin
16Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS61632, seen from no peer

Announced routes

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

138.121.236.0/23 Valid Nonecovered by 138.121.236.0/22 97 14% 39
168.232.186.0/23 Valid Nonecovered by 168.232.184.0/22 97 14% 39
131.100.124.0/23 Valid Nonecovered by 131.100.124.0/22 96 14% 39
131.100.126.0/23 Valid Nonecovered by 131.100.124.0/22 96 14% 39
138.121.238.0/23 Valid Nonecovered by 138.121.236.0/22 96 14% 39
168.232.184.0/23 Valid Nonecovered by 168.232.184.0/22 96 14% 39
2804:1bfc::/33 Valid Nonecovered by 2804:1bfc::/32 88 14% 38
2804:1bfc:8000::/33 Valid Nonecovered by 2804:1bfc::/32 88 14% 38
131.100.124.0/24 Valid Nonecovered by 131.100.124.0/22 2 0%low visibility 2
131.100.125.0/24 Valid Nonecovered by 131.100.124.0/22 2 0%low visibility 2
131.100.126.0/24 Valid Nonecovered by 131.100.124.0/22 2 0%low visibility 2
131.100.127.0/24 Valid Nonecovered by 131.100.124.0/22 2 0%low visibility 2
138.121.236.0/24 Valid Nonecovered by 138.121.236.0/22 2 0%low visibility 2
138.121.237.0/24 Valid Nonecovered by 138.121.236.0/22 2 0%low visibility 2
138.121.238.0/24 Valid Nonecovered by 138.121.236.0/22 2 0%low visibility 2
138.121.239.0/24 Valid Nonecovered by 138.121.236.0/22 2 0%low visibility 2
168.232.184.0/24 Valid Nonecovered by 168.232.184.0/22 2 0%low visibility 2
168.232.185.0/24 Valid Nonecovered by 168.232.184.0/22 2 0%low visibility 2
168.232.186.0/24 Valid Nonecovered by 168.232.184.0/22 2 0%low visibility 2
168.232.187.0/24 Valid Nonecovered by 168.232.184.0/22 2 0%low visibility 2
2804:1bfc::/34 Valid Nonecovered by 2804:1bfc::/32 2 0%low visibility 2
2804:1bfc:4000::/34 Valid Nonecovered by 2804:1bfc::/32 2 0%low visibility 2
2804:1bfc:8000::/34 Valid Nonecovered by 2804:1bfc::/32 2 0%low visibility 2
2804:1bfc:c000::/34 Valid Nonecovered by 2804:1bfc::/32 2 0%low visibility 2
138.121.236.0/22 Valid Other IRR onlyTC 670 100% 67
168.232.184.0/22 Valid Other IRR onlyTC 670 100% 67
131.100.124.0/22 Valid Other IRR onlyTC 669 99% 67
2804:1bfc::/32 Valid Other IRR onlyRADB, TC 633 100% 69

AS-SET

AS61632'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 28 are in fix.csv.

  • Route object: none24
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
Route object: none138.121.236.0/23No route object for it. A route object for 138.121.236.0/22 with origin AS61632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61632 in the RIR database for the space.97 of 673
Route object: none168.232.186.0/23No route object for it. A route object for 168.232.184.0/22 with origin AS61632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61632 in the RIR database for the space.97 of 673
Route object: none131.100.124.0/23No route object for it. A route object for 131.100.124.0/22 with origin AS61632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61632 in the RIR database for the space.96 of 673
Route object: none131.100.126.0/23No route object for it. A route object for 131.100.124.0/22 with origin AS61632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61632 in the RIR database for the space.96 of 673
Route object: none138.121.238.0/23No route object for it. A route object for 138.121.236.0/22 with origin AS61632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61632 in the RIR database for the space.96 of 673
Route object: none168.232.184.0/23No route object for it. A route object for 168.232.184.0/22 with origin AS61632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61632 in the RIR database for the space.96 of 673
Route object: none2804:1bfc::/33No route object for it. A route object for 2804:1bfc::/32 with origin AS61632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61632 in the RIR database for the space.88 of 636
Route object: none2804:1bfc:8000::/33No route object for it. A route object for 2804:1bfc::/32 with origin AS61632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61632 in the RIR database for the space.88 of 636
Route object: none131.100.124.0/24No route object for it. A route object for 131.100.124.0/22 with origin AS61632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61632 in the RIR database for the space.2 of 673
Route object: none131.100.125.0/24No route object for it. A route object for 131.100.124.0/22 with origin AS61632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61632 in the RIR database for the space.2 of 673
Route object: none131.100.126.0/24No route object for it. A route object for 131.100.124.0/22 with origin AS61632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61632 in the RIR database for the space.2 of 673
Route object: none131.100.127.0/24No route object for it. A route object for 131.100.124.0/22 with origin AS61632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61632 in the RIR database for the space.2 of 673
Route object: none138.121.236.0/24No route object for it. A route object for 138.121.236.0/22 with origin AS61632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61632 in the RIR database for the space.2 of 673
Route object: none138.121.237.0/24No route object for it. A route object for 138.121.236.0/22 with origin AS61632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61632 in the RIR database for the space.2 of 673
Route object: none138.121.238.0/24No route object for it. A route object for 138.121.236.0/22 with origin AS61632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61632 in the RIR database for the space.2 of 673
Route object: none138.121.239.0/24No route object for it. A route object for 138.121.236.0/22 with origin AS61632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61632 in the RIR database for the space.2 of 673
Route object: none168.232.184.0/24No route object for it. A route object for 168.232.184.0/22 with origin AS61632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61632 in the RIR database for the space.2 of 673
Route object: none168.232.185.0/24No route object for it. A route object for 168.232.184.0/22 with origin AS61632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61632 in the RIR database for the space.2 of 673
Route object: none168.232.186.0/24No route object for it. A route object for 168.232.184.0/22 with origin AS61632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61632 in the RIR database for the space.2 of 673
Route object: none168.232.187.0/24No route object for it. A route object for 168.232.184.0/22 with origin AS61632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61632 in the RIR database for the space.2 of 673
Route object: none2804:1bfc::/34No route object for it. A route object for 2804:1bfc::/32 with origin AS61632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61632 in the RIR database for the space.2 of 636
Route object: none2804:1bfc:4000::/34No route object for it. A route object for 2804:1bfc::/32 with origin AS61632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61632 in the RIR database for the space.2 of 636
Route object: none2804:1bfc:8000::/34No route object for it. A route object for 2804:1bfc::/32 with origin AS61632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61632 in the RIR database for the space.2 of 636
Route object: none2804:1bfc:c000::/34No route object for it. A route object for 2804:1bfc::/32 with origin AS61632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61632 in the RIR database for the space.2 of 636
Route object: RIR138.121.236.0/22Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR168.232.184.0/22Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR131.100.124.0/22Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:1bfc::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636

Route objects not announced

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