Network · data from 2026-11-12

AS211559 vodafoneqa-ISP Vodafone Qatar P.Q.S.C

Registry name: vodafoneqa-ISP Vodafone Qatar P.Q.S.C, QA · not in PeeringDB

35IPv4 routes 100.0% RPKI valid · 94.3% with a route object

2IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 2 with no route object for this origin

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

14Route objects not announced registered with origin AS211559, seen from no peer

Announced routes

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


185.25.12.0/23	Valid	Other origin only	667 99%	67
185.25.14.0/23	Valid	Other origin only	667 99%	67
212.70.120.0/24	Valid	RIR databaseRIPE	672 100%	67
212.70.121.0/24	Valid	RIR databaseRIPE	672 100%	67
80.76.166.0/23	Valid	RIR databaseRADB, RIPE	671 100%	67
80.76.168.0/23	Valid	RIR databaseRADB, RIPE	671 100%	67
103.23.126.0/24	Valid	RIR databaseRIPE	671 100%	67
103.23.127.0/24	Valid	RIR databaseRADB, RIPE	671 100%	67
212.70.103.0/24	Valid	RIR databaseRADB, RIPE	671 100%	67
212.70.105.0/24	Valid	RIR databaseRADB, RIPE	671 100%	67
212.70.122.0/24	Valid	RIR databaseRIPE	671 100%	67
212.70.123.0/24	Valid	RIR databaseRADB, RIPE	671 100%	67
212.70.124.0/24	Valid	RIR databaseRADB, RIPE	671 100%	67
37.186.49.0/24	Valid	RIR databaseRIPE	670 100%	67
37.186.56.0/24	Valid	RIR databaseRIPE	670 100%	67
37.186.57.0/24	Valid	RIR databaseRIPE	670 100%	67
37.186.60.0/22	Valid	RIR databaseRADB, RIPE	670 100%	67
80.76.167.0/24	Valid	RIR databaseRADB, RIPE	670 100%	67
87.61.192.0/23	Valid	RIR databaseRADB, RIPE	670 100%	67
103.225.72.0/24	Valid	RIR databaseRIPE	670 100%	67
103.225.73.0/24	Valid	RIR databaseRIPE	670 100%	67
103.225.74.0/24	Valid	RIR databaseRIPE	670 100%	67
185.247.88.0/22	Valid	RIR databaseRIPE	670 100%	67
212.70.100.0/24	Valid	RIR databaseRADB, RIPE	670 100%	67
212.70.101.0/24	Valid	RIR databaseRADB, RIPE	670 100%	67
212.70.104.0/24	Valid	RIR databaseRADB, RIPE	670 100%	67
80.76.166.0/24	Valid	RIR databaseRADB, RIPE	669 99%	67
103.14.208.0/22	Valid	RIR databaseRIPE	669 99%	67
103.17.0.0/24	Valid	RIR databaseRIPE	669 99%	67
80.76.168.0/24	Valid	RIR databaseRIPE	668 99%	67
212.70.102.0/24	Valid	RIR databaseRADB, RIPE	667 99%	67
31.11.48.0/21	Valid	RIR databaseRIPE	666 99%	67
37.186.38.0/24	Valid	RIR databaseRIPE	666 99%	67
80.76.165.0/24	Valid	RIR databaseRADB, RIPE	666 99%	67
80.76.169.0/24	Valid	RIR databaseRIPE	656 97%	67
2a04:7f80:85::/48	Valid	RIR databaseRADB, RIPE	635 100%	68
2a04:7f80:84::/48	Valid	RIR databaseRADB, RIPE	634 100%	67

AS-SET

AS211559 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 16 are in fix.csv.

Route object: none2
Route object: not announced14

Change	Prefix or set	Detail	Full-table peers
Route object: none	185.25.12.0/23	Route objects for it name AS48728. Add a route object with origin AS211559 in the RIR database for the space.	667 of 673
Route object: none	185.25.14.0/23	Route objects for it name AS48728. Add a route object with origin AS211559 in the RIR database for the space.	667 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

185.25.12.0/23

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

667 of 673

Route object: none

185.25.14.0/23

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

667 of 673

Route objects not announced

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


31.11.55.0/24	RIPE	Valid
37.186.60.0/24	RIPE	Valid
37.186.61.0/24	RIPE	Invalid: maxLength
37.186.62.0/24	RIPE	Invalid: maxLength
37.186.63.0/24	RIPE	Invalid: maxLength
103.14.208.0/24	RIPE	Valid
103.14.209.0/24	RIPE	Invalid: maxLength
103.14.210.0/24	RIPE	Invalid: maxLength
103.14.211.0/24	RIPE	Valid
103.225.72.0/23	RIPE	No ROA
185.247.89.0/24	RIPE	Valid
212.70.100.0/22	RIPE	Invalid: origin
212.70.104.0/22	RIPE	Invalid: origin
213.178.136.0/22	RIPE	Valid

31.11.55.0/24

RIPE

Valid

37.186.60.0/24

RIPE

Valid

37.186.61.0/24

RIPE

Invalid: maxLength

37.186.62.0/24

RIPE

Invalid: maxLength

37.186.63.0/24

RIPE

Invalid: maxLength

103.14.208.0/24

RIPE

Valid

103.14.209.0/24

RIPE

Invalid: maxLength

103.14.210.0/24

RIPE

Invalid: maxLength

103.14.211.0/24

RIPE

Valid

103.225.72.0/23

RIPE

No ROA

185.247.89.0/24

RIPE

Valid

212.70.100.0/22

RIPE

Invalid: origin

212.70.104.0/22

RIPE

Invalid: origin

213.178.136.0/22

RIPE

Valid

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.