Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Not technically about programming, so feel free to delete.


Since randomly last night every time I try to visit my browser tries and fails to connect. I've tried various response sites which tell me it's still up. Any idea what the problem could be? I'm using Chrome 5.0 but I'm experiencing the same problem in Safari 5.0 and Firefox 3.6.8. So far this is the only site I'm having the problem with.

share|improve this question

migrated from Aug 23 '10 at 18:20

This question came from our site for professional and enthusiast programmers.

Go down the line:

  • Since it's a problem between browsers, it's certainly not a cookie. So that's not it.
  • It could be a DNS cache thing or an IP/DHCP thing. Try rebooting your computer and seeing if that fixes anything.
  • If not, it may also be a network or ISP thing. Go to the library and see if it's working there.
  • If none of those work, try livebooting an Ubuntu install disc to see if it's an OS thing.
  • Maybe, if you're desperate, install Opera and see if it works there.
share|improve this answer
Might wanna add onto that list. Kind of like going to the library, without the going or the library. :p – ssube Aug 23 '10 at 18:28
thanks for your replies. updates: - doesn't work in opera - downforeveryone says it's up: that's what i meant by the rather vague term "response site". - i can get through if i use a proxy – Sebastian Aug 23 '10 at 18:35
If you can use a proxy, it's either being blocked or something's wrong with your DNS. Try running ping from the commandline and post the results here. – digitxp Aug 23 '10 at 18:43
Ping has started ... PING ( 56 data bytes --- ping statistics --- 10 packets transmitted, 0 packets received, 100% packet loss – Sebastian Aug 23 '10 at 18:46
I got the same IP address when I pinged them, so it's definitely not a DNS problem. Now, try running tracert and posting the results. – digitxp Aug 23 '10 at 20:55

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .