Edit: Tried it and confirmed it's indeed not on AWS, updated my previous comment.
Original: Not on AWS at all doesn't seem possible
The docs for Floating IPs [1] list 52.68.129.19 as an example, which is an AWS Elastic IP.
The docs for the API [2] says "Hyper.sh API signature algorithm is based on AWS Signature Version 4", and then proceeds to explain the differences, which is variable names. The API Domain is us-west-1.hyper.sh, which is the same URL schema as AWS (us-west-1 is also AWS's North California region).
Maybe the containers themselves are somehow not on AWS? Sure. But not on AWS at all doesn't seem to be the answer.
1. https://docs.hyper.sh/Feature/network/fip.html 2. https://docs.hyper.sh/Reference/API/2016-04-04%20[Ver.%201.2...
Based on AWS v4 does not means aws v4 is employed, on the contrary, the docs explains the signature of hyper, which uses different literatures.
At last, you can try it. Then you will found it is totally different from AWS.
You can try the api address us-west-1.hyper.sh
Resolves to 65.255.36.153 and 65.255.36.154, which don't have reverse DNS, but Maxmind Geolocates to China.
The hyper.sh API address is us-west-1.hyper.sh, which looks like the AWS style, however, it is not an AWS address and it is located in an independent IDC around Los Angels.