*READ FIRST* iBurst Network Status & Issues (DNS, Throughput and Latency)

internet was crappy and intermittent from yesterday afternoon till this afternoon. Then it came right. probably just a problem that I am causing ;)
 
Gekco said:
Issues with sites unable to load or loading partially. Bellville, Western Cape.
Click to expand...
had the same issue friday and saturday.

on a lighter note, my internet was off today from this morning to about an hour ago. its back up now, but downloads arent completing. probably my fault ;)
 
r00igev@@r said:
Have ask the NOC to investigate. Any particular sites a problem?
Click to expand...

It's a bit better now, after I restarted my router, but earlier I was experiencing it on most international and local sites including MyBroadband.
Currently local seems fairly ok, but the international sites remain somewhat problematic.
Google+ does not load most of the images (https://plus.google.com/).
Some sites do not render at all and browsing is still painfully slow on international.

Thx
 
Gekco said:
It's a bit better now, after I restarted my router, but earlier I was experiencing it on most international and local sites including MyBroadband.
Currently local seems fairly ok, but the international sites remain somewhat problematic.
Google+ does not load most of the images (https://plus.google.com/).
Some sites do not render at all and browsing is still painfully slow on international.

Thx
Click to expand...

Investigating connectivity issues in Johannesburg.
 
just got back from a great weekend up in Joburg where I was using a Telkom DO Broadband 384kb connection and I managed to run TWO sessions of Starcraft over the line at the same time with 0 problem.

Wow what bliss.

Now ive come back to Cape Town again (Gardens Tower), and oh boy, back to my crappy, laggy experience with iBurst.....dropped for the first time ever from a game. Worst ever lag experienced tonight. This...is....a...joke
 
yo Ronald can you check what's wrong in my area (welties)
I am getting horrible connection speed, below 200Kbps I am used to 700 and above


Download Speed: 192 kbps (24 KB/sec transfer rate)
Upload Speed: 131 kbps (16.4 KB/sec transfer rate)
Latency: 180 ms
 
Well, weeks later, my lag issues continue. Ronald, is the below normal? I just endlessly pinged www.jolt.co.uk and my responses varied greatly. This seem to be my feeling when gaming. Starts out ok, but as time progresses my connection cant keep up, and eventually it bombs out (or just becomes ridiculously unplayable). Are you 100% sure there is nothing wrong with the Gardens (Cape Town) tower (which I am directly under) or any of the kit in the area? I have already logged a call with Advanced Support who should hopefully call me on Monday, and im going to try and find the cable to connect the modem to my pc directly and eliminate my router from the equation.


Pinging jolt.co.uk [84.234.17.86] with 32 bytes of data:
Reply from 84.234.17.86: bytes=32 time=251ms TTL=117
Reply from 84.234.17.86: bytes=32 time=707ms TTL=117
Reply from 84.234.17.86: bytes=32 time=249ms TTL=117
Reply from 84.234.17.86: bytes=32 time=270ms TTL=117
Reply from 84.234.17.86: bytes=32 time=386ms TTL=117
Reply from 84.234.17.86: bytes=32 time=853ms TTL=117
Reply from 84.234.17.86: bytes=32 time=265ms TTL=117
Reply from 84.234.17.86: bytes=32 time=291ms TTL=117
Reply from 84.234.17.86: bytes=32 time=1133ms TTL=117
Reply from 84.234.17.86: bytes=32 time=1153ms TTL=117
Reply from 84.234.17.86: bytes=32 time=269ms TTL=117
Reply from 84.234.17.86: bytes=32 time=276ms TTL=117
Reply from 84.234.17.86: bytes=32 time=273ms TTL=117
Reply from 84.234.17.86: bytes=32 time=295ms TTL=117
Reply from 84.234.17.86: bytes=32 time=267ms TTL=117
Reply from 84.234.17.86: bytes=32 time=488ms TTL=117
Reply from 84.234.17.86: bytes=32 time=375ms TTL=117
Reply from 84.234.17.86: bytes=32 time=235ms TTL=117
Reply from 84.234.17.86: bytes=32 time=471ms TTL=117
Reply from 84.234.17.86: bytes=32 time=273ms TTL=117
Reply from 84.234.17.86: bytes=32 time=294ms TTL=117
Reply from 84.234.17.86: bytes=32 time=996ms TTL=117
Reply from 84.234.17.86: bytes=32 time=243ms TTL=117
Reply from 84.234.17.86: bytes=32 time=274ms TTL=117
Reply from 84.234.17.86: bytes=32 time=286ms TTL=117
Reply from 84.234.17.86: bytes=32 time=273ms TTL=117
Reply from 84.234.17.86: bytes=32 time=930ms TTL=117
Reply from 84.234.17.86: bytes=32 time=266ms TTL=117
Reply from 84.234.17.86: bytes=32 time=272ms TTL=117
Reply from 84.234.17.86: bytes=32 time=1103ms TTL=117
Reply from 84.234.17.86: bytes=32 time=749ms TTL=117
Reply from 84.234.17.86: bytes=32 time=278ms TTL=117
Reply from 84.234.17.86: bytes=32 time=299ms TTL=117
Reply from 84.234.17.86: bytes=32 time=276ms TTL=117
Reply from 84.234.17.86: bytes=32 time=268ms TTL=117
Reply from 84.234.17.86: bytes=32 time=279ms TTL=117
Reply from 84.234.17.86: bytes=32 time=291ms TTL=117
Reply from 84.234.17.86: bytes=32 time=262ms TTL=117
Reply from 84.234.17.86: bytes=32 time=253ms TTL=117
Reply from 84.234.17.86: bytes=32 time=271ms TTL=117
Reply from 84.234.17.86: bytes=32 time=272ms TTL=117
Reply from 84.234.17.86: bytes=32 time=369ms TTL=117
Reply from 84.234.17.86: bytes=32 time=280ms TTL=117
Reply from 84.234.17.86: bytes=32 time=807ms TTL=117
Reply from 84.234.17.86: bytes=32 time=263ms TTL=117
Reply from 84.234.17.86: bytes=32 time=424ms TTL=117
Reply from 84.234.17.86: bytes=32 time=331ms TTL=117
Reply from 84.234.17.86: bytes=32 time=283ms TTL=117
Reply from 84.234.17.86: bytes=32 time=389ms TTL=117
Reply from 84.234.17.86: bytes=32 time=270ms TTL=117
Reply from 84.234.17.86: bytes=32 time=302ms TTL=117
Reply from 84.234.17.86: bytes=32 time=283ms TTL=117
Reply from 84.234.17.86: bytes=32 time=295ms TTL=117
Reply from 84.234.17.86: bytes=32 time=272ms TTL=117

And

Reply from 84.234.17.86: bytes=32 time=332ms TTL=117
Reply from 84.234.17.86: bytes=32 time=531ms TTL=117
Reply from 84.234.17.86: bytes=32 time=260ms TTL=117
Reply from 84.234.17.86: bytes=32 time=254ms TTL=117
Reply from 84.234.17.86: bytes=32 time=298ms TTL=117
Reply from 84.234.17.86: bytes=32 time=257ms TTL=117
Reply from 84.234.17.86: bytes=32 time=247ms TTL=117
Reply from 84.234.17.86: bytes=32 time=238ms TTL=117
Request timed out.
Reply from 84.234.17.86: bytes=32 time=426ms TTL=117
Reply from 84.234.17.86: bytes=32 time=1340ms TTL=117
Request timed out.
Reply from 84.234.17.86: bytes=32 time=1144ms TTL=117
Reply from 84.234.17.86: bytes=32 time=1121ms TTL=117
Reply from 84.234.17.86: bytes=32 time=1738ms TTL=117
Reply from 84.234.17.86: bytes=32 time=1188ms TTL=117
Request timed out.
Request timed out.
Reply from 84.234.17.86: bytes=32 time=1431ms TTL=117
Reply from 84.234.17.86: bytes=32 time=654ms TTL=117
Reply from 84.234.17.86: bytes=32 time=2423ms TTL=117
Reply from 84.234.17.86: bytes=32 time=559ms TTL=117
Reply from 84.234.17.86: bytes=32 time=944ms TTL=117
Reply from 84.234.17.86: bytes=32 time=2584ms TTL=117
Reply from 84.234.17.86: bytes=32 time=284ms TTL=117
Request timed out.
Reply from 84.234.17.86: bytes=32 time=427ms TTL=117
Reply from 84.234.17.86: bytes=32 time=251ms TTL=117
Reply from 84.234.17.86: bytes=32 time=1029ms TTL=117
Reply from 84.234.17.86: bytes=32 time=1574ms TTL=117
Reply from 84.234.17.86: bytes=32 time=245ms TTL=117


I have checked that there are 0 other devices on the network at the time of doing this ping, and that on my PC, there is no other traffic on the nic. Last time i played with no noticeable lag was last Sunday night. You've also told me previously that weather was to blame, and tomorrow is lined up to be a near perfect day in the Cape, so you can be sure I will be testing this very carefully.
 
Last edited:
Markd said:
Well, weeks later, my lag issues continue. Ronald, is the below normal? I just endlessly pinged www.jolt.co.uk and my responses varied greatly. This seem to be my feeling when gaming. Starts out ok, but as time progresses my connection cant keep up, and eventually it bombs out (or just becomes ridiculously unplayable). Are you 100% sure there is nothing wrong with the Gardens (Cape Town) tower (which I am directly under) or any of the kit in the area? I have already logged a call with Advanced Support who should hopefully call me on Monday, and im going to try and find the cable to connect the modem to my pc directly and eliminate my router from the equation.


Pinging jolt.co.uk [84.234.17.86] with 32 bytes of data:
Reply from 84.234.17.86: bytes=32 time=251ms TTL=117
Reply from 84.234.17.86: bytes=32 time=707ms TTL=117
Reply from 84.234.17.86: bytes=32 time=249ms TTL=117
Reply from 84.234.17.86: bytes=32 time=270ms TTL=117
Reply from 84.234.17.86: bytes=32 time=386ms TTL=117
Reply from 84.234.17.86: bytes=32 time=853ms TTL=117
Reply from 84.234.17.86: bytes=32 time=265ms TTL=117
Reply from 84.234.17.86: bytes=32 time=291ms TTL=117
Reply from 84.234.17.86: bytes=32 time=1133ms TTL=117
Reply from 84.234.17.86: bytes=32 time=1153ms TTL=117
Reply from 84.234.17.86: bytes=32 time=269ms TTL=117
Reply from 84.234.17.86: bytes=32 time=276ms TTL=117
Reply from 84.234.17.86: bytes=32 time=273ms TTL=117
Reply from 84.234.17.86: bytes=32 time=295ms TTL=117
Reply from 84.234.17.86: bytes=32 time=267ms TTL=117
Reply from 84.234.17.86: bytes=32 time=488ms TTL=117
Reply from 84.234.17.86: bytes=32 time=375ms TTL=117
Reply from 84.234.17.86: bytes=32 time=235ms TTL=117
Reply from 84.234.17.86: bytes=32 time=471ms TTL=117
Reply from 84.234.17.86: bytes=32 time=273ms TTL=117
Reply from 84.234.17.86: bytes=32 time=294ms TTL=117
Reply from 84.234.17.86: bytes=32 time=996ms TTL=117
Reply from 84.234.17.86: bytes=32 time=243ms TTL=117
Reply from 84.234.17.86: bytes=32 time=274ms TTL=117
Reply from 84.234.17.86: bytes=32 time=286ms TTL=117
Reply from 84.234.17.86: bytes=32 time=273ms TTL=117
Reply from 84.234.17.86: bytes=32 time=930ms TTL=117
Reply from 84.234.17.86: bytes=32 time=266ms TTL=117
Reply from 84.234.17.86: bytes=32 time=272ms TTL=117
Reply from 84.234.17.86: bytes=32 time=1103ms TTL=117
Reply from 84.234.17.86: bytes=32 time=749ms TTL=117
Reply from 84.234.17.86: bytes=32 time=278ms TTL=117
Reply from 84.234.17.86: bytes=32 time=299ms TTL=117
Reply from 84.234.17.86: bytes=32 time=276ms TTL=117
Reply from 84.234.17.86: bytes=32 time=268ms TTL=117
Reply from 84.234.17.86: bytes=32 time=279ms TTL=117
Reply from 84.234.17.86: bytes=32 time=291ms TTL=117
Reply from 84.234.17.86: bytes=32 time=262ms TTL=117
Reply from 84.234.17.86: bytes=32 time=253ms TTL=117
Reply from 84.234.17.86: bytes=32 time=271ms TTL=117
Reply from 84.234.17.86: bytes=32 time=272ms TTL=117
Reply from 84.234.17.86: bytes=32 time=369ms TTL=117
Reply from 84.234.17.86: bytes=32 time=280ms TTL=117
Reply from 84.234.17.86: bytes=32 time=807ms TTL=117
Reply from 84.234.17.86: bytes=32 time=263ms TTL=117
Reply from 84.234.17.86: bytes=32 time=424ms TTL=117
Reply from 84.234.17.86: bytes=32 time=331ms TTL=117
Reply from 84.234.17.86: bytes=32 time=283ms TTL=117
Reply from 84.234.17.86: bytes=32 time=389ms TTL=117
Reply from 84.234.17.86: bytes=32 time=270ms TTL=117
Reply from 84.234.17.86: bytes=32 time=302ms TTL=117
Reply from 84.234.17.86: bytes=32 time=283ms TTL=117
Reply from 84.234.17.86: bytes=32 time=295ms TTL=117
Reply from 84.234.17.86: bytes=32 time=272ms TTL=117

And

Reply from 84.234.17.86: bytes=32 time=332ms TTL=117
Reply from 84.234.17.86: bytes=32 time=531ms TTL=117
Reply from 84.234.17.86: bytes=32 time=260ms TTL=117
Reply from 84.234.17.86: bytes=32 time=254ms TTL=117
Reply from 84.234.17.86: bytes=32 time=298ms TTL=117
Reply from 84.234.17.86: bytes=32 time=257ms TTL=117
Reply from 84.234.17.86: bytes=32 time=247ms TTL=117
Reply from 84.234.17.86: bytes=32 time=238ms TTL=117
Request timed out.
Reply from 84.234.17.86: bytes=32 time=426ms TTL=117
Reply from 84.234.17.86: bytes=32 time=1340ms TTL=117
Request timed out.
Reply from 84.234.17.86: bytes=32 time=1144ms TTL=117
Reply from 84.234.17.86: bytes=32 time=1121ms TTL=117
Reply from 84.234.17.86: bytes=32 time=1738ms TTL=117
Reply from 84.234.17.86: bytes=32 time=1188ms TTL=117
Request timed out.
Request timed out.
Reply from 84.234.17.86: bytes=32 time=1431ms TTL=117
Reply from 84.234.17.86: bytes=32 time=654ms TTL=117
Reply from 84.234.17.86: bytes=32 time=2423ms TTL=117
Reply from 84.234.17.86: bytes=32 time=559ms TTL=117
Reply from 84.234.17.86: bytes=32 time=944ms TTL=117
Reply from 84.234.17.86: bytes=32 time=2584ms TTL=117
Reply from 84.234.17.86: bytes=32 time=284ms TTL=117
Request timed out.
Reply from 84.234.17.86: bytes=32 time=427ms TTL=117
Reply from 84.234.17.86: bytes=32 time=251ms TTL=117
Reply from 84.234.17.86: bytes=32 time=1029ms TTL=117
Reply from 84.234.17.86: bytes=32 time=1574ms TTL=117
Reply from 84.234.17.86: bytes=32 time=245ms TTL=117


I have checked that there are 0 other devices on the network at the time of doing this ping, and that on my PC, there is no other traffic on the nic. Last time i played with no noticeable lag was last Sunday night. You've also told me previously that weather was to blame, and tomorrow is lined up to be a near perfect day in the Cape, so you can be sure I will be testing this very carefully.
Click to expand...

Please PM me your UTID as I do not have it on record.
 
I've just sent it Ronald. Please confirm that you have it.

Yesterday was ok, today not so. The inconsistency appears to continue.

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