Network · data from 2026-11-12

AS202651 NBTEL-FTTH Al-Tair Al-Watani Company for General Trading, Agricultural Investments, Production and Distribution, Technical Services, Internet Services, Public Services, Information Technology and Software Ltd

Registry name: NBTEL-FTTH Al-Tair Al-Watani Company for General Trading, Agricultural Investments, Production and Distribution, Technical Services, Internet Services, Public Services, Information Technology and Software Ltd, IQ · not in PeeringDB

23IPv4 routes 73.9% RPKI valid · 73.9% with a route object

0IPv6 routes

6RPKI invalid 6 origin · 0 maxLength

0No ROA 6 with no route object for this origin

6Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS202651, seen from no peer

Announced routes

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


194.39.110.0/24	Invalid: origin	Other origin only	3 0%low visibility	3
151.246.137.0/24	Invalid: origin	Other origin only	2 0%low visibility	2
151.246.139.0/24	Invalid: origin	Other origin only	2 0%low visibility	2
151.246.140.0/24	Invalid: origin	None	2 0%low visibility	2
151.246.141.0/24	Invalid: origin	None	2 0%low visibility	2
151.246.143.0/24	Invalid: origin	Other origin only	2 0%low visibility	2
91.192.6.0/24	Valid	RIR databaseRIPE	670 100%	67
92.119.63.0/24	Valid	RIR databaseRIPE	670 100%	67
176.105.236.0/24	Valid	RIR databaseRIPE	670 100%	67
193.219.112.0/24	Valid	RIR databaseRADB, RIPE	670 100%	67
195.7.8.0/24	Valid	RIR databaseRIPE	670 100%	67
5.253.68.0/24	Valid	RIR databaseRIPE	669 99%	67
5.253.69.0/24	Valid	RIR databaseRIPE	669 99%	67
5.253.70.0/24	Valid	RIR databaseRIPE	669 99%	67
5.253.71.0/24	Valid	RIR databaseRIPE	669 99%	67
37.205.116.0/24	Valid	RIR databaseRIPE	669 99%	67
37.205.117.0/24	Valid	RIR databaseRIPE	669 99%	67
37.205.118.0/24	Valid	RIR databaseRIPE	669 99%	67
37.205.119.0/24	Valid	RIR databaseRIPE	669 99%	67
45.143.29.0/24	Valid	RIR databaseRIPE	669 99%	67
45.143.30.0/24	Valid	RIR databaseRIPE	669 99%	67
45.146.14.0/24	Valid	RIR databaseRIPE	669 99%	67
45.146.15.0/24	Valid	RIR databaseRIPE	669 99%	67

194.39.110.0/24

Invalid: origin

Other origin only

3 0%low visibility

151.246.137.0/24

Invalid: origin

Other origin only

2 0%low visibility

151.246.139.0/24

Invalid: origin

Other origin only

2 0%low visibility

151.246.140.0/24

Invalid: origin

None

2 0%low visibility

151.246.141.0/24

Invalid: origin

None

2 0%low visibility

151.246.143.0/24

Invalid: origin

Other origin only

2 0%low visibility

91.192.6.0/24

Valid

RIR databaseRIPE

670 100%

92.119.63.0/24

Valid

RIR databaseRIPE

670 100%

176.105.236.0/24

Valid

RIR databaseRIPE

670 100%

193.219.112.0/24

Valid

RIR databaseRADB, RIPE

670 100%

195.7.8.0/24

Valid

RIR databaseRIPE

670 100%

5.253.68.0/24

Valid

RIR databaseRIPE

669 99%

5.253.69.0/24

Valid

RIR databaseRIPE

669 99%

5.253.70.0/24

Valid

RIR databaseRIPE

669 99%

5.253.71.0/24

Valid

RIR databaseRIPE

669 99%

37.205.116.0/24

Valid

RIR databaseRIPE

669 99%

37.205.117.0/24

Valid

RIR databaseRIPE

669 99%

37.205.118.0/24

Valid

RIR databaseRIPE

669 99%

37.205.119.0/24

Valid

RIR databaseRIPE

669 99%

45.143.29.0/24

Valid

RIR databaseRIPE

669 99%

45.143.30.0/24

Valid

RIR databaseRIPE

669 99%

45.146.14.0/24

Valid

RIR databaseRIPE

669 99%

45.146.15.0/24

Valid

RIR databaseRIPE

669 99%

AS-SET

AS202651 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 12 are in fix.csv.

ROA: origin6
Route object: none6

Change	Prefix or set	Detail	Full-table peers
ROA: origin	194.39.110.0/24	ROAs covering it name AS41745, not AS202651. If AS202651 should announce it, add a ROA for AS202651.	3 of 673
Route object: none	194.39.110.0/24	Route objects for it name AS41745. Add a route object with origin AS202651 in the RIR database for the space.	3 of 673
ROA: origin	151.246.137.0/24	ROAs covering it name AS834, AS211484, not AS202651. If AS202651 should announce it, add a ROA for AS202651.	2 of 673
Route object: none	151.246.137.0/24	Route objects for it name AS834. Add a route object with origin AS202651 in the RIR database for the space.	2 of 673
ROA: origin	151.246.139.0/24	ROAs covering it name AS834, AS211484, not AS202651. If AS202651 should announce it, add a ROA for AS202651.	2 of 673
Route object: none	151.246.139.0/24	Route objects for it name AS834. Add a route object with origin AS202651 in the RIR database for the space.	2 of 673
ROA: origin	151.246.140.0/24	ROAs covering it name AS834, AS211484, AS212477, not AS202651. If AS202651 should announce it, add a ROA for AS202651.	2 of 673
Route object: none	151.246.140.0/24	No route object for it. Add a route object with origin AS202651 in the RIR database for the space.	2 of 673
ROA: origin	151.246.141.0/24	ROAs covering it name AS834, AS211484, AS212477, not AS202651. If AS202651 should announce it, add a ROA for AS202651.	2 of 673
Route object: none	151.246.141.0/24	No route object for it. Add a route object with origin AS202651 in the RIR database for the space.	2 of 673
ROA: origin	151.246.143.0/24	ROAs covering it name AS834, AS211484, not AS202651. If AS202651 should announce it, add a ROA for AS202651.	2 of 673
Route object: none	151.246.143.0/24	Route objects for it name AS834. Add a route object with origin AS202651 in the RIR database for the space.	2 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

194.39.110.0/24

ROAs covering it name AS41745, not AS202651. If AS202651 should announce it, add a ROA for AS202651.

3 of 673

Route object: none

194.39.110.0/24

Route objects for it name AS41745. Add a route object with origin AS202651 in the RIR database for the space.

3 of 673

ROA: origin

151.246.137.0/24

ROAs covering it name AS834, AS211484, not AS202651. If AS202651 should announce it, add a ROA for AS202651.

2 of 673

Route object: none

151.246.137.0/24

Route objects for it name AS834. Add a route object with origin AS202651 in the RIR database for the space.

2 of 673

ROA: origin

151.246.139.0/24

ROAs covering it name AS834, AS211484, not AS202651. If AS202651 should announce it, add a ROA for AS202651.

2 of 673

Route object: none

151.246.139.0/24

Route objects for it name AS834. Add a route object with origin AS202651 in the RIR database for the space.

2 of 673

ROA: origin

151.246.140.0/24

ROAs covering it name AS834, AS211484, AS212477, not AS202651. If AS202651 should announce it, add a ROA for AS202651.

2 of 673

Route object: none

151.246.140.0/24

No route object for it. Add a route object with origin AS202651 in the RIR database for the space.

2 of 673

ROA: origin

151.246.141.0/24

ROAs covering it name AS834, AS211484, AS212477, not AS202651. If AS202651 should announce it, add a ROA for AS202651.

2 of 673

Route object: none

151.246.141.0/24

No route object for it. Add a route object with origin AS202651 in the RIR database for the space.

2 of 673

ROA: origin

151.246.143.0/24

ROAs covering it name AS834, AS211484, not AS202651. If AS202651 should announce it, add a ROA for AS202651.

2 of 673

Route object: none

151.246.143.0/24

Route objects for it name AS834. Add a route object with origin AS202651 in the RIR database for the space.

2 of 673

Route objects not announced

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