bgpreport

Network · data from 2026-11-12

AS201738 UFO-TECHNOLOGIES-LIMITED UFO TECHNOLOGIES LIMITED

Registry name: UFO-TECHNOLOGIES-LIMITED UFO TECHNOLOGIES LIMITED, GB · not in PeeringDB

8IPv4 routes 25.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
6No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS201738, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS201738, 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.
62.204.41.0/24 No ROA RIR databaseRIPE 665 99% 66
91.240.118.0/24 No ROA RIR databaseRIPE 665 99% 66
92.255.85.0/24 No ROA RIR databaseRIPE 665 99% 66
185.11.61.0/24 No ROA RIR databaseRIPE 665 99% 66
185.81.68.0/24 No ROA RIR databaseRIPE 665 99% 66
45.93.20.0/24 No ROA RIR databaseRIPE 664 99% 66
193.178.158.0/24 Valid RIR databaseRIPE 665 99% 66
109.238.86.0/24 Valid RIR databaseRIPE 662 98% 66

AS-SET

AS201738 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 6 are in fix.csv.

  • ROA: none6
ChangePrefix or setDetailFull-table peers
ROA: none62.204.41.0/24No ROA covers it. Add a ROA for AS201738, maxLength 24.665 of 673
ROA: none91.240.118.0/24No ROA covers it. Add a ROA for AS201738, maxLength 24.665 of 673
ROA: none92.255.85.0/24No ROA covers it. Add a ROA for AS201738, maxLength 24.665 of 673
ROA: none185.11.61.0/24No ROA covers it. Add a ROA for AS201738, maxLength 24.665 of 673
ROA: none185.81.68.0/24No ROA covers it. Add a ROA for AS201738, maxLength 24.665 of 673
ROA: none45.93.20.0/24No ROA covers it. Add a ROA for AS201738, maxLength 24.664 of 673

Route objects not announced

Every route object with origin AS201738 is announced.

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.