Anyone experiencing degraded speed?

[DarkWater]

OMG! can it be ...is that the google logo! o heaven can it be!.....wow!..............Fu*k...my imagination...international still messed...lol

 

[Hiroshige]

Same here.At least you got salty cracks

 

[DarkWater]

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

Reply from 66.102.9.99: bytes=32 time=327ms TTL=232
Reply from 66.102.9.99: bytes=32 time=351ms TTL=232
Reply from 66.102.9.99: bytes=32 time=359ms TTL=232
Reply from 66.102.9.99: bytes=32 time=343ms TTL=232

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

still cant browse

 

[Hiroshige]

You need a program to perform the test above or can I do it...and if so...pray do tell...

 

[DarkWater]

start-run-type cmd-press enter-type ping www.google.co.za and see what happens

 

[DarkWater]

err....nevermind....I want saltycracks!

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

Request timed out.
Request timed out.
Request timed out.

 

[Hiroshige]

Cheers.
I hear that nicotene helps curb the need for saltycracks.I hope it curbs the urge to take this here iCursed modem and smash it into teeny lil pieces to use for some abstract collage artwork later.

 

[DarkWater]

I hear that nicotene helps.

I'm on my second packet....jeez....Iburst...the only thing bursting is my wallet..lol

 

[Hiroshige]

lol
you tried calling.I hear it's a CT town thing and..."the technicians are on it" tee hee.
Various images spring to mind at this point...most of them involving monkeys and such.

 

[Ekhaatvensters]

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

Reply from 66.102.9.99: bytes=32 time=327ms TTL=232
Reply from 66.102.9.99: bytes=32 time=351ms TTL=232
Reply from 66.102.9.99: bytes=32 time=359ms TTL=232
Reply from 66.102.9.99: bytes=32 time=343ms TTL=232

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

still cant browse

Dark, are your pings to google ever this good?

I've seen pings that low in Cape Town a few times before when they were having problems and had to route our international traffic throught other networks.. better ones it seems but then its totally congested or the thing is broken anyway.

Normally CPT international pings sit at around 500ms+

 

[DarkWater]

Dark, are your pings to google ever this good?

I've seen pings that low in Cape Town a few times before when they were having problems and had to route our international traffic throught other networks.. better ones it seems but then its totally congested or the thing is broken anyway.

Normally CPT international pings sit at around 500ms+

Yep...that's my standard pings

 

[Ekhaatvensters]

Weird, I've seen very good connections in Cape Town and they are still limited by international bandwidth... around 500 or high 400's for any US based ping.

 

[Ekhaatvensters]

Well I'm also getting the good international pings now.. and that means only one thing.. international problems. Sites are not loading now It will probably be back in a few minutes then down again, but while it does work on these pings its blazing fast, why can't iBurst organise decent pings for us all of the time?

Pinging google.com [72.14.207.99] with 32 bytes of data:

Reply from 72.14.207.99: bytes=32 time=362ms TTL=237
Reply from 72.14.207.99: bytes=32 time=363ms TTL=237
Reply from 72.14.207.99: bytes=32 time=368ms TTL=237
Reply from 72.14.207.99: bytes=32 time=373ms TTL=237
Reply from 72.14.207.99: bytes=32 time=373ms TTL=237
Reply from 72.14.207.99: bytes=32 time=363ms TTL=237
Reply from 72.14.207.99: bytes=32 time=373ms TTL=237
Reply from 72.14.207.99: bytes=32 time=373ms TTL=237
Reply from 72.14.207.99: bytes=32 time=378ms TTL=237
Reply from 72.14.207.99: bytes=32 time=393ms TTL=237

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

I swear I want to forward these pings to iBUrst and tell them to make it stay like this. Not that they'd do or could do anyhting..

btw ADSL in Cape Town is having similar problems (except the ping is normal for them)

 

[who.is.michael]

They are apparently working on the issue; my speeds are around the 300 kbps mark with frequent timeouts...

Since last Friday when they installed the proxy server in Cape Town the network has gone for a ball of ****, according to them “iBurst” they switched upstream providers….

Pinging 72.14.207.99 with 32 bytes of data:

Reply from 72.14.207.99: bytes=32 time=526ms TTL=240
Reply from 72.14.207.99: bytes=32 time=528ms TTL=240
Reply from 72.14.207.99: bytes=32 time=567ms TTL=240
Reply from 72.14.207.99: bytes=32 time=561ms TTL=240
Reply from 72.14.207.99: bytes=32 time=569ms TTL=240
Reply from 72.14.207.99: bytes=32 time=508ms TTL=240
Reply from 72.14.207.99: bytes=32 time=571ms TTL=240
Reply from 72.14.207.99: bytes=32 time=550ms TTL=240
Request timed out.
Reply from 72.14.207.99: bytes=32 time=567ms TTL=240
Reply from 72.14.207.99: bytes=32 time=546ms TTL=240
Reply from 72.14.207.99: bytes=32 time=534ms TTL=240
Reply from 72.14.207.99: bytes=32 time=557ms TTL=240

Ping statistics for 72.14.207.99:
Packets: Sent = 13, Received = 12, Lost = 1 (7% loss),
Approximate round trip times in milli-seconds:
Minimum = 508ms, Maximum = 571ms, Average = 548ms

EDIT:

Some ISP´s provide a web proxy that, unless you specify otherwise, you are forced to use.
This proxy server is sometimes NOT there for your benefit. It is installed to control bandwidth & traffic for the ISP.
Some ISP´s proxies are not reliable (hence slow web access, DNS failure from time to time).
To bypass the ISP proxy, select an alternative (working) proxy on a port other than 80.
"Fool" the ISP proxy into giving you "fresh" content by appending a random string to the URL (e.g. http://www.bbc.co.uk?tgfd23).

 

[Ekhaatvensters]

Well if that new upstream provider can get my pings to stay like they are now (without breaking the internet) then I'll be happy.

But atm it just looks like the new upstream provider has a lot of problems..

 

[DaEvAnAm]

Yup i have that same issue with pings timing out regularly again. It started again recently. Sigh .

 

[oldBastard]

This from the new Rooihuiskraal Tower:

google.com

Pinging google.com [64.233.167.99] with 32 bytes of data:

Reply from 64.233.167.99: bytes=32 time=331ms TTL=239
Reply from 64.233.167.99: bytes=32 time=372ms TTL=239
Reply from 64.233.167.99: bytes=32 time=352ms TTL=239
Reply from 64.233.167.99: bytes=32 time=357ms TTL=239
Reply from 64.233.167.99: bytes=32 time=357ms TTL=239
Request timed out.
Request timed out.
Reply from 64.233.167.99: bytes=32 time=353ms TTL=239
Reply from 64.233.167.99: bytes=32 time=353ms TTL=239
Reply from 64.233.167.99: bytes=32 time=358ms TTL=239
Reply from 64.233.167.99: bytes=32 time=358ms TTL=239
Reply from 64.233.167.99: bytes=32 time=368ms TTL=239
Request timed out.
Reply from 64.233.167.99: bytes=32 time=363ms TTL=239
Request timed out.
Reply from 64.233.167.99: bytes=32 time=358ms TTL=239
Reply from 64.233.167.99: bytes=32 time=338ms TTL=239
Reply from 64.233.167.99: bytes=32 time=358ms TTL=239
Request timed out.
Reply from 64.233.167.99: bytes=32 time=358ms TTL=239
Reply from 64.233.167.99: bytes=32 time=358ms TTL=239
Reply from 64.233.167.99: bytes=32 time=358ms TTL=239

Ping statistics for 64.233.167.99:
Packets: Sent = 22, Received = 17, Lost = 5 (22% loss),
Approximate round trip times in milli-seconds:
Minimum = 331ms, Maximum = 372ms, Average = 355ms

myadsl.co.za

Pinging myadsl.co.za [196.40.97.13] with 32 bytes of data:

Reply from 196.40.97.13: bytes=32 time=119ms TTL=246
Reply from 196.40.97.13: bytes=32 time=113ms TTL=246
Reply from 196.40.97.13: bytes=32 time=112ms TTL=246
Reply from 196.40.97.13: bytes=32 time=112ms TTL=246
Reply from 196.40.97.13: bytes=32 time=112ms TTL=246
Reply from 196.40.97.13: bytes=32 time=112ms TTL=246
Reply from 196.40.97.13: bytes=32 time=112ms TTL=246
Reply from 196.40.97.13: bytes=32 time=112ms TTL=246
Reply from 196.40.97.13: bytes=32 time=112ms TTL=246
Reply from 196.40.97.13: bytes=32 time=112ms TTL=246
Reply from 196.40.97.13: bytes=32 time=112ms TTL=246
Reply from 196.40.97.13: bytes=32 time=112ms TTL=246
Reply from 196.40.97.13: bytes=32 time=112ms TTL=246
Reply from 196.40.97.13: bytes=32 time=112ms TTL=246
Reply from 196.40.97.13: bytes=32 time=127ms TTL=246
Reply from 196.40.97.13: bytes=32 time=112ms TTL=246
Reply from 196.40.97.13: bytes=32 time=112ms TTL=246
Reply from 196.40.97.13: bytes=32 time=112ms TTL=246

Ping statistics for 196.40.97.13:
Packets: Sent = 18, Received = 18, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 112ms, Maximum = 127ms, Average = 113ms

 

[DaEvAnAm]

Im getting about 20% loss to International and Local. My pings are also unusually high. Speed test revealed im on 56k which is pretty horrible. iBurst = Most expensive 56k on Earth.

 

[Ekhaatvensters]

My international pings are back down to 300's after being "normal" at 500+ for the last day or two.

I'm not sure if they are trying to change to the lower latency permanently or if they just keep messing it up.

Now somehow they come up with this:

Pinging google.co.uk [216.239.59.104] with 32 bytes of dat

Reply from 216.239.59.104: bytes=32 time=298ms TTL=236
Reply from 216.239.59.104: bytes=32 time=297ms TTL=236
Reply from 216.239.59.104: bytes=32 time=287ms TTL=236
Reply from 216.239.59.104: bytes=32 time=300ms TTL=236
Reply from 216.239.59.104: bytes=32 time=329ms TTL=236
Reply from 216.239.59.104: bytes=32 time=302ms TTL=236
Reply from 216.239.59.104: bytes=32 time=302ms TTL=236
Reply from 216.239.59.104: bytes=32 time=300ms TTL=236
Reply from 216.239.59.104: bytes=32 time=310ms TTL=236
Reply from 216.239.59.104: bytes=32 time=304ms TTL=236

Ping statistics for 216.239.59.104:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 287ms, Maximum = 329ms, Average = 302ms

C:\Users\Walter>ping -n 10 myadsl.co.za

Pinging myadsl.co.za [196.40.97.13] with 32 bytes of data:

Reply from 196.40.97.13: bytes=32 time=134ms TTL=242
Reply from 196.40.97.13: bytes=32 time=168ms TTL=242
Reply from 196.40.97.13: bytes=32 time=176ms TTL=242
Reply from 196.40.97.13: bytes=32 time=164ms TTL=242
Reply from 196.40.97.13: bytes=32 time=157ms TTL=242
Reply from 196.40.97.13: bytes=32 time=161ms TTL=242
Reply from 196.40.97.13: bytes=32 time=184ms TTL=242
Reply from 196.40.97.13: bytes=32 time=157ms TTL=242
Reply from 196.40.97.13: bytes=32 time=175ms TTL=242
Reply from 196.40.97.13: bytes=32 time=208ms TTL=242

Ping statistics for 196.40.97.13:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 134ms, Maximum = 208ms, Average = 168ms

 

[DaEvAnAm]

Myadsl.co.za

Pinging myadsl.co.za [196.40.97.12] with 32 bytes of data:

Reply from 196.40.97.12: bytes=32 time=75ms TTL=247
Reply from 196.40.97.12: bytes=32 time=119ms TTL=247
Reply from 196.40.97.12: bytes=32 time=78ms TTL=247
Request timed out.
Request timed out.
Request timed out.
Reply from 196.40.97.12: bytes=32 time=123ms TTL=247
Reply from 196.40.97.12: bytes=32 time=66ms TTL=247
Reply from 196.40.97.12: bytes=32 time=100ms TTL=247
Reply from 196.40.97.12: bytes=32 time=69ms TTL=247
Reply from 196.40.97.12: bytes=32 time=128ms TTL=247
Reply from 196.40.97.12: bytes=32 time=108ms TTL=247
Reply from 196.40.97.12: bytes=32 time=77ms TTL=247
Request timed out.
Reply from 196.40.97.12: bytes=32 time=108ms TTL=247
Reply from 196.40.97.12: bytes=32 time=77ms TTL=247
Request timed out.
Reply from 196.40.97.12: bytes=32 time=118ms TTL=247
Reply from 196.40.97.12: bytes=32 time=77ms TTL=247
Request timed out.

Ping statistics for 196.40.97.12:
Packets: Sent = 20, Received = 14, Lost = 6 (30% loss),
Approximate round trip times in milli-seconds:
Minimum = 66ms, Maximum = 128ms, Average = 94ms

Google.com

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

Reply from 66.102.9.147: bytes=32 time=542ms TTL=237
Reply from 66.102.9.147: bytes=32 time=501ms TTL=237
Reply from 66.102.9.147: bytes=32 time=476ms TTL=237
Reply from 66.102.9.147: bytes=32 time=466ms TTL=237
Reply from 66.102.9.147: bytes=32 time=545ms TTL=237
Reply from 66.102.9.147: bytes=32 time=480ms TTL=237
Reply from 66.102.9.147: bytes=32 time=479ms TTL=237
Reply from 66.102.9.147: bytes=32 time=533ms TTL=237
Reply from 66.102.9.147: bytes=32 time=458ms TTL=237
Reply from 66.102.9.147: bytes=32 time=457ms TTL=237
Request timed out.
Request timed out.
Reply from 66.102.9.147: bytes=32 time=491ms TTL=237
Reply from 66.102.9.147: bytes=32 time=545ms TTL=237
Reply from 66.102.9.147: bytes=32 time=465ms TTL=237
Request timed out.
Reply from 66.102.9.147: bytes=32 time=532ms TTL=237
Request timed out.
Reply from 66.102.9.147: bytes=32 time=466ms TTL=237
Reply from 66.102.9.147: bytes=32 time=466ms TTL=237

Ping statistics for 66.102.9.147:
Packets: Sent = 20, Received = 16, Lost = 4 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 457ms, Maximum = 545ms, Average = 493ms

Horrible timeouts and my line was basically idling.