bgpreport

Network · data from 2026-11-12

AS149175 UFWDTL-AS-AP - UNION FU WAH DIGITAL TECHNOLOGY LIMITED

Registry name: UFWDTL-AS-AP - UNION FU WAH DIGITAL TECHNOLOGY LIMITED, HK · not in PeeringDB

62IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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
29Route objects not announced registered with origin AS149175, seen from no peer

Announced routes

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

39.109.67.0/24 Valid RIR databaseAPNIC 672 100% 67
39.109.68.0/24 Valid RIR databaseAPNIC 672 100% 67
39.109.69.0/24 Valid RIR databaseAPNIC 672 100% 67
39.109.70.0/24 Valid RIR databaseAPNIC 672 100% 67
39.109.72.0/24 Valid RIR databaseAPNIC 672 100% 67
39.109.74.0/24 Valid RIR databaseAPNIC 672 100% 67
39.109.76.0/24 Valid RIR databaseAPNIC 672 100% 67
39.109.78.0/24 Valid RIR databaseAPNIC 672 100% 67
39.109.80.0/24 Valid RIR databaseAPNIC 672 100% 67
39.109.82.0/24 Valid RIR databaseAPNIC 672 100% 67
39.109.84.0/24 Valid RIR databaseAPNIC 672 100% 67
39.109.85.0/24 Valid RIR databaseAPNIC 672 100% 67
39.109.89.0/24 Valid RIR databaseAPNIC 672 100% 67
39.109.93.0/24 Valid RIR databaseAPNIC 672 100% 67
39.109.94.0/24 Valid RIR databaseAPNIC 672 100% 67
39.109.95.0/24 Valid RIR databaseAPNIC 672 100% 67
61.15.64.0/24 Valid RIR databaseAPNIC 672 100% 67
61.15.65.0/24 Valid RIR databaseAPNIC 672 100% 67
61.15.66.0/24 Valid RIR databaseAPNIC 672 100% 67
61.15.67.0/24 Valid RIR databaseAPNIC 672 100% 67
61.15.68.0/24 Valid RIR databaseAPNIC 672 100% 67
61.15.69.0/24 Valid RIR databaseAPNIC 672 100% 67
61.15.70.0/24 Valid RIR databaseAPNIC 672 100% 67
61.15.71.0/24 Valid RIR databaseAPNIC 672 100% 67
61.15.76.0/22 Valid RIR databaseAPNIC 672 100% 67
61.15.80.0/22 Valid RIR databaseAPNIC 672 100% 67
61.15.84.0/24 Valid RIR databaseAPNIC 672 100% 67
61.15.85.0/24 Valid RIR databaseAPNIC 672 100% 67
61.15.86.0/24 Valid RIR databaseAPNIC 672 100% 67
61.15.87.0/24 Valid RIR databaseAPNIC 672 100% 67
61.15.112.0/24 Valid RIR databaseAPNIC 672 100% 67
61.15.113.0/24 Valid RIR databaseAPNIC 672 100% 67
61.15.114.0/24 Valid RIR databaseAPNIC 672 100% 67
61.15.115.0/24 Valid RIR databaseAPNIC 672 100% 67
103.82.216.0/24 Valid RIR databaseAPNIC 672 100% 67
103.82.217.0/24 Valid RIR databaseAPNIC 672 100% 67
103.98.14.0/24 Valid RIR databaseAPNIC 672 100% 67
103.119.132.0/24 Valid RIR databaseAPNIC 672 100% 67
103.119.133.0/24 Valid RIR databaseAPNIC 672 100% 67
103.120.228.0/24 Valid RIR databaseAPNIC 672 100% 67
103.120.229.0/24 Valid RIR databaseAPNIC 672 100% 67
103.227.128.0/24 Valid RIR databaseAPNIC 672 100% 67
103.227.129.0/24 Valid RIR databaseAPNIC 672 100% 67
103.227.131.0/24 Valid RIR databaseAPNIC 672 100% 67
202.181.179.0/24 Valid RIR databaseAPNIC 672 100% 67
202.181.221.0/24 Valid RIR databaseAPNIC 672 100% 67
202.181.222.0/24 Valid RIR databaseAPNIC 672 100% 67
203.168.221.0/24 Valid RIR databaseAPNIC 672 100% 67
203.168.238.0/24 Valid RIR databaseAPNIC 672 100% 67
203.168.244.0/24 Valid RIR databaseAPNIC 672 100% 67
203.168.245.0/24 Valid RIR databaseAPNIC 672 100% 67
203.168.246.0/24 Valid RIR databaseAPNIC 672 100% 67
203.168.247.0/24 Valid RIR databaseAPNIC 672 100% 67
203.168.248.0/24 Valid RIR databaseAPNIC 672 100% 67
203.168.249.0/24 Valid RIR databaseAPNIC 672 100% 67
203.168.250.0/24 Valid RIR databaseAPNIC 672 100% 67
203.168.251.0/24 Valid RIR databaseAPNIC 672 100% 67
203.168.253.0/24 Valid RIR databaseAPNIC 672 100% 67
203.168.255.0/24 Valid RIR databaseAPNIC 672 100% 67
222.167.36.0/22 Valid RIR databaseAPNIC 672 100% 67
222.167.40.0/24 Valid RIR databaseAPNIC 672 100% 67
39.109.88.0/24 Valid RIR databaseAPNIC 666 99% 67
2403:e840::/33 Valid RIR databaseAPNIC, RADB 636 100% 67

AS-SET

AS149175 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 29 are in fix.csv.

  • Route object: not announced29

Route objects not announced

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

39.109.71.0/24APNICValid
39.109.73.0/24APNICValid
39.109.75.0/24APNICValid
39.109.79.0/24APNICValid
39.109.92.0/24APNICValid
61.15.70.0/23APNICValid
61.15.72.0/22APNICValid
61.15.72.0/23APNICValid
61.15.74.0/23APNICValid
61.15.84.0/23APNICValid
61.15.88.0/22APNICValid
61.15.88.0/23APNICValid
61.15.88.0/24APNICValid
61.15.89.0/24APNICValid
61.15.90.0/23APNICValid
61.15.90.0/24APNICValid
61.15.91.0/24APNICValid
61.15.97.0/24APNICValid
103.82.218.0/24APNICValid
103.82.219.0/24APNICValid
103.98.15.0/24APNICValid
103.120.228.0/23APNICValid
103.144.40.0/24APNICValid
163.53.16.0/24APNIC, RADBValid
202.181.137.0/24APNICValid
202.181.138.0/24APNICValid
202.181.142.0/24APNICValid
202.181.149.0/24APNICValid
202.181.155.0/24APNICValid

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.