bgpreport

Network · data from 2026-11-12

AS61662 G2 XAXIM TELECOMUNICACOES

Registry name: AS61662 - G2 XAXIM TELECOMUNICACOES LTDA, BR · PeeringDB

7IPv4 routes 0.0% RPKI valid · 100.0% with a route object
1IPv6 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
5Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS61662, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS61662, 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.
131.100.214.0/24 No ROA Other IRR onlyRADB 671 100% 67
131.100.212.0/24 No ROA Other IRR onlyRADB 670 100% 67
2804:1c90::/32 No ROA Other IRR onlyRADB 635 100% 67
131.100.212.0/22 No ROA Other IRR onlyALTDB, RADB 1 0%low visibility 1
131.100.212.0/23 No ROA Other IRR onlyRADB 1 0%low visibility 1
131.100.213.0/24 No ROA Other IRR onlyRADB 1 0%low visibility 1
131.100.214.0/23 No ROA Other IRR onlyRADB 1 0%low visibility 1
131.100.215.0/24 No ROA Other IRR onlyRADB 1 0%low visibility 1

AS-SET

AS61662'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 16 are in fix.csv.

  • ROA: none8
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
ROA: none131.100.214.0/24No ROA covers it. Add a ROA for AS61662, maxLength 24.671 of 673
Route object: RIR131.100.214.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none131.100.212.0/24No ROA covers it. Add a ROA for AS61662, maxLength 24.670 of 673
Route object: RIR131.100.212.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2804:1c90::/32No ROA covers it. Add a ROA for AS61662, maxLength 32.635 of 636
Route object: RIR2804:1c90::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none131.100.212.0/22No ROA covers it. Add a ROA for AS61662, maxLength 22.1 of 673
Route object: RIR131.100.212.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.1 of 673
ROA: none131.100.212.0/23No ROA covers it. Add a ROA for AS61662, maxLength 23.1 of 673
Route object: RIR131.100.212.0/23Route object only in RADB. Add it in the RIR database for the space.1 of 673
ROA: none131.100.213.0/24No ROA covers it. Add a ROA for AS61662, maxLength 24.1 of 673
Route object: RIR131.100.213.0/24Route object only in RADB. Add it in the RIR database for the space.1 of 673
ROA: none131.100.214.0/23No ROA covers it. Add a ROA for AS61662, maxLength 23.1 of 673
Route object: RIR131.100.214.0/23Route object only in RADB. Add it in the RIR database for the space.1 of 673
ROA: none131.100.215.0/24No ROA covers it. Add a ROA for AS61662, maxLength 24.1 of 673
Route object: RIR131.100.215.0/24Route object only in RADB. Add it in the RIR database for the space.1 of 673

Route objects not announced

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