bgpreport

Network · data from 2026-11-12

AS271012 AS271012 - GSMNET TELECOMUNICACOES E INSTALACAO ELETRICA LTDA

Registry name: AS271012 - GSMNET TELECOMUNICACOES E INSTALACAO ELETRICA LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271012, 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.
2804:74ec::/32 No ROA None 635 100% 67
177.10.176.0/22 No ROA Other IRR onlyTC 672 100% 67
177.10.176.0/23 No ROA Other IRR onlyTC 669 99% 67
177.10.176.0/24 No ROA Other IRR onlyTC 669 99% 67
177.10.177.0/24 No ROA Other IRR onlyTC 669 99% 67
177.10.178.0/23 No ROA Other IRR onlyTC 669 99% 67
177.10.178.0/24 No ROA Other IRR onlyTC 669 99% 67
177.10.179.0/24 No ROA Other IRR onlyTC 669 99% 67

AS-SET

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

  • ROA: none8
  • Route object: none1
  • Route object: RIR7
ChangePrefix or setDetailFull-table peers
ROA: none2804:74ec::/32No ROA covers it. Add a ROA for AS271012, maxLength 32.635 of 636
Route object: none2804:74ec::/32No route object for it. Add a route object with origin AS271012 in the RIR database for the space.635 of 636
ROA: none177.10.176.0/22No ROA covers it. Add a ROA for AS271012, maxLength 22.672 of 673
Route object: RIR177.10.176.0/22Route object only in TC. Add it in the RIR database for the space.672 of 673
ROA: none177.10.176.0/23No ROA covers it. Add a ROA for AS271012, maxLength 23.669 of 673
Route object: RIR177.10.176.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
ROA: none177.10.176.0/24No ROA covers it. Add a ROA for AS271012, maxLength 24.669 of 673
Route object: RIR177.10.176.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
ROA: none177.10.177.0/24No ROA covers it. Add a ROA for AS271012, maxLength 24.669 of 673
Route object: RIR177.10.177.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
ROA: none177.10.178.0/23No ROA covers it. Add a ROA for AS271012, maxLength 23.669 of 673
Route object: RIR177.10.178.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
ROA: none177.10.178.0/24No ROA covers it. Add a ROA for AS271012, maxLength 24.669 of 673
Route object: RIR177.10.178.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
ROA: none177.10.179.0/24No ROA covers it. Add a ROA for AS271012, maxLength 24.669 of 673
Route object: RIR177.10.179.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673

Route objects not announced

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