Network · data from 2026-11-12

AS202038 INTERCITY-TECH-UKCORE Intercity Technology Ltd

Registry name: INTERCITY-TECH-UKCORE Intercity Technology Ltd, GB · not in PeeringDB

19IPv4 routes 100.0% RPKI valid · 94.7% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

0No ROA 1 with no route object for this origin

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

2Route objects not announced registered with origin AS202038, seen from no peer

Announced routes

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


109.234.224.0/21	Valid	Other origin only	673 100%	66
94.199.232.0/21	Valid	RIR databaseRIPE	673 100%	66
94.199.234.0/23	Valid	RIR databaseRIPE	673 100%	66
94.199.239.0/24	Valid	RIR databaseRIPE	673 100%	66
109.234.228.0/23	Valid	RIR databaseRIPE	673 100%	66
185.78.216.0/23	Valid	RIR databaseRIPE	673 100%	66
185.78.217.0/24	Valid	RIR databaseRIPE	673 100%	66
185.108.92.0/22	Valid	RIR databaseRIPE	673 100%	66
185.108.94.0/24	Valid	RIR databaseRIPE	673 100%	66
94.199.232.0/23	Valid	RIR databaseRIPE	672 100%	66
94.199.236.0/23	Valid	RIR databaseRIPE	672 100%	66
94.199.238.0/24	Valid	RIR databaseRIPE	672 100%	66
109.234.224.0/24	Valid	RIR databaseRIPE	672 100%	66
109.234.226.0/23	Valid	RIR databaseRIPE	672 100%	66
185.78.216.0/24	Valid	RIR databaseRIPE	672 100%	66
109.234.225.0/24	Valid	RIR databaseRIPE	308 46%	51
185.108.95.0/24	Valid	RIR databaseRIPE	308 46%	51
185.108.92.0/24	Valid	RIR databaseRIPE	18 3%low visibility	17
185.108.93.0/24	Valid	RIR databaseRIPE	18 3%low visibility	17

109.234.224.0/21

Valid

Other origin only

673 100%

94.199.232.0/21

Valid

RIR databaseRIPE

673 100%

94.199.234.0/23

Valid

RIR databaseRIPE

673 100%

94.199.239.0/24

Valid

RIR databaseRIPE

673 100%

109.234.228.0/23

Valid

RIR databaseRIPE

673 100%

185.78.216.0/23

Valid

RIR databaseRIPE

673 100%

185.78.217.0/24

Valid

RIR databaseRIPE

673 100%

185.108.92.0/22

Valid

RIR databaseRIPE

673 100%

185.108.94.0/24

Valid

RIR databaseRIPE

673 100%

94.199.232.0/23

Valid

RIR databaseRIPE

672 100%

94.199.236.0/23

Valid

RIR databaseRIPE

672 100%

94.199.238.0/24

Valid

RIR databaseRIPE

672 100%

109.234.224.0/24

Valid

RIR databaseRIPE

672 100%

109.234.226.0/23

Valid

RIR databaseRIPE

672 100%

185.78.216.0/24

Valid

RIR databaseRIPE

672 100%

109.234.225.0/24

Valid

RIR databaseRIPE

308 46%

185.108.95.0/24

Valid

RIR databaseRIPE

308 46%

185.108.92.0/24

Valid

RIR databaseRIPE

18 3%low visibility

185.108.93.0/24

Valid

RIR databaseRIPE

18 3%low visibility

AS-SET

AS202038 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 3 are in fix.csv.

Route object: none1
Route object: not announced2

Change	Prefix or set	Detail	Full-table peers
Route object: none	109.234.224.0/21	Route objects for it name AS205402. Add a route object with origin AS202038 in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

109.234.224.0/21

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

673 of 673

Route objects not announced

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


2a02:8d1::/32	RIPE	No ROA
2a05:6b00::/29	RIPE	No ROA

2a02:8d1::/32

RIPE

No ROA

2a05:6b00::/29

RIPE

No 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.