bgpreport

Network · data from 2026-11-12

AS203363 Kuroit (UK)

Registry name: KUROIT Kuroit Limited, GB · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS203363, 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.
2a05:4140:19::/48 Invalid: origin None 129 20% 48
147.90.210.0/24 Invalid: origin None 2 0%low visibility 2
91.205.158.0/24 Valid RIR databaseRIPE 672 100% 66
109.205.214.0/24 Valid RIR databaseRIPE 672 100% 66
178.93.148.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
2.58.203.0/24 Valid RIR databaseRIPE 670 100% 67
5.83.214.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
45.67.85.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
45.80.193.0/24 Valid RIR databaseRIPE 670 100% 67
46.37.124.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
2401:8360:a3::/48 Valid RIR databaseAPNIC 636 100% 67

AS-SET

AS203363'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 19 are in fix.csv.

  • ROA: origin2
  • Route object: none2
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: origin2a05:4140:19::/48ROAs covering it name AS212271, not AS203363. If AS203363 should announce it, add a ROA for AS203363.129 of 636
Route object: none2a05:4140:19::/48No route object for it. Add a route object with origin AS203363 in the RIR database for the space.129 of 636
ROA: origin147.90.210.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS203363 should announce it, add a ROA for AS203363.2 of 673
Route object: none147.90.210.0/24No route object for it. Add a route object with origin AS203363 in the RIR database for the space.2 of 673

Route objects not announced

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

2.58.201.0/24RIPEValid
45.67.84.0/24RIPEValid
103.244.226.0/24APNIC, RADBValid
109.69.111.0/24RIPEValid
178.239.171.0/24RIPEValid
185.216.72.0/24RIPEValid
193.176.28.0/24RIPEValid
216.180.126.0/24ARINValid
2401:8360:3::/48APNICValid
2401:8360:4::/48APNICValid
2401:8360:7::/48APNICValid
2401:8360:8::/48APNICValid
2401:8360:9::/48APNICValid
2401:8360:a::/48APNICValid
2401:8360:a2::/48APNICValid

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.