What is going on with game worlds? I can't enter to any world with my airlines (R1, Rδ) - always got error "DNS_PROBE_FINISHED_NXDOMAIN".
All servers are dead?
#1
Posted 28 January 2019 - 06:45 AM
#2
Posted 28 January 2019 - 06:46 AM
I am having the same problems as you.
#3
Posted 28 January 2019 - 07:57 AM
Ditto. It's not the first time. It will come back. Maybe Yuxi's taken it offline to load up some surprises for us? New gameworlds were due to start in the last couple of hours. Maybe there were some issues. Or, as I said, surprises in store?
#4
Posted 28 January 2019 - 08:03 AM
Update: O1 has now restarted (about 2 hours behind UTC 06:00), currently at January 2 as I write this. Still can't access it however.
#5
Posted 28 January 2019 - 08:27 AM
Still can't access it however.
Can you try https://kinsta.com/k...lear-dns-cache/and see if it helps? There was a hiccup earlier with a domain/nameserver change for the website, but everything should be back up now.
#6
Posted 28 January 2019 - 11:32 AM
Can you try https://kinsta.com/k...lear-dns-cache/and see if it helps? There was a hiccup earlier with a domain/nameserver change for the website, but everything should be back up now.
Tried that as suggested. Followed the procedures as specified. No different. Still can't log in to the airline game world.
#7
Posted 28 January 2019 - 11:43 AM
Tried a complete restart after clearing my cache thingy. Still can't log in to the game worlds.
#8
Posted 28 January 2019 - 12:19 PM
Woohoo! Appears now fixed! Thank you!
#9
Posted 28 January 2019 - 01:15 PM
#10
Guest_wings203_*
Posted 28 January 2019 - 10:40 PM
Not sure if it's related, but I'm experiencing some issues too...
When I go and click on 'enter world' to deal with my existing airline, I get an error of this site can't be reached ('ERR_NAME_NOT RESOLVED'). Is there something I can do to fix this, or is there an issue with the entire site right now?
#11
Posted 28 January 2019 - 10:53 PM
Maybe it is region specific?
#12
Guest_wings203_*
Posted 29 January 2019 - 05:34 AM
Resolved after a few hours, not sure why it was occurring...
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users