Was working all summer, and not working the last few day on 4G now in France.
Still working here in US thankfully.
A few days ago, the certificate lock let from the url was red.
Now the color is normal. No clue why it wouldn’t work on 4G but there are chances it’s linked.
1 Like
I’ve seen occasional very slow load times over cable internet sporadically for the last few days. Right now it is particularly bad. Traceroute shows ~120 ms from Chicago which seems reasonable. 
1 Like
Is there any chance we can raise the issue with someone at Elektron? I don’t have Wi-Fi at home yet (just occasional access with the SFR FON thingy). So, I’m more or less locked out of using the site 
It seems to be working again, right now, and very fluid.
On my phone, it’s still broken. But when hotspotting my laptop through my phone, it seems to be working again. That wasn’t the case in the last few days. Anyway, I have some access at least! 
2 Likes
it’s been working on my lte for quite a while now - used to have issues quite often.
Right, I’ve solved it for myself and I think I can solve it for others. Basically, if it’s not working on LTE/4G in your country, you need a VPN.
As I’m an iPhone user with an iCloud+ account (I pay £2.50 for an extra 200GB of cloud storage), there’s a kinda but not really VPN built in called Private Relay. This only works on mobile Safari and has to be enabled within the iCloud+ settings
But it works flawlessly. So now I have Elektronauts back on my phone over 4G. We shouldn’t need these solutions but that’s how it is for some users for the foreseeable. Android users with problems connecting to Elektronauts can check out their built in options or get a free VPN. Good luck!
1 Like
Was still not working yesterday on my phone on 4G…
Really curious this website 
1 Like
Sounds like it could be a DNS issue - your mobile connection will likely be using a different DNS server than you home connection.
If you’re able to change your DNS server on your phone set it to Google’s public servers: 8.8.8.8 and 8.8.4.4
The only other possibility I can think of is that there’s a script or flag in the code that targets the connection type and has some kind of bug, i.e. some kind of performance enhancement for mobile connections.
1 Like
I looked into this briefly this morning btw and there’s no way I could find to target a connection type, could only be based on bandwidth which is unlikely to only impact 4G/LTE users.
I kind of find this problem fascinating tbh haha
DNS is still my best guess (but still an odd one) but I’d love to know the resolution!