It, most likely, has to do with your provider and who they peer with for internet access, and how it's routed.
From a machine that doesn't work you can run from a command prompt:
Start -> Run -> cmd
Type:
Code: |
C:> tracert community.livejournal.com
|
It'll give some output on how the connection is routed to the destination, but if there are issues where it's taking a long time (like over 100ms between hops), or even just timing out, marked by a '
*' (asterisks) in the time field, then that can easily cause connection timeouts.
Note that a '
*' doesn't necessarily mean a timeout, as a router
can block the timing mechanism used by tracert to determine the time... but most of the major ISP Backbone routers don't block it by practice.
If there's a major hiccup somewhere, not much you can do about it unfortunately until they either route around it, or replace the bad route. :/