Network · data from 2026-11-12

AS204670 NTT NTT United Kingdom Ltd

Registry name: NTT NTT United Kingdom Ltd, GB · not in PeeringDB

5IPv4 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

4Route objects not announced registered with origin AS204670, seen from no peer

Announced routes

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


128.121.15.0/24	Valid	Other IRR onlyNTTCOM	673 100%	67
128.242.94.0/24	Valid	Other IRR onlyNTTCOM, RADB	673 100%	67
131.103.30.0/24	Valid	Other IRR onlyNTTCOM	673 100%	67
140.174.224.0/24	Valid	Other IRR onlyNTTCOM	673 100%	67
168.143.179.0/24	Valid	Other IRR onlyNTTCOM, RADB	673 100%	67

AS-SET

AS204670 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 9 are in fix.csv.

Route object: RIR5
Route object: not announced4

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	128.121.15.0/24	Route object only in NTTCOM. Add it in the RIR database for the space.	673 of 673
Route object: RIR	128.242.94.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	131.103.30.0/24	Route object only in NTTCOM. Add it in the RIR database for the space.	673 of 673
Route object: RIR	140.174.224.0/24	Route object only in NTTCOM. Add it in the RIR database for the space.	673 of 673
Route object: RIR	168.143.179.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

128.121.15.0/24

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

673 of 673

Route object: RIR

128.242.94.0/24

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

673 of 673

Route object: RIR

131.103.30.0/24

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

673 of 673

Route object: RIR

140.174.224.0/24

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

673 of 673

Route object: RIR

168.143.179.0/24

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

673 of 673

Route objects not announced

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


128.121.11.0/24	NTTCOM	Valid
128.121.32.0/24	NTTCOM, RADB	Valid
128.121.43.0/24	NTTCOM	Valid
140.174.228.0/24	NTTCOM	Valid

128.121.11.0/24

NTTCOM

Valid

128.121.32.0/24

NTTCOM, RADB

Valid

128.121.43.0/24

NTTCOM

Valid

140.174.228.0/24

NTTCOM

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.