bgpreport

Network · data from 2026-11-12

AS208324 NBTEL-WIFI 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-WIFI 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

35IPv4 routes 100.0% RPKI valid · 51.4% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No ROA 17 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS208324, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS208324, 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.
91.192.4.0/24 Valid Other origin only 672 100% 67
151.244.144.0/24 Valid Nonecovered by 151.244.144.0/20 672 100% 66
151.244.148.0/24 Valid Nonecovered by 151.244.144.0/20 672 100% 67
151.244.149.0/24 Valid Nonecovered by 151.244.144.0/20 672 100% 67
151.244.150.0/24 Valid Nonecovered by 151.244.144.0/20 672 100% 67
151.244.151.0/24 Valid Nonecovered by 151.244.144.0/20 672 100% 67
151.244.152.0/24 Valid Nonecovered by 151.244.144.0/20 672 100% 67
151.244.153.0/24 Valid Nonecovered by 151.244.144.0/20 672 100% 67
151.244.154.0/24 Valid Nonecovered by 151.244.144.0/20 672 100% 67
151.244.158.0/24 Valid Nonecovered by 151.244.144.0/20 672 100% 67
151.244.159.0/24 Valid Nonecovered by 151.244.144.0/20 672 100% 67
151.244.145.0/24 Valid Nonecovered by 151.244.144.0/20 670 100% 67
151.244.146.0/24 Valid Nonecovered by 151.244.144.0/20 670 100% 67
151.244.147.0/24 Valid Nonecovered by 151.244.144.0/20 670 100% 67
151.244.156.0/24 Valid Nonecovered by 151.244.144.0/20 39 6%low visibility 21
151.244.155.0/24 Valid Nonecovered by 151.244.144.0/20 2 0%low visibility 2
151.244.157.0/24 Valid Nonecovered by 151.244.144.0/20 2 0%low visibility 2
92.119.61.0/24 Valid RIR databaseRIPE 672 100% 67
94.231.199.0/24 Valid RIR databaseRIPE 672 100% 67
176.105.237.0/24 Valid RIR databaseRIPE 672 100% 67
176.105.238.0/24 Valid RIR databaseRIPE 672 100% 67
185.89.98.0/24 Valid RIR databaseRIPE 672 100% 66
185.132.248.0/24 Valid RIR databaseRIPE 672 100% 67
185.132.249.0/24 Valid RIR databaseRIPE 672 100% 67
185.132.250.0/24 Valid RIR databaseRIPE 672 100% 67
85.31.41.0/24 Valid RIR databaseRIPE 671 100% 66
195.7.9.0/24 Valid RIR databaseRIPE 671 100% 66
45.143.31.0/24 Valid RIR databaseRIPE 670 100% 67
92.119.60.0/24 Valid RIR databaseRIPE 670 100% 67
176.105.239.0/24 Valid RIR databaseRIPE 670 100% 67
185.132.251.0/24 Valid RIR databaseRIPE 670 100% 67
194.127.108.0/24 Valid RIR databaseRIPE 670 100% 67
194.127.110.0/24 Valid RIR databaseRIPE 670 100% 67
195.7.10.0/24 Valid RIR databaseRIPE 670 100% 67
195.7.11.0/24 Valid RIR databaseRIPE 670 100% 67

AS-SET

AS208324 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 21 are in fix.csv.

  • Route object: none17
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none91.192.4.0/24Route objects for it name AS208424. Add a route object with origin AS208324 in the RIR database for the space.672 of 673
Route object: none151.244.144.0/24No route object for it. A route object for 151.244.144.0/20 with origin AS208324 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208324 in the RIR database for the space.672 of 673
Route object: none151.244.148.0/24No route object for it. A route object for 151.244.144.0/20 with origin AS208324 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208324 in the RIR database for the space.672 of 673
Route object: none151.244.149.0/24No route object for it. A route object for 151.244.144.0/20 with origin AS208324 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208324 in the RIR database for the space.672 of 673
Route object: none151.244.150.0/24No route object for it. A route object for 151.244.144.0/20 with origin AS208324 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208324 in the RIR database for the space.672 of 673
Route object: none151.244.151.0/24No route object for it. A route object for 151.244.144.0/20 with origin AS208324 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208324 in the RIR database for the space.672 of 673
Route object: none151.244.152.0/24No route object for it. A route object for 151.244.144.0/20 with origin AS208324 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208324 in the RIR database for the space.672 of 673
Route object: none151.244.153.0/24No route object for it. A route object for 151.244.144.0/20 with origin AS208324 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208324 in the RIR database for the space.672 of 673
Route object: none151.244.154.0/24No route object for it. A route object for 151.244.144.0/20 with origin AS208324 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208324 in the RIR database for the space.672 of 673
Route object: none151.244.158.0/24No route object for it. A route object for 151.244.144.0/20 with origin AS208324 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208324 in the RIR database for the space.672 of 673
Route object: none151.244.159.0/24No route object for it. A route object for 151.244.144.0/20 with origin AS208324 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208324 in the RIR database for the space.672 of 673
Route object: none151.244.145.0/24No route object for it. A route object for 151.244.144.0/20 with origin AS208324 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208324 in the RIR database for the space.670 of 673
Route object: none151.244.146.0/24No route object for it. A route object for 151.244.144.0/20 with origin AS208324 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208324 in the RIR database for the space.670 of 673
Route object: none151.244.147.0/24No route object for it. A route object for 151.244.144.0/20 with origin AS208324 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208324 in the RIR database for the space.670 of 673
Route object: none151.244.156.0/24No route object for it. A route object for 151.244.144.0/20 with origin AS208324 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208324 in the RIR database for the space.39 of 673
Route object: none151.244.155.0/24No route object for it. A route object for 151.244.144.0/20 with origin AS208324 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208324 in the RIR database for the space.2 of 673
Route object: none151.244.157.0/24No route object for it. A route object for 151.244.144.0/20 with origin AS208324 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208324 in the RIR database for the space.2 of 673

Route objects not announced

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

151.244.144.0/20RADB, RIPEValid
185.239.179.0/24RIPEValid
188.72.44.0/24RIPEValid
2a0e:be40::/29RIPENo 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.