bgpreport

Network · data from 2026-11-12

AS271038 AS271038 - Mega Turbo Internet Banda Larga Telecom LTDA

Registry name: AS271038 - Mega Turbo Internet Banda Larga Telecom LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271038, 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.129.230.0/23 No ROA Nonecovered by 177.129.228.0/22 665 99% 67
2804:7550::/34 No ROA Nonecovered by 2804:7550::/32 634 100% 67
2804:7550:4000::/34 No ROA Nonecovered by 2804:7550::/32 634 100% 67
2804:7550:8000::/34 No ROA Nonecovered by 2804:7550::/32 634 100% 67
177.129.229.0/24 No ROA Other IRR onlyRADB 670 100% 67
177.129.228.0/24 No ROA Other IRR onlyRADB 664 99% 67
2804:7550:c000::/34 No ROA Other IRR onlyRADB 632 99% 67

AS-SET

AS271038 isn't in PeeringDB, where networks name their 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 18 are in fix.csv.

  • ROA: none7
  • Route object: none4
  • Route object: RIR3
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none177.129.230.0/23No ROA covers it. Add a ROA for AS271038, maxLength 23.665 of 673
Route object: none177.129.230.0/23No route object for it. A route object for 177.129.228.0/22 with origin AS271038 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271038 in the RIR database for the space.665 of 673
ROA: none2804:7550::/34No ROA covers it. Add a ROA for AS271038, maxLength 34.634 of 636
Route object: none2804:7550::/34No route object for it. A route object for 2804:7550::/32 with origin AS271038 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271038 in the RIR database for the space.634 of 636
ROA: none2804:7550:4000::/34No ROA covers it. Add a ROA for AS271038, maxLength 34.634 of 636
Route object: none2804:7550:4000::/34No route object for it. A route object for 2804:7550::/32 with origin AS271038 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271038 in the RIR database for the space.634 of 636
ROA: none2804:7550:8000::/34No ROA covers it. Add a ROA for AS271038, maxLength 34.634 of 636
Route object: none2804:7550:8000::/34No route object for it. A route object for 2804:7550::/32 with origin AS271038 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271038 in the RIR database for the space.634 of 636
ROA: none177.129.229.0/24No ROA covers it. Add a ROA for AS271038, maxLength 24.670 of 673
Route object: RIR177.129.229.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none177.129.228.0/24No ROA covers it. Add a ROA for AS271038, maxLength 24.664 of 673
Route object: RIR177.129.228.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
ROA: none2804:7550:c000::/34No ROA covers it. Add a ROA for AS271038, maxLength 34.632 of 636
Route object: RIR2804:7550:c000::/34Route object only in RADB. Add it in the RIR database for the space.632 of 636

Route objects not announced

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

177.129.228.0/22RADBNo ROA
177.129.230.0/24RADBNo ROA
177.129.231.0/24RADBNo ROA
2804:7550::/32RADBNo 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.