bgpreport

Network · data from 2026-11-12

AS43103 ONE TELECOM ltd

Registry name: ONETELECOM-AS ONE TELECOM ltd, UA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS43103, 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.
80.90.238.0/23 No ROA Nonecovered by 80.90.236.0/22 673 100% 67
80.90.224.0/20 No ROA RIR databaseRIPE 671 100% 68
80.90.224.0/22 No ROA RIR databaseRIPE 671 100% 68
80.90.224.0/24 No ROA RIR databaseRIPE 671 100% 68
80.90.228.0/22 No ROA RIR databaseRIPE 671 100% 68
80.90.230.0/24 No ROA RIR databaseRIPE 671 100% 68
80.90.232.0/22 No ROA RIR databaseRIPE 671 100% 68
80.90.236.0/22 No ROA RIR databaseRIPE 671 100% 68
91.194.72.0/24 No ROA RIR databaseRIPE 671 100% 68
91.196.92.0/22 No ROA RIR databaseRIPE 671 100% 68
185.4.40.0/22 No ROA RIR databaseRIPE 671 100% 68
185.4.40.0/23 No ROA RIR databaseRIPE 671 100% 68
80.90.237.0/24 No ROA RIR databaseRIPE 670 100% 68
185.4.43.0/24 No ROA RIR databaseRIPE 670 100% 68

AS-SET

AS43103'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 29 are in fix.csv.

  • ROA: none14
  • Route object: none1
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
ROA: none80.90.238.0/23No ROA covers it. Add a ROA for AS43103, maxLength 23.673 of 673
Route object: none80.90.238.0/23No route object for it. A route object for 80.90.236.0/22 with origin AS43103 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43103 in the RIR database for the space.673 of 673
ROA: none80.90.224.0/20No ROA covers it. Add a ROA for AS43103, maxLength 20.671 of 673
ROA: none80.90.224.0/22No ROA covers it. Add a ROA for AS43103, maxLength 22.671 of 673
ROA: none80.90.224.0/24No ROA covers it. Add a ROA for AS43103, maxLength 24.671 of 673
ROA: none80.90.228.0/22No ROA covers it. Add a ROA for AS43103, maxLength 22.671 of 673
ROA: none80.90.230.0/24No ROA covers it. Add a ROA for AS43103, maxLength 24.671 of 673
ROA: none80.90.232.0/22No ROA covers it. Add a ROA for AS43103, maxLength 22.671 of 673
ROA: none80.90.236.0/22No ROA covers it. Add a ROA for AS43103, maxLength 22.671 of 673
ROA: none91.194.72.0/24No ROA covers it. Add a ROA for AS43103, maxLength 24.671 of 673
ROA: none91.196.92.0/22No ROA covers it. Add a ROA for AS43103, maxLength 22.671 of 673
ROA: none185.4.40.0/22No ROA covers it. Add a ROA for AS43103, maxLength 22.671 of 673
ROA: none185.4.40.0/23No ROA covers it. Add a ROA for AS43103, maxLength 23.671 of 673
ROA: none80.90.237.0/24No ROA covers it. Add a ROA for AS43103, maxLength 24.670 of 673
ROA: none185.4.43.0/24No ROA covers it. Add a ROA for AS43103, maxLength 24.670 of 673

Route objects not announced

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

80.90.225.0/24RIPENo ROA
80.90.227.0/24RIPENo ROA
80.90.228.0/24RIPENo ROA
80.90.229.0/24RIPENo ROA
80.90.231.0/24RIPENo ROA
80.90.236.0/24RIPENo ROA
80.90.238.0/24RIPENo ROA
80.90.239.0/24RIPENo ROA
91.194.73.0/24RIPENo ROA
91.196.92.0/24RIPENo ROA
91.196.93.0/24RIPENo ROA
91.196.94.0/24RIPENo ROA
91.196.95.0/24RIPENo ROA
185.4.42.0/24RIPENo 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.