Cold Syrup Thru Speed
June 2nd 2008 10:08
Jon, are some of your servers down? I am having to wait several minutes (not seconds) to open a post, to comment or upload a new post. This is the worst it's ever been.
Everything other site I visit loads lightening fast ~ this is been annoying. Is a main line or satellite link down?
Raven
Everything other site I visit loads lightening fast ~ this is been annoying. Is a main line or satellite link down?
Raven
| 39 |
| Vote |
Subscribe to this blog
Comment by jon
Orble News
Urban Hint
Blog Adviser
Jon's Bookmarks
Debate Battle
Orblepedia
Orble Notes
Sydney WeekendNotes
Comment by tlcorbin
Coffee Quip
A Global Citizen
Paranormal Paranormal
Is Why
Alaska Chronicle
Maybe the backbone is overloaded? I have a 7meg connection on a new fiber optics system, and that has me wondering about the one of the other trunk lines.
Australia and Alaska aren't exactly next door neighbors....I wonder how hops it takes to get hooked up???
I doubt that anything can be done about it, but thought you ought to know.
Comment by Ahmed
techy.Bytes
Video Gamer Kids
Little Green Foosballs
PolyKicks
Qwerk
Cinema Three
Well the Orble servers are apparently in the US so that shouldn't be an issue. It could be your ISP is bottle knecked at a certain point or maybe ithey're playing a game with net neutrality laws?
Comment by tlcorbin
Coffee Quip
A Global Citizen
Paranormal Paranormal
Is Why
Alaska Chronicle
Comment by tlcorbin
Coffee Quip
A Global Citizen
Paranormal Paranormal
Is Why
Alaska Chronicle
Pinging orble.com [66.39.87.194] with 32 bytes of data:
Reply from 66.39.87.194: bytes=32 time=107ms TTL=50
Reply from 66.39.87.194: bytes=32 time=108ms TTL=50
Reply from 66.39.87.194: bytes=32 time=109ms TTL=50
Reply from 66.39.87.194: bytes=32 time=106ms TTL=50
Ping statistics for 66.39.87.194:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 106ms, Maximum = 109ms, Average = 107ms
C:\>tracert www.orble.com
Tracing route to orble.com [66.39.87.194]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 7 ms 6 ms 6 ms 145-138-165-209.gci.net [209.165.138.145]
4 40 ms 42 ms 41 ms 66-251-223-66.gci.net [66.223.251.66]
5 28 ms 29 ms 28 ms 169-129-165-209.gci.net [209.165.129.169]
6 29 ms 29 ms 28 ms 106-129-165-209.gci.net [209.165.129.106]
7 29 ms 31 ms 29 ms Really Long Link [144.224.113.85]
8 31 ms 28 ms 28 ms Really Long Link [144.232.6.121]
9 84 ms 85 ms 86 ms sl-bb25-chi-5-0.sprintlink.net [144.232.20.84]
10 74 ms 73 ms 73 ms Really Long Link [144.232.26.82]
11 97 ms 100 ms 97 ms sl-bb25-nyc-5-0.sprintlink.net [144.232.9.157]
12 144 ms 118 ms 118 ms 144.232.13.146
13 118 ms 117 ms 136 ms 208.30.223.38
14 * * * Request timed out.
15 107 ms 109 ms 107 ms orble.com [66.39.87.194]
Trace complete.
Jon, I have had to wait long enough for connection that I could make a pot of coffee while my puter slammed away at your servers: does this info help?