In reply to a post by AndyPandy:

The problem with that, and all DDNS services, is Linux (CentOS 7 in my case) doesn't seem to have a way to require a hostname, only and IP. This makes sense from a security perspective, as a domain could be hijacked and pointed to a threat actor's IP.

At least I've not found a way...

Veering way off topic here, but you can use Authelia to set up local SSO. A Cloudflare tunnel never exposes your WAN IP to anyone, but will allow you to use a DNS subdomain to connect to your services. All of that can have SSL certificates and is all free open source software. Everything can be configured in Docker containers relatively easily. It does depend how much time you want to spend tinkering vs the benefit you get from it of course!

At the end of the day, if Hey! could just keep my IP static, I wouldn't have any issues at all!

They seem to just move you onto an IP that "works", instead of addressing issues with other IP ranges.

Hey guys, has anyone been experiencing much poorer latency to AWS services lately on Hey!B? Particularly on games like R6 Siege, Apex, Fortnite?

CMD ping to amazon.co.uk is also pretty high (50ms+)... and cloudping.info shows high ping to europe-based amazon servers (previously single digit latency.. now 50ms+), VPN makes latency <20ms...
BQM normal and outside of AWS services latency is same as before

Its happening strictly to AWS... Anyone else? Looks like a routing issue perhaps?

It seems traffic is going via NEAR IP S.L., their not so great peer, instead of Cogent Communications, which is a decent peer. They only have 2....

Here's my trace to amazon.co.uk:

Tracing route to amazon.co.uk [178.236.7.220]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms RT-AC86U-1310 [192.168.0.1]
2 5 ms 4 ms 4 ms ip3.apfutura.net [31.214.156.3]
3 4 ms 4 ms 4 ms 172.16.245.2
4 4 ms 4 ms 5 ms 194.35.42.12 - This is NEAR IP S.L.
5 * * * Request timed out.
6 25 ms 25 ms 25 ms 172.16.253.14 - Still inside a private network, and this is the latency???
7 25 ms 25 ms 24 ms 185.1.68.95 - Congratulations, you're in Spain!
8 30 ms 25 ms 25 ms 52.93.96.137 - Now in Amazon's network.
9 * * * Request timed out.
10 26 ms 26 ms 29 ms 52.93.17.205
11 27 ms 25 ms 25 ms 52.93.17.95
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 56 ms 55 ms 56 ms 178.236.7.220 - Amazon Ireland

Subjectively, I've noticed general browsing to some major sites (linkedin, twitter, facebook) to be very laggy today.

Edit: I ran a test here: https://aws-latency-test.com/ and the best latency to AWS is in Spain, so it does seem to be a routing issue. Probably related to F&W being run by a bloke that started off in Spain (Carlos Bock).

Edited by AndyPandy (Sat 13-Jan-24 18:07:25)

Hey Andy,

Thanks for going to the lengths to test it out.

I am considering sending an e-mail to them to check it out as its gotten quite annoying affecting gaming on AWS services and such.

Wonderful to know that their traffic is going to Spain and then coming back to Ireland???! :/

Wonder if it'll be simple for them to fix it though ...

As it's a routing issue, they should be able to sort it.

Interestingly NEAR IP S.L. (Based in Spain) appears to be majority owned by APFUTURA TELECOM SL (Based in Spain), of which Carlos Bock is a director. As he also is of F&W networks & Hey!Broadband.

It's a very twisted web that he weaves!

I recently got assigned a new IP in the 95.82.x.x range after the last bout of network upgrades/maintenance and although stability and uptime has been fine since I got this IP.. I'm having trouble accessing my bank account from any devices which are using the WiFi or the hey connection in general. I get the 'Service Unavailable - Unfortunately, Online Banking and some of our other services are not available in your current location, if you need help, contact us on the relevant number below.' message every time I go to login. And a Something went wrong error when trying to use the app on my mobile phone.

I reached out to Hey just after new year on the 2nd, heard nothing back all week so sent off a follow up email on Friday pretty much saying nothing has changed and I'm still locked out of the banking app/site. It's been about 9 days since that last follow up email I sent and STILL HAD NOTHING BACK.

I've tried to get myself assigned a new IP manually by shutting off the ONT and Adtran for a few minutes then booting it back up in hope it'll churn out a different IP which it's done in the past without issues, but it seems this time I'm stuck with this troublesome IP address.. I've explained to them I have no mobile data on my phone so I can't just use the app on mobile bypassing the hey connection

I think this is pretty bad considering it's probably a 5 second fix for them, all they have to do is assign me an IP in a different range from their end and I'll be able to access everything again.

But it seems they're just blatantly ignoring my communications or just have nobody manning the email department in support?

Wonder how much longer they're going to keep me locked out of certain services

Just thought I'd share this little story here

Should certainly be possible to get a wan ip in a different subnet but you'll need to leave the ont off for a few hours.

My trace is very similar to yours, and I also have been getting laggy response from websites the past few days (maybe a week, hard to recall). Mainly slowness in loading the initial page or refreshing. Bandwidth has been fine & fortunately the latency doesn't seem to be affecting my work connection, though I have been off since Tuesday last week... If it starts affecting that, I'll have to look into it some more.

Text

1 23 45 67 89 1011 1213 1415 1617 1819 2021 2223

Tracing route to amazon.co.uk [54.239.34.171] over a maximum of 30 hops:    1    <1 ms    <1 ms    <1 ms  192.168.0.123  2     4 ms     4 ms     4 ms  38.9.8.3   3     4 ms     5 ms    17 ms  172.16.245.2  4    12 ms     4 ms     4 ms  194.35.42.12   5     *        *        *     Request timed out.  6    24 ms    25 ms    25 ms  172.16.253.14   7    25 ms    32 ms    31 ms  185.1.68.95  8    36 ms    26 ms    26 ms  52.93.96.135   9     *        *        *     Request timed out. 10    25 ms    26 ms    25 ms  52.93.17.197  11    25 ms    26 ms    25 ms  52.93.17.29 12     *        *        *     Request timed out.  13     *        *        *     Request timed out. 14     *        *        *     Request timed out.  15     *        *        *     Request timed out. 16     *        *        *     Request timed out.  17     *        *        *     Request timed out. 18     *        *        *     Request timed out.  19     *        *        *     Request timed out. 20    56 ms    56 ms    56 ms  54.239.34.171

In reply to a post by Henry8:

Should certainly be possible to get a wan ip in a different subnet but you'll need to leave the ont off for a few hours.

Gonna give that a go tonight before bed as I don't think HeyBB support are going to respond any time soon, cheers