Sat-3 Maintenance

[diegoa]

I mean portion of the sat-3 system

 

[LazyLion]

OK, it's working now... must have just been a glitch in the Matrix.

 

[techead]

That's really annoying...Who is your ISP?

Can you post a speedtest result from the London server? And maybe New York? Just out of interest...

sorry mate Im at the office now, will do so when I get back gome after work. Im with Axxess

 

[jannier]

Hooray!!! SAT-3 seems back up and all my latency's are back to normal again.

Well done!!

 

[Dames]

I'm still pinging at over 800ms to London and only getting about 2.6Mbps...CT server is still ping 12ms and 3.4Mbps though.

 

[PallBearer]

Dear Network Notice Subscriber

The following notice has been UPDATED.

TIME: 12 Feb 2010 1:12:41 PM
ADDITIONAL: All restorable traffic has been finally normalized and back onto SAT3. We will closely monitor for stability.

 

[Blackhand]

Confirmed, latency is significantly better.

I just tested with a traceroute as I'm at work, will test out game performance when I get home.

 

[g-d-zilla]

IS and Afrihost had SAT-3 problems a few days ago. I was incensed that my normally stable internet connection was down. Then the Assvoelkop Telkom exchange was off Thursday morning, and they are so [expletive] indifferent, couldn't give a [expletive] damn. I protested as only I can do (you think Isabel Jones was bad?) and within an hour it was up and running, and has been stable since. But I heard from Afrihost that the SAT-3 (whatever that's supposed to mean) was in fact "down". Nou ja!

 

[g-d-zilla]

What is wrong with this?

C:\Documents and Settings\sounds>tracert www.afrihost.com

Tracing route to www.afrihost.com [196.38.88.28]
over a maximum of 30 hops:

1 <10 ms <10 ms <10 ms Router [10.0.0.2]
2 * * * Request timed out.
3 29 ms 29 ms 29 ms cdsl1-rba-vl2253.ip.isnet.net [196.38.73.181]
4 24 ms 29 ms 29 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
5 23 ms 30 ms 29 ms core6a-rba-gi1-0-0.ip.isnet.net [168.209.1.165]

6 26 ms 28 ms 29 ms core2a-bry-gi0-0-2-216.ip.isnet.net [168.209.100
.201]
7 25 ms 29 ms 28 ms csw1-b-jup-bry-gi3-2.ip.isnet.net [168.209.218.2
1]
8 26 ms 30 ms 29 ms 196.34.134.105
9 31 ms 37 ms 28 ms gw.aserv.co.za [196.33.227.1]
10 29 ms 28 ms 33 ms www.afrihost.com [196.38.88.28]

Trace complete.

Why is the 2nd hop always * * * Request timed out?

 

[Splice]

Ping request could be blocked on that router which the hop was intended to go to