1500ms local ping. help!

They're back.

I guess this confirms the problem. I'll get hold of Telkom once I have three traceroutes.

Code: 
Tracing route to mybroadband.co.za [41.203.21.137]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.94
  2   462 ms   467 ms   484 ms  dsl-***-**-**.telkomadsl.co.za [41.***.**.*]
  3   501 ms   505 ms   503 ms  rrba-ip-lir-1-gig-3-0-0.telkom-ipnet.co.za [196.43.11.134]
  4   469 ms   470 ms   495 ms  196.43.25.138
  5   547 ms   542 ms   554 ms  mtn-gw.telkom-ipnet.co.za [196.25.58.18]
  6   488 ms   498 ms   508 ms  41.181.139.108
  7   537 ms   514 ms   509 ms  196.44.31.97
  8   514 ms   502 ms   517 ms  ge4-0-0.gw17.jnb6.za.mtnbusiness.net [196.30.1.37]
  9   514 ms   502 ms   501 ms  vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.136]
 10   495 ms   500 ms   508 ms  core-router1.jnb2.host-h.net [196.30.213.108]
 11   510 ms   508 ms   515 ms  41.72.136.53
 12   485 ms   499 ms   501 ms  mybroadband.co.za [41.203.21.137]

Trace complete.
 
Same issue on my side in Boksburg (Dayan Glen suburb). Had it last week Wednesday, and it came right the next day. Definitely looks like it's back again. And on Diablo night at that :(

Code: 
Tracing route to mybroadband.co.za [41.203.21.137]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.0.1
  2  1054 ms  1021 ms   985 ms  41-133-74-1.dsl.mweb.co.za [41.133.74.1]
  3   959 ms   949 ms   933 ms  41-86-107-6.mweb.co.za [41.86.107.6]
  4   966 ms   968 ms   984 ms  vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
  5  1017 ms  1052 ms  1044 ms  196.22.169.241
  6   948 ms   945 ms   931 ms  tengig0-1-0-0.vic-up-1.mweb.co.za [197.80.4.125]
  7   979 ms   999 ms  1021 ms  g-0-3-vic-jinx-2.mweb.co.za [196.22.163.1]
  8   999 ms   982 ms   963 ms  196.22.161.134
  9   985 ms   987 ms   992 ms  jh-cr-2.za--jh-pr-1.za.mtnns.net [196.44.0.223]
 10   957 ms   980 ms   989 ms  196.44.31.99
 11   991 ms   975 ms   980 ms  ge11-0-0.gw2.jnb6.za.mtnbusiness.net [196.30.1.22]
 12   961 ms   980 ms  1007 ms  vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.136]
 13   962 ms   994 ms  1002 ms  196.30.213.108
 14   976 ms   941 ms   912 ms  41.72.136.53
 15  1044 ms  1047 ms  1043 ms  mybroadband.co.za [41.203.21.137]
 
Just came back from my brother's house.

He also lives in Sunward Park. Also has huge (1000+) local pings.

Kind of feel sorry for him... Diablo 3 being released in a couple of hours and all... :cry:
 
Having the same problem on the Glenvista exchange the whole of yesterday and today :(
 
Murderous Telskum

thisgeek said:
Bardene exchange I'm guessing? I'm right down the road from the bloody thing.
I logged an online fault with Telkom at around 23:30 last night.
Click to expand...

Hey man. I am on Bardene 2 as well, massive issues with latency this evening 14/05. Local latency goes to 900ms.

Still having issues on your side?

Stay strong :D
 
Yep, back strong again tonight. It's better than it was an hour ago tho. It was over 700ms!

Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms dsldevice.lan [192.168.10.1]
2 408 ms 387 ms 384 ms 41-133-74-1.dsl.mweb.co.za [41.133.74.1]
3 378 ms 384 ms 383 ms tengig-0-0-0-100.vic-ipc-2.mweb.co.za [196.22.163.206]
Click to expand...

What pisses me off though is that the ticket I logged the other night is still in "Open - Logged to Telkom" status. I just escalated it, but I doubt I'll get a response any time soon.
 
Yeah, I have had so many issues over the last couple days, not to mention the outage of Bardene 2 that took 6 days to resolve. Now the latency is off the charts. WHY DO WE HAVE TO BEND OVER BACKWARDS TO GET DECENT INTERNET IN THIS COUNTRY FFS!

Yes I know, ALL CAPS RAGE ! :mad::mad::mad::mad::mad:
 
D3x! said:
Mine seems fine now this morning
Click to expand...

Mine isn't:cry:.

Code: 
Tracing route to mybroadband.co.za [41.203.21.137]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.94
  2   273 ms   267 ms   276 ms  dsl-***-**-**.telkomadsl.co.za [41.***.**.*]
  3   292 ms   297 ms   301 ms  rrba-ip-lir-1-gig-3-0-0.telkom-ipnet.co.za [196.43.11.134]
  4   303 ms   300 ms   302 ms  196.43.25.138
  5   293 ms   268 ms   267 ms  mtn-gw.telkom-ipnet.co.za [196.25.58.18]
  6   266 ms   264 ms   265 ms  41.181.139.108
  7   282 ms   280 ms   273 ms  196.44.31.97
  8   267 ms   266 ms   277 ms  ge4-0-0.gw17.jnb6.za.mtnbusiness.net [196.30.1.37]
  9   299 ms   286 ms   284 ms  vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.136]
 10   305 ms   303 ms   305 ms  core-router1.jnb2.host-h.net [196.30.213.108]
 11   302 ms   319 ms   319 ms  41.72.136.53
 12   314 ms   309 ms   303 ms  mybroadband.co.za [41.203.21.137]

Trace complete.

Better than last night, but still not good.
 
last night was ****.

This Morning was @ 6ms.

Now back too the dogs really WTF...

Pinging greens.dyndns.tv [41.185.69.93] with 32 bytes of data:
Reply from 41.185.69.93: bytes=32 time=1055ms TTL=50
Reply from 41.185.69.93: bytes=32 time=863ms TTL=50
Reply from 41.185.69.93: bytes=32 time=699ms TTL=50
Reply from 41.185.69.93: bytes=32 time=686ms TTL=50
Reply from 41.185.69.93: bytes=32 time=742ms TTL=50
Reply from 41.185.69.93: bytes=32 time=739ms TTL=50
Reply from 41.185.69.93: bytes=32 time=730ms TTL=50
Reply from 41.185.69.93: bytes=32 time=747ms TTL=50
Reply from 41.185.69.93: bytes=32 time=742ms TTL=50
 
The alberton area was down yesterday, there was a problem somewhere but i did see they had it listed in their Notice board of area's down. apparently there were 1140 users affected. It is no longer listed on their notice board so i assume it has been repaired
 
Drunkard #1 said:
Mine isn't:cry:.

Code: 
Tracing route to mybroadband.co.za [41.203.21.137]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.94
  2   273 ms   267 ms   276 ms  dsl-***-**-**.telkomadsl.co.za [41.***.**.*]
  3   292 ms   297 ms   301 ms  rrba-ip-lir-1-gig-3-0-0.telkom-ipnet.co.za [196.43.11.134]
  4   303 ms   300 ms   302 ms  196.43.25.138
  5   293 ms   268 ms   267 ms  mtn-gw.telkom-ipnet.co.za [196.25.58.18]
  6   266 ms   264 ms   265 ms  41.181.139.108
  7   282 ms   280 ms   273 ms  196.44.31.97
  8   267 ms   266 ms   277 ms  ge4-0-0.gw17.jnb6.za.mtnbusiness.net [196.30.1.37]
  9   299 ms   286 ms   284 ms  vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.136]
 10   305 ms   303 ms   305 ms  core-router1.jnb2.host-h.net [196.30.213.108]
 11   302 ms   319 ms   319 ms  41.72.136.53
 12   314 ms   309 ms   303 ms  mybroadband.co.za [41.203.21.137]

Trace complete.

Better than last night, but still not good.
Click to expand...



Also. Tested this morning before I left for work, and first hop (after the router) was the same... ~ 200ms.
 
FFS. It was fine again when I left home this morning, and now it's broken again. All I want to do is play Diablo...
 
ah thats lame, friends in the alberton area are reporting there are still issues on their lines aswell. What a **** time for a network fault to occur. why the day D3 is released :p
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X