bgpreport

Network · data from 2026-11-12

AS48966 Ooredoo Palestine (Wataniya Mobile)

Registry name: WPT Wataniya Palestine Mobile Telecommunication Company PLC, PS · PeeringDB

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

Announced routes

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

95.130.88.0/23 Valid Nonecovered by 95.130.88.0/22 673 100% 66
95.130.92.0/23 Valid Nonecovered by 95.130.92.0/22 673 100% 66
95.130.91.0/24 Valid Nonecovered by 95.130.88.0/22 672 100% 66
95.130.94.0/24 Valid Nonecovered by 95.130.92.0/22 671 100% 67
95.130.89.0/24 Valid Nonecovered by 95.130.88.0/22 1 0%low visibility 1
95.130.92.0/24 Valid Nonecovered by 95.130.92.0/22 1 0%low visibility 1
95.130.93.0/24 Valid Nonecovered by 95.130.92.0/22 1 0%low visibility 1
185.88.82.0/24 Valid Nonecovered by 185.88.82.0/23 1 0%low visibility 1
185.88.83.0/24 Valid Nonecovered by 185.88.82.0/23 1 0%low visibility 1
95.130.88.0/24 Valid Other IRR onlyRADB 1 0%low visibility 1
185.88.80.0/23 Valid RIR databaseRIPE 673 100% 67
185.88.82.0/23 Valid RIR databaseRIPE 672 100% 67

AS-SET

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

  • Route object: none9
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none95.130.88.0/23No route object for it. A route object for 95.130.88.0/22 with origin AS48966 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48966 in the RIR database for the space.673 of 673
Route object: none95.130.92.0/23No route object for it. A route object for 95.130.92.0/22 with origin AS48966 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48966 in the RIR database for the space.673 of 673
Route object: none95.130.91.0/24No route object for it. A route object for 95.130.88.0/22 with origin AS48966 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48966 in the RIR database for the space.672 of 673
Route object: none95.130.94.0/24No route object for it. A route object for 95.130.92.0/22 with origin AS48966 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48966 in the RIR database for the space.671 of 673
Route object: none95.130.89.0/24No route object for it. A route object for 95.130.88.0/22 with origin AS48966 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48966 in the RIR database for the space.1 of 673
Route object: none95.130.92.0/24No route object for it. A route object for 95.130.92.0/22 with origin AS48966 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48966 in the RIR database for the space.1 of 673
Route object: none95.130.93.0/24No route object for it. A route object for 95.130.92.0/22 with origin AS48966 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48966 in the RIR database for the space.1 of 673
Route object: none185.88.82.0/24No route object for it. A route object for 185.88.82.0/23 with origin AS48966 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48966 in the RIR database for the space.1 of 673
Route object: none185.88.83.0/24No route object for it. A route object for 185.88.82.0/23 with origin AS48966 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48966 in the RIR database for the space.1 of 673
Route object: RIR95.130.88.0/24Route object only in RADB. Add it in the RIR database for the space.1 of 673

Route objects not announced

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

95.130.88.0/22RIPENo ROA
95.130.92.0/22RIPENo 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.