bgpreport

Network · data from 2026-11-12

AS53225 IPGLOBE

Registry name: AS53225 - IPGLOBE INTERNET LTDA, BR · PeeringDB

31IPv4 routes 96.8% RPKI valid · 45.2% with a route object
1IPv6 routes 100.0% RPKI valid · 0.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 18 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
9Route objects not announced registered with origin AS53225, seen from no peer

Announced routes

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

186.251.129.0/24 No ROA Other IRR onlyRADB 669 99% 66
177.137.25.0/24 Valid Nonecovered by 177.137.24.0/21 669 99% 67
177.137.28.0/23 Valid Nonecovered by 177.137.24.0/21 669 99% 67
177.137.30.0/24 Valid Nonecovered by 177.137.24.0/21 669 99% 67
186.251.128.0/24 Valid Nonecovered by 186.251.128.0/21 669 99% 67
186.251.130.0/24 Valid Nonecovered by 186.251.128.0/21 669 99% 67
186.251.131.0/24 Valid Nonecovered by 186.251.128.0/21 669 99% 67
186.251.132.0/24 Valid Nonecovered by 186.251.128.0/21 669 99% 67
186.251.133.0/24 Valid Nonecovered by 186.251.128.0/21 669 99% 67
186.251.134.0/24 Valid Nonecovered by 186.251.128.0/21 669 99% 67
186.251.135.0/24 Valid Nonecovered by 186.251.128.0/21 669 99% 67
186.251.136.0/24 Valid Nonecovered by 186.251.136.0/22 669 99% 67
186.251.137.0/24 Valid Nonecovered by 186.251.136.0/22 669 99% 67
186.251.138.0/24 Valid Nonecovered by 186.251.136.0/22 669 99% 67
186.251.139.0/24 Valid Nonecovered by 186.251.136.0/22 669 99% 67
186.251.140.0/24 Valid Nonecovered by 186.251.140.0/22 669 99% 67
186.251.141.0/24 Valid Nonecovered by 186.251.140.0/22 669 99% 67
186.251.142.0/24 Valid Nonecovered by 186.251.140.0/22 669 99% 67
2804:644::/48 Valid Nonecovered by 2804:644::/32 635 100% 67
177.137.18.0/24 Valid Other IRR onlyTC 672 100% 66
177.137.21.0/24 Valid Other IRR onlyRADB, TC 672 100% 67
177.137.27.0/24 Valid Other IRR onlyRADB 672 100% 66
177.137.19.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
177.137.20.0/23 Valid Other IRR onlyRADB, TC 671 100% 67
177.137.20.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
177.137.22.0/24 Valid Other IRR onlyTC 670 100% 67
177.137.26.0/24 Valid Other IRR onlyRADB 670 100% 66
186.251.143.0/24 Valid Other IRR onlyRADB 670 100% 66
177.137.23.0/24 Valid Other IRR onlyTC 669 99% 67
177.137.16.0/24 Valid Other IRR onlyTC 668 99% 67
177.137.24.0/24 Valid Other IRR onlyRADB 668 99% 66
177.137.17.0/24 Valid Other IRR onlyRADB, TC 667 99% 67

AS-SET

AS53225'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 42 are in fix.csv.

  • ROA: none1
  • Route object: none18
  • Route object: RIR14
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none186.251.129.0/24No ROA covers it. Add a ROA for AS53225, maxLength 24.669 of 673
Route object: RIR186.251.129.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: none177.137.25.0/24No route object for it. A route object for 177.137.24.0/21 with origin AS53225 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53225 in the RIR database for the space.669 of 673
Route object: none177.137.28.0/23No route object for it. A route object for 177.137.24.0/21 with origin AS53225 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53225 in the RIR database for the space.669 of 673
Route object: none177.137.30.0/24No route object for it. A route object for 177.137.24.0/21 with origin AS53225 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53225 in the RIR database for the space.669 of 673
Route object: none186.251.128.0/24No route object for it. A route object for 186.251.128.0/21 with origin AS53225 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53225 in the RIR database for the space.669 of 673
Route object: none186.251.130.0/24No route object for it. A route object for 186.251.128.0/21 with origin AS53225 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53225 in the RIR database for the space.669 of 673
Route object: none186.251.131.0/24No route object for it. A route object for 186.251.128.0/21 with origin AS53225 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53225 in the RIR database for the space.669 of 673
Route object: none186.251.132.0/24No route object for it. A route object for 186.251.128.0/21 with origin AS53225 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53225 in the RIR database for the space.669 of 673
Route object: none186.251.133.0/24No route object for it. A route object for 186.251.128.0/21 with origin AS53225 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53225 in the RIR database for the space.669 of 673
Route object: none186.251.134.0/24No route object for it. A route object for 186.251.128.0/21 with origin AS53225 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53225 in the RIR database for the space.669 of 673
Route object: none186.251.135.0/24No route object for it. A route object for 186.251.128.0/21 with origin AS53225 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53225 in the RIR database for the space.669 of 673
Route object: none186.251.136.0/24No route object for it. A route object for 186.251.136.0/22 with origin AS53225 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53225 in the RIR database for the space.669 of 673
Route object: none186.251.137.0/24No route object for it. A route object for 186.251.136.0/22 with origin AS53225 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53225 in the RIR database for the space.669 of 673
Route object: none186.251.138.0/24No route object for it. A route object for 186.251.136.0/22 with origin AS53225 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53225 in the RIR database for the space.669 of 673
Route object: none186.251.139.0/24No route object for it. A route object for 186.251.136.0/22 with origin AS53225 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53225 in the RIR database for the space.669 of 673
Route object: none186.251.140.0/24No route object for it. A route object for 186.251.140.0/22 with origin AS53225 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53225 in the RIR database for the space.669 of 673
Route object: none186.251.141.0/24No route object for it. A route object for 186.251.140.0/22 with origin AS53225 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53225 in the RIR database for the space.669 of 673
Route object: none186.251.142.0/24No route object for it. A route object for 186.251.140.0/22 with origin AS53225 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53225 in the RIR database for the space.669 of 673
Route object: none2804:644::/48No route object for it. A route object for 2804:644::/32 with origin AS53225 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53225 in the RIR database for the space.635 of 636
Route object: RIR177.137.18.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.137.21.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.137.27.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.137.19.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.137.20.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.137.20.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.137.22.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR177.137.26.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR186.251.143.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR177.137.23.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR177.137.16.0/24Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR177.137.24.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR177.137.17.0/24Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673

Route objects not announced

Route objects with origin AS53225 whose prefix no peer sees AS53225 announce. Many are kept on purpose (backup routes, space announced only in some places).

177.137.16.0/20RADBNo ROA
177.137.16.0/21TCNo ROA
177.137.20.0/22RADBNo ROA
177.137.24.0/21ALTDB, RADBNo ROA
186.251.128.0/20RADB, RIPE-NONAUTHNo ROA
186.251.128.0/21TCNo ROA
186.251.136.0/22TCNo ROA
186.251.140.0/22TCNo ROA
2804:644::/32RADB, TCNo ROA

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.