The hosting is actually not bad ;-) We may have expensive phone calls but when it comes to Internet, I had a 50 Mbit connection when tons of people in the western world were still on modems ;-)
I think all this just confirms that there are a couple of important junctions that block these servers and as a result the site might be unavailable for half of the planet (maybe more, maybe less). I think we just have to wait...
The Real Wizard · Member since
But what has changed in the last few weeks? Am I missing something?
GratefulFan · Member since
The whole thing completely fascinates me. What has happened? From a technical standpoint, what is going on? In Canada, why is Bell/Eastlink/Rogers routing killing this right out of the gate and Shaw letting it out just fine? What's Telus doing? Is this like an optional blacklist? Or has something broken and the propagation of the fixed routes is just taking longer for some services than others? What is the scope of this? I'm hoping everybody who has posted failed traceroutes will post them again once things are back up. I'm just terribly curious about the technical details behind this, and what the point of failure(?) was. The interwebs are supposed to be drunk with redundancy and yet this is impacting at least 5 or 6 countries based on this little QZ sampling alone. Weird and interesting.
cjpew · Member since
To answer above question about Telus - my ISP is Telus - I haven't been able to get to the site for days.
Mr. Scully · Member since
I believe it's some kind of blacklist that is shared among a lof of providers... but I have never experienced anything like that before. It's like if some routes were dead ends while some kept working normally. Even the redundancy doesn't help for some reason. Weird situation... please let me know if things return back to normal.
Mr. Scully · Member since
Btw. the stats show a decrease in the amount of visitors by about 20%.
thomasquinn 32989 · Member since
[QUOTE] [b]Mr. Scully wrote:[/b]
Btw. the stats show a decrease in the amount of visitors by about 20%.[/QUOTE]
Interesting. That means some people can still log on. Any similarities between their IP-addresses, e.g. distinct geographic regions?
Marcos Napier · Member since
The fact that downforeveryone reports it as being available shows that the connection is being cut somewhere. It might be a DNS caching/propagation issue in the middle of the way. It's not uncommon to have connection issues to a specific backbone either. The IP used by the site might be in a blacklist too, considering a lot of IPs are shared by a lot of different domains it could be sharing the IP with a spam site, for example, and it's being blocked somewhere.
I remember this page that used to list all the sites/domains hosted in the same IP/server, and it was very useful to find problems: http://www.yougetsignal.com/tools/web-sites-on-web-server/
You just have to try some of these sites in the list, and if they work, the problem maybe is in the configuration of your own domain, not the server.
In a similar situation, when you register and start a domain name hosting, sometimes it takes up to 72 hours for it to appear in certain places (depending on how often they update their DNS list) while in others it appears nearly immediately, but the IP responds to ping and tracert, just the page isn't displayed.
Marknow · Member since
Clear your cache and cookies folks, might help.
Marcos Napier · Member since
Just tested a bunch of these domains hosted in the same IP, all have the same problem. It's more serious than cache and cookies.
pittrek · Member since
[QUOTE] [b]thomasquinn 32989 wrote:[/b]
[QUOTE] [b]Mr. Scully wrote:[/b]
Btw. the stats show a decrease in the amount of visitors by about 20%.[/QUOTE]
Interesting. That means some people can still log on. Any similarities between their IP-addresses, e.g. distinct geographic regions?[/QUOTE]
As I wrote I could access the site from both Slovakia and Austria (Vienna)
GratefulFan · Member since
[QUOTE] [b]Mr. Scully wrote:[/b]
Btw. the stats show a decrease in the amount of visitors by about 20%.[/QUOTE]
Interestingly, when I ran thinline.cz through dns.squish.net just now 20% of the traffic is the figure that was noted to have failed. All through one of five top level .cz DNS resolvers: d.ns.nic.cz. Other DNS traversal tools also report failures there. The timeouts we're experiencing would make sense if some cached DNS records were still trying to refer to a failing resolver. And it would happen early in the process as the the top level domains are the next step after the local and root servers. This is where one expects that some of the redundancy would automatically kick in though? And would the local servers be caching records for full hostnames, or just the next step top level domains? If the latter all .cz domains should fail, which they're not. However when I put in the URL of another Czech web hosting company, the report was not the same, suggesting there is some granularity in the records, though it also had a 20% failure through the aforementioned d.ns.nic.cz as well. Don't know enough about DNS to know for sure but the consistent failure of that one .cz resolver across multiple dns traversal tools, the early failure of the traces, and the 'matching' figures of about 20% are interesting.
GratefulFan · Member since
Also forgot to mention that 91.239.200.5 does not show up on any of the blacklist checker tools I tried, which was several.
