bgpreport

Network · data from 2026-11-12

AS42020 LibanTelecom

Registry name: LibanTelecom OGERO, LB · PeeringDB

12IPv4 routes 100.0% RPKI valid · 58.3% with a route object
4IPv6 routes 50.0% RPKI valid · 75.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
2No ROA 6 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS42020, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS42020, 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.

2a00:6920:f::/48 No ROA Nonecovered by 2a00:6920::/40 636 100% 67
2a00:6920::/40 No ROA RIR databaseRIPE 636 100% 67
77.42.248.0/24 Valid Nonecovered by 77.42.248.0/21 672 100% 67
77.42.249.0/24 Valid Nonecovered by 77.42.248.0/21 672 100% 67
77.42.253.0/24 Valid Nonecovered by 77.42.248.0/21 672 100% 67
77.42.254.0/24 Valid Nonecovered by 77.42.248.0/21 672 100% 67
77.42.255.0/24 Valid Nonecovered by 77.42.248.0/21 672 100% 67
185.173.60.0/24 Valid RIR databaseRIPE 673 100% 67
185.173.61.0/24 Valid RIR databaseRIPE 673 100% 67
185.173.62.0/24 Valid RIR databaseRIPE 673 100% 67
185.173.63.0/24 Valid RIR databaseRIPE 673 100% 67
77.42.250.0/24 Valid RIR databaseRIPE 672 100% 67
77.42.251.0/24 Valid RIR databaseRIPE 672 100% 67
77.42.252.0/24 Valid RIR databaseRIPE 672 100% 67
2a00:6920::/48 Valid RIR databaseRIPE 636 100% 67
2a00:6920:1000::/40 Valid RIR databaseRIPE 636 100% 67

AS-SET

AS42020'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: none2
  • Route object: none6
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none2a00:6920:f::/48No ROA covers it. Add a ROA for AS42020, maxLength 48.636 of 636
Route object: none2a00:6920:f::/48No route object for it. A route object for 2a00:6920::/40 with origin AS42020 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42020 in the RIR database for the space.636 of 636
ROA: none2a00:6920::/40No ROA covers it. Add a ROA for AS42020, maxLength 40.636 of 636
Route object: none77.42.248.0/24No route object for it. A route object for 77.42.248.0/21 with origin AS42020 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42020 in the RIR database for the space.672 of 673
Route object: none77.42.249.0/24No route object for it. A route object for 77.42.248.0/21 with origin AS42020 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42020 in the RIR database for the space.672 of 673
Route object: none77.42.253.0/24No route object for it. A route object for 77.42.248.0/21 with origin AS42020 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42020 in the RIR database for the space.672 of 673
Route object: none77.42.254.0/24No route object for it. A route object for 77.42.248.0/21 with origin AS42020 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42020 in the RIR database for the space.672 of 673
Route object: none77.42.255.0/24No route object for it. A route object for 77.42.248.0/21 with origin AS42020 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42020 in the RIR database for the space.672 of 673

Route objects not announced

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

77.42.192.0/20RIPEInvalid: origin
77.42.248.0/21RIPENo ROA
2a00:6920::/56RIPEInvalid: maxLength

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.