bgpreport

Network · data from 2026-11-12

AS44259 Ultahost

Registry name: ULTAHOST-AP-AS Ultahost, Inc., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS44259, 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.
192.142.14.0/24 Invalid: origin Other origin only 2 0%low visibility 2
103.227.210.0/24 Valid Other IRR onlyRADB 672 100% 67
82.47.165.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
95.135.255.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
168.222.75.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
31.59.184.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
103.26.10.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
103.72.101.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
154.18.187.0/24 Valid RIR databaseARIN 671 100% 67
154.18.239.0/24 Valid RIR databaseARIN 671 100% 67
192.142.4.0/24 Valid RIR databaseAFRINIC 671 100% 67
192.142.35.0/24 Valid RIR databaseAFRINIC 671 100% 67
192.142.50.0/24 Valid RIR databaseAFRINIC 671 100% 67
192.142.51.0/24 Valid RIR databaseAFRINIC 671 100% 67
216.185.57.0/24 Valid RIR databaseARIN, RADB 671 100% 67
38.89.142.0/24 Valid RIR databaseARIN 670 100% 67
38.127.8.0/24 Valid RIR databaseARIN 670 100% 67
38.127.216.0/24 Valid RIR databaseARIN 670 100% 67
38.134.189.0/24 Valid RIR databaseARIN 670 100% 67
38.247.64.0/24 Valid RIR databaseARIN 670 100% 67

AS-SET

AS44259'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 5 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin192.142.14.0/24ROAs covering it name AS212238, not AS44259. If AS44259 should announce it, add a ROA for AS44259.2 of 673
Route object: none192.142.14.0/24Route objects for it name AS212238. Add a route object with origin AS44259 in the RIR database for the space.2 of 673
Route object: RIR103.227.210.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

147.90.205.0/24RADB, RIPEValid
168.222.17.0/24RADB, RIPEValid

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.