bgpreport

Network · data from 2026-11-12

AS61806 AS61806 - LIG TECH TELECOMUNICACOES EIRELI

Registry name: AS61806 - LIG TECH TELECOMUNICACOES EIRELI, BR · not in PeeringDB

1IPv4 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
4No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS61806, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS61806, 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.
201.150.156.0/22 No ROA Other IRR onlyALTDB, RADB 670 100% 67
2804:199c::/32 No ROA Other IRR onlyALTDB, RADB 635 100% 67
2804:199c::/33 No ROA Other IRR onlyALTDB 635 100% 67
2804:199c:8000::/33 No ROA Other IRR onlyALTDB 635 100% 67

AS-SET

AS61806 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 14 are in fix.csv.

  • ROA: none4
  • Route object: RIR4
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none201.150.156.0/22No ROA covers it. Add a ROA for AS61806, maxLength 22.670 of 673
Route object: RIR201.150.156.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
ROA: none2804:199c::/32No ROA covers it. Add a ROA for AS61806, maxLength 32.635 of 636
Route object: RIR2804:199c::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:199c::/33No ROA covers it. Add a ROA for AS61806, maxLength 33.635 of 636
Route object: RIR2804:199c::/33Route object only in ALTDB. Add it in the RIR database for the space.635 of 636
ROA: none2804:199c:8000::/33No ROA covers it. Add a ROA for AS61806, maxLength 33.635 of 636
Route object: RIR2804:199c:8000::/33Route object only in ALTDB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

201.150.156.0/23RADBNo ROA
201.150.156.0/24ALTDBNo ROA
201.150.157.0/24ALTDBNo ROA
201.150.158.0/23RADBNo ROA
201.150.158.0/24ALTDBNo ROA
201.150.159.0/24ALTDBNo 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.