bgpreport

Network · data from 2026-11-12

AS61671 AS61671 - LIGMAIS TELECOMUNICACAO EIRELI

Registry name: AS61671 - LIGMAIS TELECOMUNICACAO EIRELI, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS61671, 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.108.52.0/24 No ROA Nonecovered by 131.108.52.0/23 6 1%low visibility 5
131.108.53.0/24 No ROA Nonecovered by 131.108.52.0/23 6 1%low visibility 5
131.108.54.0/24 No ROA Nonecovered by 131.108.54.0/23 6 1%low visibility 5
131.108.55.0/24 No ROA Nonecovered by 131.108.54.0/23 6 1%low visibility 5
131.108.52.0/22 No ROA Other IRR onlyRADB 672 100% 67
131.108.54.0/23 No ROA Other IRR onlyRADB 671 100% 67
131.108.52.0/23 No ROA Other IRR onlyRADB 670 100% 67
2804:1cb8::/32 No ROA Other IRR onlyRADB 634 100% 69

AS-SET

AS61671 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: none4
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
ROA: none131.108.52.0/24No ROA covers it. Add a ROA for AS61671, maxLength 24.6 of 673
Route object: none131.108.52.0/24No route object for it. A route object for 131.108.52.0/23 with origin AS61671 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61671 in the RIR database for the space.6 of 673
ROA: none131.108.53.0/24No ROA covers it. Add a ROA for AS61671, maxLength 24.6 of 673
Route object: none131.108.53.0/24No route object for it. A route object for 131.108.52.0/23 with origin AS61671 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61671 in the RIR database for the space.6 of 673
ROA: none131.108.54.0/24No ROA covers it. Add a ROA for AS61671, maxLength 24.6 of 673
Route object: none131.108.54.0/24No route object for it. A route object for 131.108.54.0/23 with origin AS61671 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61671 in the RIR database for the space.6 of 673
ROA: none131.108.55.0/24No ROA covers it. Add a ROA for AS61671, maxLength 24.6 of 673
Route object: none131.108.55.0/24No route object for it. A route object for 131.108.54.0/23 with origin AS61671 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61671 in the RIR database for the space.6 of 673
ROA: none131.108.52.0/22No ROA covers it. Add a ROA for AS61671, maxLength 22.672 of 673
Route object: RIR131.108.52.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none131.108.54.0/23No ROA covers it. Add a ROA for AS61671, maxLength 23.671 of 673
Route object: RIR131.108.54.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none131.108.52.0/23No ROA covers it. Add a ROA for AS61671, maxLength 23.670 of 673
Route object: RIR131.108.52.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2804:1cb8::/32No ROA covers it. Add a ROA for AS61671, maxLength 32.634 of 636
Route object: RIR2804:1cb8::/32Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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