SAIX International problems

D

Dennis

Well-Known Member
Joined
Aug 10, 2006
Messages
155
Reaction score
0
Location
Pietermaritzburg
Any one else having problems with int ????


Pinging www.l.google.com [66.249.85.99] with 32 bytes of data:

Request timed out.
Reply from 66.249.85.99: bytes=32 time=376ms TTL=244
Reply from 66.249.85.99: bytes=32 time=376ms TTL=244
Reply from 66.249.85.99: bytes=32 time=377ms TTL=244
Reply from 66.249.85.99: bytes=32 time=384ms TTL=244
Reply from 66.249.85.99: bytes=32 time=394ms TTL=244
Reply from 66.249.85.99: bytes=32 time=414ms TTL=244
Reply from 66.249.85.99: bytes=32 time=434ms TTL=244
Reply from 66.249.85.99: bytes=32 time=440ms TTL=244
Reply from 66.249.85.99: bytes=32 time=461ms TTL=244
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 66.249.85.99: bytes=32 time=377ms TTL=244
Reply from 66.249.85.99: bytes=32 time=385ms TTL=244
Reply from 66.249.85.99: bytes=32 time=401ms TTL=244
Reply from 66.249.85.99: bytes=32 time=434ms TTL=244
Reply from 66.249.85.99: bytes=32 time=454ms TTL=244
Reply from 66.249.85.99: bytes=32 time=455ms TTL=244
Reply from 66.249.85.99: bytes=32 time=428ms TTL=244
Reply from 66.249.85.99: bytes=32 time=435ms TTL=244
Reply from 66.249.85.99: bytes=32 time=455ms TTL=244
Request timed out.
Reply from 66.249.85.99: bytes=32 time=377ms TTL=244
Reply from 66.249.85.99: bytes=32 time=377ms TTL=244
Reply from 66.249.85.99: bytes=32 time=377ms TTL=244
Reply from 66.249.85.99: bytes=32 time=404ms TTL=244
Reply from 66.249.85.99: bytes=32 time=447ms TTL=244


Local is fine


Pinging games.saix.net [198.54.202.4] with 32 bytes of data:

Reply from 198.54.202.4: bytes=32 time=43ms TTL=250
Reply from 198.54.202.4: bytes=32 time=44ms TTL=250
Reply from 198.54.202.4: bytes=32 time=44ms TTL=250
Reply from 198.54.202.4: bytes=32 time=46ms TTL=250
Reply from 198.54.202.4: bytes=32 time=45ms TTL=250
Reply from 198.54.202.4: bytes=32 time=45ms TTL=250
Reply from 198.54.202.4: bytes=32 time=45ms TTL=250
Reply from 198.54.202.4: bytes=32 time=45ms TTL=250
Reply from 198.54.202.4: bytes=32 time=45ms TTL=250
Reply from 198.54.202.4: bytes=32 time=46ms TTL=250
Reply from 198.54.202.4: bytes=32 time=44ms TTL=250
Reply from 198.54.202.4: bytes=32 time=45ms TTL=250
Reply from 198.54.202.4: bytes=32 time=45ms TTL=250
Reply from 198.54.202.4: bytes=32 time=45ms TTL=250
Reply from 198.54.202.4: bytes=32 time=45ms TTL=250
Reply from 198.54.202.4: bytes=32 time=45ms TTL=250
Reply from 198.54.202.4: bytes=32 time=46ms TTL=250
Reply from 198.54.202.4: bytes=32 time=46ms TTL=250
Reply from 198.54.202.4: bytes=32 time=46ms TTL=250
Reply from 198.54.202.4: bytes=32 time=47ms TTL=250
Reply from 198.54.202.4: bytes=32 time=44ms TTL=250
Reply from 198.54.202.4: bytes=32 time=44ms TTL=250
Reply from 198.54.202.4: bytes=32 time=43ms TTL=250
Reply from 198.54.202.4: bytes=32 time=45ms TTL=250
Reply from 198.54.202.4: bytes=32 time=47ms TTL=250
Reply from 198.54.202.4: bytes=32 time=46ms TTL=250
Reply from 198.54.202.4: bytes=32 time=46ms TTL=250

Thanks Dennis
 
Mine's been screwing around for the past 2 hours. Not just international but everywhere... I've been downloading Fedora Core 5 and it was stable until a few hours ago. Now my IRC's going down, FTP transfer is up the creek and no IM'ing.

(Downloading from ftp.is.co.za and international sites. The graph was stable and now it's spiking all over the place, nothing stable.)

Something is definitely wrong.
 
i get dc every 5 mins while playing WoW.... not to mention my ping jumps up to 15000 before it happens |-)
 
SAIX Network Notices

Severity 1 Network Faults latest
Call Reference ID : STT000000004994
Failure Type : Network Failure
Problem Description : Link down New York and Hong Kong
Time Down : 21 Aug 2006, 00:40:00
Impact : Clients will experience slow responses to International Sites
Site : New York
Services Affected : International
Updates : 20 Aug 2006, 00:56:44 zumanm1
Our Techs are investigating.
20 Aug 2006, 04:08:46 zumanm1
Overseas Technicians to investigate.
Cause of Failure : Unkown
Status : New

http://www.axxess.co.za/network.php
 
well it seems to be sorted out

Pinging www.l.google.com [66.249.85.99] with 32 bytes of data:

Reply from 66.249.85.99: bytes=32 time=415ms TTL=243
Reply from 66.249.85.99: bytes=32 time=415ms TTL=243
Reply from 66.249.85.99: bytes=32 time=414ms TTL=243
Reply from 66.249.85.99: bytes=32 time=416ms TTL=243
Reply from 66.249.85.99: bytes=32 time=415ms TTL=243
Reply from 66.249.85.99: bytes=32 time=416ms TTL=243
Reply from 66.249.85.99: bytes=32 time=414ms TTL=243
Reply from 66.249.85.99: bytes=32 time=415ms TTL=243
Reply from 66.249.85.99: bytes=32 time=424ms TTL=243
Reply from 66.249.85.99: bytes=32 time=418ms TTL=243
Reply from 66.249.85.99: bytes=32 time=415ms TTL=243
Reply from 66.249.85.99: bytes=32 time=417ms TTL=243
Reply from 66.249.85.99: bytes=32 time=419ms TTL=243
Reply from 66.249.85.99: bytes=32 time=415ms TTL=243
Reply from 66.249.85.99: bytes=32 time=414ms TTL=243
Reply from 66.249.85.99: bytes=32 time=414ms TTL=243
Reply from 66.249.85.99: bytes=32 time=413ms TTL=243
Reply from 66.249.85.99: bytes=32 time=419ms TTL=243
Reply from 66.249.85.99: bytes=32 time=413ms TTL=243
Reply from 66.249.85.99: bytes=32 time=417ms TTL=243
Reply from 66.249.85.99: bytes=32 time=413ms TTL=243
Reply from 66.249.85.99: bytes=32 time=415ms TTL=243
Reply from 66.249.85.99: bytes=32 time=414ms TTL=243
Reply from 66.249.85.99: bytes=32 time=413ms TTL=243
Reply from 66.249.85.99: bytes=32 time=412ms TTL=243
Reply from 66.249.85.99: bytes=32 time=415ms TTL=243
Reply from 66.249.85.99: bytes=32 time=417ms TTL=243
Reply from 66.249.85.99: bytes=32 time=415ms TTL=243
Reply from 66.249.85.99: bytes=32 time=417ms TTL=243
Reply from 66.249.85.99: bytes=32 time=418ms TTL=243
Reply from 66.249.85.99: bytes=32 time=415ms TTL=243
Reply from 66.249.85.99: bytes=32 time=414ms TTL=243
Reply from 66.249.85.99: bytes=32 time=413ms TTL=243
Reply from 66.249.85.99: bytes=32 time=413ms TTL=243
Reply from 66.249.85.99: bytes=32 time=413ms TTL=243
Reply from 66.249.85.99: bytes=32 time=418ms TTL=243
Reply from 66.249.85.99: bytes=32 time=412ms TTL=243

Nice and steady aswell
Cheers Dennis
 
But if the problem had been local, they would still be looking at blaming it on some1 before fixing it...
 
Not even a thank you to the Axxess dude for posting that error log?
Shame on you guys :mad:
 
axxess said:
Severity 1 Network Faults latest
Call Reference ID : STT000000004994
Failure Type : Network Failure
Problem Description : Link down New York and Hong Kong
Time Down : 21 Aug 2006, 00:40:00
Impact : Clients will experience slow responses to International Sites
Site : New York
Services Affected : International
Updates : 20 Aug 2006, 00:56:44 zumanm1
Our Techs are investigating.
20 Aug 2006, 04:08:46 zumanm1
Overseas Technicians to investigate.
Cause of Failure : Unkown
Status : New

http://www.axxess.co.za/network.php
Click to expand...

Thanks Axxess
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X