International Dead

google is back. was not only google, but also yahoo.com and a number of other .com sites
 
I must be on a different planet then since gmail has been working fine all day and still is.:rolleyes:
 
We back on +-350ms pings international again. They just keep switching between the two...

Too bad they changed it in the middle of a game :( Got dropped.
 
I'm fed up with this crap. Gonna put some effort into getting ADSL now.
One minute everthing is fine and running smoothly, and the next it just randomly disconnects. I dont want the beste, fastest connection. I want a reliable connection.
 
who.is.michael said:
Packet loss has gone through the roof and speeds down to the 100's kbps again...
Click to expand...

Sorry to hear your connection has gone belly up again, but mine is still flying along both local and international which makes me think your base station could be the problem. :confused: :(
 
Major Packet Loss

Hi Guys,

Wondering if anybody can explain. I have been experiencing major packet loss for any international traffic this whole week. Local browsing works 100%

Pinging google.com over 150 packet at 32 byte it has 17% packet loss.

Is it just a Durban problem or what?:eek:

Here's a tracert to google.com

Tracing route to google.com [64.233.187.99]

over a maximum of 30 hops:



1 <1 ms <1 ms <1 ms 192.168.0.1

2 90 ms 100 ms 95 ms wbs-196-2-100-1.wbs.co.za [196.2.100.1]

3 138 ms 64 ms 104 ms 192.168.0.97

4 120 ms 150 ms 179 ms 192.168.0.101

5 219 ms 199 ms 174 ms 196.38.243.125

6 138 ms 129 ms 109 ms 168.209.86.122

7 136 ms 114 ms 109 ms 168.209.86.121

8 135 ms 100 ms 109 ms core1b-rba-gi0-1.rtr.isnet.net [196.26.0.10]

9 285 ms 264 ms 274 ms 168.209.160.253

10 * * * Request timed out.

11 * * 302 ms 195.66.226.125

12 287 ms * 286 ms 66.249.95.130

13 426 ms 350 ms 364 ms 72.14.236.216

14 539 ms * 386 ms 66.249.94.235

15 415 ms 389 ms 389 ms 72.14.238.138

16 389 ms 369 ms 389 ms 72.14.239.23

17 403 ms * 396 ms 216.239.49.222

18 * 391 ms 374 ms google.com [64.233.187.99]



Trace complete.
 
To me the problem looks like iBurst has changed to using IS for international routing to Europe instead of Verizon. We all know how 'spanked' IS's network is these days.
 
It affects me... am trying to update a Linux box... getting FARKING DIAL-UP SPEEDS :mad: :mad: :mad:
 
I also notice they are now switched onto Internet Solutions.. whom in the opinion of a mate of mine... "they are crap"

So this means iBurst is going to be crap from now on....
Time to get ADSL for sure....
 
None of this makes any sense since mine is still working fine, unless CT is on a different routing system.:confused:
 
Well... I'll tell you what makes sense.. I want to bomb iBurst and IS's offices right now.. they fscked up my Linux install on a customer's machine I was busy getting updates in and I had to start ALL OVER FROM SCRATCH.. even my post to THIS FORUM was lost... it hung on this page!!! :mad: :mad: :mad: :mad: :mad:
 
JTech, That sounds similar to the way it was in CT last week so I have a good idea of how you feel about it.
 
Pinging www.l.google.com [66.102.9.104] with 32 bytes of data:

Reply from 66.102.9.104: bytes=32 time=455ms TTL=238
Reply from 66.102.9.104: bytes=32 time=449ms TTL=238
Reply from 66.102.9.104: bytes=32 time=448ms TTL=238
Reply from 66.102.9.104: bytes=32 time=452ms TTL=238

Ping statistics for 66.102.9.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 448ms, Maximum = 455ms, Average = 451ms

WTF....happend to 275ms :confused: :mad:
 
Yet mine have gone down..

Reply from 72.14.207.99: bytes=32 time=355ms TTL=237
Reply from 72.14.207.99: bytes=32 time=379ms TTL=237
Reply from 72.14.207.99: bytes=32 time=379ms TTL=237
Reply from 72.14.207.99: bytes=32 time=375ms TTL=237

Ping statistics for 72.14.207.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 355ms, Maximum = 379ms, Average = 372ms

No idea what's going on now, except that its good in Cape Town, I love the low international pings :)
 
Pinging www.l.google.com [64.233.189.104] with 32 bytes of data:

Reply from 64.233.189.104: bytes=32 time=361ms TTL=241
Reply from 64.233.189.104: bytes=32 time=361ms TTL=241
Reply from 64.233.189.104: bytes=32 time=362ms TTL=241
Reply from 64.233.189.104: bytes=32 time=362ms TTL=241

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

It's a bit better...but not like it use to be
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X