iburst playing up AGAIN!

[jamieb]

More unreliablility for the folks at iBurst. I almost had a straight five days without any problems... was beginning to think they were getting their act together. sadly this is not the case.

ping www.google.com

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

Reply from 66.249.85.104: bytes=32 time=525ms TTL=237
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 66.249.85.104:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 525ms, Maximum = 525ms, Average = 525ms

 

[w1z4rd]

not my side, still running lank well

 

[JasonH]

same problem here but i can access google.com fine

 

[fergus]

I've been running a ping job to www.iburst.co.za the whole day and this is what I get:

Ping statistics for 196.30.31.120:
Packets: Sent = 143747, Received = 140741, Lost = 3006 (2% loss),
Reply from 196.30.31.120: bytes=32 time=80ms TTL=122
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 4102ms, Average = 159ms

Only some of the lost packets come from disconnections. Every now and then the connection will just go dead for a few seconds and then come alive again. Its definitely not anything to do with signal because I'm less than 100 meters from the tower but it might be something with the radio link from the tower to the isp.

 

[JasonH]

Dang, It's fixed, I just swaped to Ethernet and it works :weirD:

 

[JasonH]

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

Reply from 66.249.85.104: bytes=32 time=439ms TTL=238
Reply from 66.249.85.104: bytes=32 time=374ms TTL=238
Reply from 66.249.85.104: bytes=32 time=432ms TTL=238
Reply from 66.249.85.104: bytes=32 time=346ms TTL=238

Ping statistics for 66.249.85.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 346ms, Maximum = 439ms, Average = 397ms