Network · data from 2026-11-12

AS17993 Vodafone Samoa Limited

Registry name: VODAFONESAMOA-AS-AP - Vodafone Samoa Limited, WS · PeeringDB

37IPv4 routes 100.0% RPKI valid · 100.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

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

6Route objects not announced registered with origin AS17993, seen from no peer

Announced routes

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


110.5.113.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67
110.5.114.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67
110.5.115.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67
202.4.33.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67
202.4.34.0/24	Valid	Other IRR onlyNTTCOM	667 99%	67
202.4.35.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67
202.4.37.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67
202.4.38.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67
202.4.39.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67
202.4.40.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67
202.4.41.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67
202.4.42.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67
202.4.43.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67
202.4.44.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67
202.4.45.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67
202.4.46.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67
202.4.49.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67
202.4.50.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67
202.4.51.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67
202.4.52.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67
202.4.53.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67
202.4.54.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67
202.4.55.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67
202.4.56.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67
202.4.57.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67
202.4.58.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67
202.4.59.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67
202.4.60.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67
202.4.61.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67
202.4.62.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67
202.4.63.0/24	Valid	Other IRR onlyNTTCOM, RADB	667 99%	67
110.5.112.0/24	Valid	Other IRR onlyNTTCOM, RADB	170 25%	52
202.4.32.0/24	Valid	Other IRR onlyNTTCOM, RADB	170 25%	52
202.4.48.0/24	Valid	Other IRR onlyNTTCOM, RADB	170 25%	52
110.5.112.0/22	Valid	RIR databaseAPNIC, NTTCOM	673 100%	67
202.4.32.0/19	Valid	RIR databaseAPNIC, NTTCOM, RADB	671 100%	67
203.99.255.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	667 99%	67

AS-SET

AS17993'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 40 are in fix.csv.

Route object: RIR34
Route object: not announced6

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	110.5.113.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	110.5.114.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	110.5.115.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	202.4.33.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	202.4.34.0/24	Route object only in NTTCOM. Add it in the RIR database for the space.	667 of 673
Route object: RIR	202.4.35.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	202.4.37.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	202.4.38.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	202.4.39.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	202.4.40.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	202.4.41.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	202.4.42.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	202.4.43.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	202.4.44.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	202.4.45.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	202.4.46.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	202.4.49.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	202.4.50.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	202.4.51.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	202.4.52.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	202.4.53.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	202.4.54.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	202.4.55.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	202.4.56.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	202.4.57.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	202.4.58.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	202.4.59.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	202.4.60.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	202.4.61.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	202.4.62.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	202.4.63.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	110.5.112.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	170 of 673
Route object: RIR	202.4.32.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	170 of 673
Route object: RIR	202.4.48.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	170 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

110.5.113.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

110.5.114.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

110.5.115.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

202.4.33.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

202.4.34.0/24

Route object only in NTTCOM. Add it in the RIR database for the space.

667 of 673

Route object: RIR

202.4.35.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

202.4.37.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

202.4.38.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

202.4.39.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

202.4.40.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

202.4.41.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

202.4.42.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

202.4.43.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

202.4.44.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

202.4.45.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

202.4.46.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

202.4.49.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

202.4.50.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

202.4.51.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

202.4.52.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

202.4.53.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

202.4.54.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

202.4.55.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

202.4.56.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

202.4.57.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

202.4.58.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

202.4.59.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

202.4.60.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

202.4.61.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

202.4.62.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

202.4.63.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

110.5.112.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

170 of 673

Route object: RIR

202.4.32.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

170 of 673

Route object: RIR

202.4.48.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

170 of 673

Route objects not announced

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


103.131.62.0/24	APNIC	Valid
202.4.32.0/21	APNIC, NTTCOM	Valid
202.4.36.0/24	NTTCOM, RADB	Valid
202.4.40.0/21	APNIC, NTTCOM, RADB	Valid
202.4.47.0/24	NTTCOM, RADB	Valid
202.4.48.0/20	APNIC, NTTCOM, RADB	Valid

103.131.62.0/24

APNIC

Valid

202.4.32.0/21

APNIC, NTTCOM

Valid

202.4.36.0/24

NTTCOM, RADB

Valid

202.4.40.0/21

APNIC, NTTCOM, RADB

Valid

202.4.47.0/24

NTTCOM, RADB

Valid

202.4.48.0/20

APNIC, NTTCOM, RADB

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.