A post was merged into an existing topic: Service down 08/12/2023
2 posts were merged into an existing topic: Service down 08/12/2023
New IP with location as London but still no Tiktok
Been fine all day in West Yorkshire on the “old” network.
Just had the disconnect now with the move to the new network. Just got my brand new Iranian IP. Hopefully this issue with the geo is fixed in the morning as stated by @Yayzi_Team on the other thread.
It will be we jumped the gun a little trying to get rid of the bad IP range.
So it seems, based on my speed test being 900/900ish and email stating new network clients will be traffic managed temporarily, that i am on the old network but on one of new IPs (31.57.x.x). Is this possibly accurate?
So router went off so rebooted and have switched from 31.57 to 79.135 and apart from yayzi.co.uk it’s a bit slow, lagy bandwidth limiting for now I can understand.
But with several sites inaccessible, here’s a few:
- microsoft update
- intel.com
- speedtest.net
- github
other sites take awhile and partially load minus any images.
Can you please advise what IP range I should be on now as have 31.57 at the moment but still can’t access TikTok - and that’s for the kids not me, before anyone flames me!
Hmm, some other sites still not working either.
Looks like I’ve been migrated over night to the 31.57.x range too.
Given it shows as Iran, is this the bad range? Do I need to reboot my router?
We are aware of an ongoing issue where some IP addresses are incorrectly showing as being located in Iran. Our team is actively addressing this matter and collaborating closely with our GeoDB (Geolocation Database) providers to rectify the situation as quickly as possible.
Key Points:
- The issue affects only a subset of IP addresses
- We are in direct communication with GeoDB providers
- A solution is being expedited to ensure accurate geolocation data
We appreciate your patience and understanding as we work to resolve this discrepancy. We will provide updates as soon as the geolocation data has been corrected.
TLDR: We are aware of the GeoDB issue and it’s being resolved
Does this copy and paste response apply to me as it’s not clear and I didn’t mention Iran?!
We are aware of an ongoing issue where some IP addresses are incorrectly showing as being located in Iran. Our team is actively addressing this matter and collaborating closely with our GeoDB (Geolocation Database) providers to rectify the situation as quickly as possible.
Key Points:
- The issue affects only a subset of IP addresses
- We are in direct communication with GeoDB providers
- A solution is being expedited to ensure accurate geolocation data
We appreciate your patience and understanding as we work to resolve this discrepancy. We will provide updates as soon as the geolocation data has been corrected.
TLDR: We are aware of the GeoDB issue and it’s being resolved
I second this. Fast.com does not load at wll
And it’s gone down again, in the middle of the day, whilst I’m trying to work from home
I was on a 3x io address and sites were loading but other pc applications that needed internet access weren’t eg sky go…
Now however my connection is gone completely
See status: Apology for Downtime and Update on Migration Progress - #2
But essentially, the 31 range Yayzi brought was not fit for purpose, many GEO issues with thinking we were all in Iran.
Yayzi last night attemtped to bulk move all 31 range to a 213 range (a range that has been UK educational based for ~10years), this did fail, so Yayzi went back to previous IP’s temporarily.
This morning everyone was put back on a 213 range, hence the blip at 9.30am GMT.
There wasn’t a great heads up, this needs to be improved IMO. The good news is that those now on 213 should not face any GEO issues.
If you are not on a 213 IP, it is likely you have not been migrated yet.
If you are still facing no internet, the best thing to do is email [email protected]
I don’t work for Yayzi, simply trying to give an overview of what’s happened the past 12 hours.
What an awesome reply and summary, Thank you, Drop