bgpreport

Network · data from 2026-11-12

AS52788 Meganet Telecomunicaçoes e Internet LTDA

Registry name: AS52788 - Meganet Telecomunicacoes e Internet LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS52788, 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.
177.38.68.0/24 Valid Nonecovered by 177.38.68.0/23 664 99% 67
177.38.71.0/24 Valid Nonecovered by 177.38.70.0/23 664 99% 67
177.38.70.0/24 Valid Nonecovered by 177.38.70.0/23 135 20% 45
177.38.68.0/22 Valid Other IRR onlyRADB, TC 668 99% 67
2804:b84::/32 Valid Other IRR onlyRADB, TC 636 100% 70
2804:b84::/33 Valid Other IRR onlyRADB 636 100% 67
2804:b84:8000::/33 Valid Other IRR onlyRADB 636 100% 67
177.38.69.0/24 Valid Other IRR onlyRADB 135 20% 45
177.38.68.0/23 Valid Other IRR onlyRADB 0 0%low visibility 1
177.38.70.0/23 Valid Other IRR onlyRADB 0 0%low visibility 1

AS-SET

AS52788'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 10 are in fix.csv.

  • Route object: none3
  • Route object: RIR7
ChangePrefix or setDetailFull-table peers
Route object: none177.38.68.0/24No route object for it. A route object for 177.38.68.0/23 with origin AS52788 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52788 in the RIR database for the space.664 of 673
Route object: none177.38.71.0/24No route object for it. A route object for 177.38.70.0/23 with origin AS52788 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52788 in the RIR database for the space.664 of 673
Route object: none177.38.70.0/24No route object for it. A route object for 177.38.70.0/23 with origin AS52788 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52788 in the RIR database for the space.135 of 673
Route object: RIR177.38.68.0/22Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:b84::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:b84::/33Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:b84:8000::/33Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR177.38.69.0/24Route object only in RADB. Add it in the RIR database for the space.135 of 673
Route object: RIR177.38.68.0/23Route object only in RADB. Add it in the RIR database for the space.0 of 673
Route object: RIR177.38.70.0/23Route object only in RADB. Add it in the RIR database for the space.0 of 673

Route objects not announced

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