bgpreport

Network · data from 2026-11-12

AS206715 UXHOST UXHOST LTD

Registry name: UXHOST UXHOST LTD, GB · not in PeeringDB

13IPv4 routes 100.0% RPKI valid · 92.3% with a route object
4IPv6 routes 75.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
7Route objects not announced registered with origin AS206715, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS206715, 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.
2a0d:d940:a0::/44 No ROA RIR databaseRIPE 635 100% 69
150.251.142.0/24 Valid None 673 100% 66
5.1.40.0/24 Valid RIR databaseRIPE 673 100% 67
92.242.165.0/24 Valid RIR databaseRIPE 673 100% 67
93.89.216.0/24 Valid RIR databaseRIPE 673 100% 67
104.165.205.0/24 Valid RIR databaseARIN, RADB 673 100% 67
140.225.208.0/24 Valid RIR databaseRIPE 673 100% 67
140.225.209.0/24 Valid RIR databaseRIPE 673 100% 67
144.31.177.0/24 Valid RIR databaseRIPE 673 100% 67
144.31.178.0/24 Valid RIR databaseRIPE 673 100% 67
89.125.94.0/24 Valid RIR databaseRIPE 672 100% 66
144.31.179.0/24 Valid RIR databaseRIPE 672 100% 67
45.88.12.0/24 Valid RIR databaseRIPE 670 100% 66
91.108.250.0/24 Valid RIR databaseRIPE 669 99% 68
2a0c:16c7:1::/48 Valid RIR databaseRIPE 636 100% 67
2a12:bec4:1c3::/48 Valid RIR databaseRIPE 634 100% 67
2a12:bec4:1c4::/48 Valid RIR databaseRIPE 9 1%low visibility 7

AS-SET

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

  • ROA: none1
  • Route object: none1
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none2a0d:d940:a0::/44No ROA covers it. Add a ROA for AS206715, maxLength 44.635 of 636
Route object: none150.251.142.0/24No route object for it. Add a route object with origin AS206715 in the RIR database for the space.673 of 673

Route objects not announced

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

144.31.176.0/24RIPEValid
179.253.94.0/23RIPEValid
2a0d:d940:90::/44RIPEValid
2a12:bec4:1c0::/48RIPEValid
2a12:bec4:1c1::/48RIPEValid
2a12:bec4:1c2::/48RIPEValid
2a12:bec4:1c5::/48RIPEValid

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.