Thread: Kobo website
View Single Post
Old 11-09-2021, 10:15 PM   #27
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by gtriever View Post
I too spent a lot of time with Kobo Help via Chat. Their conclusion was that it was either an ISP problem or a computer issue on my end, even though I told them it was multiple browsers, etc.

However, as of 10 minutes ago, the Kobo website came back up with a new site address. It's changed from https://www.kobo.com to https://www.kobo.com/us/en.
Which is how the site has worked for a very long time. If you use just https://www.kobo.com, it will redirect to a country and language specific site. For me, it will go to https://www.kobo.com/au/en/. I can override this when I get to the site by selecting a country and language. And they tend to be remembered for the next visit.

Looking back at your first post in this thread, the other parts of Kobo use different base URLs (help.kobo.com and xx.kobobooks.com where xx is the country code). They are hosted different ways to the book store. Or may go through different protection mechanisms. There was a change last month to www.kobo.com. It looks like Kobo is using Akamai for more than they were. If your ISP has an Akamai cache and that was misbehaving n some way, it could explain the problems you were seeing. Or it could have been an error in the DNS servers you are using and they had not updated. Your use of TOR would have avoided this and hit different Akamai caches that might have been updated properly.
davidfor is offline   Reply With Quote