bgpreport

Network · data from 2026-11-12

AS22110 Ligtel Communications, Inc.

Registry name: LIGTEL-COMMUNICATIONS - Ligtel Communications, Inc., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS22110, 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.
2605:7b00::/32 No ROA Other IRR onlyRADB 635 100% 70
64.184.32.0/20 Valid Other IRR onlyRADB 671 100% 68
64.184.100.0/22 Valid Other IRR onlyRADB 671 100% 68
64.184.116.0/22 Valid Other IRR onlyRADB 671 100% 68
69.160.198.0/23 Valid Other IRR onlyRADB 671 100% 68
69.160.208.0/24 Valid Other IRR onlyRADB 671 100% 68
208.103.24.0/21 Valid Other IRR onlyRADB 671 100% 68
208.103.40.0/22 Valid Other IRR onlyRADB 671 100% 68
208.103.52.0/22 Valid Other IRR onlyRADB 671 100% 68

AS-SET

AS22110'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 11 are in fix.csv.

  • ROA: none1
  • Route object: RIR9
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2605:7b00::/32No ROA covers it. Add a ROA for AS22110, maxLength 32.635 of 636
Route object: RIR2605:7b00::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR64.184.32.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR64.184.100.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR64.184.116.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR69.160.198.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR69.160.208.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR208.103.24.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR208.103.40.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR208.103.52.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

208.6.170.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.