bgpreport

Network · data from 2026-11-12

AS271131 Giga Sul Telecom

Registry name: AS271131 - Giga Sul Telecom, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271131, 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.
179.42.72.0/22 No ROA Other IRR onlyTC 667 99% 67
179.42.72.0/24 No ROA Other IRR onlyRADB 667 99% 66
179.42.74.0/24 No ROA Other IRR onlyRADB 666 99% 67
179.42.75.0/24 No ROA Other IRR onlyRADB 666 99% 67
2804:76bc::/32 No ROA Other IRR onlyRADB, TC 631 99% 67
2804:76bc::/33 No ROA Other IRR onlyRADB 631 99% 67
2804:76bc:8000::/33 No ROA Other IRR onlyRADB 631 99% 67
179.42.73.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2

AS-SET

AS271131'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 18 are in fix.csv.

  • ROA: none8
  • Route object: RIR8
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none179.42.72.0/22No ROA covers it. Add a ROA for AS271131, maxLength 22.667 of 673
Route object: RIR179.42.72.0/22Route object only in TC. Add it in the RIR database for the space.667 of 673
ROA: none179.42.72.0/24No ROA covers it. Add a ROA for AS271131, maxLength 24.667 of 673
Route object: RIR179.42.72.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none179.42.74.0/24No ROA covers it. Add a ROA for AS271131, maxLength 24.666 of 673
Route object: RIR179.42.74.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none179.42.75.0/24No ROA covers it. Add a ROA for AS271131, maxLength 24.666 of 673
Route object: RIR179.42.75.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none2804:76bc::/32No ROA covers it. Add a ROA for AS271131, maxLength 32.631 of 636
Route object: RIR2804:76bc::/32Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
ROA: none2804:76bc::/33No ROA covers it. Add a ROA for AS271131, maxLength 33.631 of 636
Route object: RIR2804:76bc::/33Route object only in RADB. Add it in the RIR database for the space.631 of 636
ROA: none2804:76bc:8000::/33No ROA covers it. Add a ROA for AS271131, maxLength 33.631 of 636
Route object: RIR2804:76bc:8000::/33Route object only in RADB. Add it in the RIR database for the space.631 of 636
ROA: none179.42.73.0/24No ROA covers it. Add a ROA for AS271131, maxLength 24.2 of 673
Route object: RIR179.42.73.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

179.42.72.0/23RADBNo ROA
179.42.74.0/23RADBNo 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.