ichigo
Executive Member
Its either filter or traffic congestion on exchange/dslam try post a tracert to see if it might show anything wrong
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: What's the most interesting small town you've visited in South Africa?
Telkom or Mweb Problem?
- Thread starter DUDE!@##$%%
- Start date
Its either filter or traffic congestion on exchange/dslam try post a tracert to see if it might show anything wrong
dbtrethewey
New Member
Green
Low on smarts so request assistance on finding the line specs. I have done a speedtest and on a 4meg line, I am getting usually 3 megs down in Africa , .3 up, then .3 down from States or Europe with the. Uploads down to .1 to as low as .08 to Germany where our server is resting ( that seems like a dumb idea now . . ) I'm 59 so time is gettin short ! I take it this is a Telkom problem with their overseas lines?
Where can I find the other line specs please?
Low on smarts so request assistance on finding the line specs. I have done a speedtest and on a 4meg line, I am getting usually 3 megs down in Africa , .3 up, then .3 down from States or Europe with the. Uploads down to .1 to as low as .08 to Germany where our server is resting ( that seems like a dumb idea now . . ) I'm 59 so time is gettin short ! I take it this is a Telkom problem with their overseas lines?
Where can I find the other line specs please?
dbtrethewey
New Member
sounds like a plan , how do you post a tracert?
Ok forst time i've done a tracert it did it to Greece here it is:
traceroute to 41.133.156.208 (41.133.156.208), 15 hops max, 40 byte packets
1 warp-srv (147.102.222.200) 0.349 ms 0.298 ms 0.226 ms
2 grnetRouter.ntua-primary.koletti-1.access-link.grnet.gr (194.177.209.117) 28.840 ms 0.474 ms 0.351 ms
3 eie2-to-koletti1.backbone.grnet.gr (195.251.27.46) 0.487 ms 0.509 ms 0.477 ms
4 grnet.rt1.ath2.gr.geant2.net (62.40.124.89) 0.611 ms 0.623 ms 0.600 ms
5 as0.rt1.vie.at.geant2.net (62.40.112.165) 30.839 ms 30.896 ms 30.785 ms
6 tenGigabitEthernet1-3.ar2.VIE1.gblx.net (64.214.145.145) 150.876 ms 195.914 ms 30.949 ms
7 OTE-INTERNATIONAL-SOLUTIONS-S-A.TenGigabitEthernet6-1.ar3.FRA4.gblx.net (64.215.27.210) 99.785 ms 98.171 ms 98.545 ms
8 frankfurt-2--gayrettepe-t2-2.turktelekom.com.tr (212.156.101.18) 100.397 ms 94.766 ms 94.922 ms
9 static.turktelekom.com.tr (212.156.103.33) 148.994 ms 148.131 ms 148.131 ms
10 ge-0-2-0-0.lonth-inter-2.interoute.net (195.66.226.53) 99.651 ms 103.614 ms 99.508 ms
11 Gi0-0.lon-001-access-1.interoute.net (84.233.218.177) 99.650 ms 99.623 ms 99.531 ms
12 89.202.130.182 (89.202.130.182) 400.093 ms 399.513 ms 399.331 ms
13 tengig-0-0-0-0-41.vic-up-2.mweb.co.za (196.22.169.210) 400.213 ms 398.913 ms 400.599 ms
14 vl-12.vic-hscore-2.mweb.co.za (196.22.169.243) 398.342 ms 397.748 ms 397.847 ms
15 tengig-0-0-0-92.vic-ipc-1.mweb.co.za (196.22.189.17) 396.083 ms 395.953 ms 395.978 ms
traceroute to 41.133.156.208 (41.133.156.208), 15 hops max, 40 byte packets
1 warp-srv (147.102.222.200) 0.349 ms 0.298 ms 0.226 ms
2 grnetRouter.ntua-primary.koletti-1.access-link.grnet.gr (194.177.209.117) 28.840 ms 0.474 ms 0.351 ms
3 eie2-to-koletti1.backbone.grnet.gr (195.251.27.46) 0.487 ms 0.509 ms 0.477 ms
4 grnet.rt1.ath2.gr.geant2.net (62.40.124.89) 0.611 ms 0.623 ms 0.600 ms
5 as0.rt1.vie.at.geant2.net (62.40.112.165) 30.839 ms 30.896 ms 30.785 ms
6 tenGigabitEthernet1-3.ar2.VIE1.gblx.net (64.214.145.145) 150.876 ms 195.914 ms 30.949 ms
7 OTE-INTERNATIONAL-SOLUTIONS-S-A.TenGigabitEthernet6-1.ar3.FRA4.gblx.net (64.215.27.210) 99.785 ms 98.171 ms 98.545 ms
8 frankfurt-2--gayrettepe-t2-2.turktelekom.com.tr (212.156.101.18) 100.397 ms 94.766 ms 94.922 ms
9 static.turktelekom.com.tr (212.156.103.33) 148.994 ms 148.131 ms 148.131 ms
10 ge-0-2-0-0.lonth-inter-2.interoute.net (195.66.226.53) 99.651 ms 103.614 ms 99.508 ms
11 Gi0-0.lon-001-access-1.interoute.net (84.233.218.177) 99.650 ms 99.623 ms 99.531 ms
12 89.202.130.182 (89.202.130.182) 400.093 ms 399.513 ms 399.331 ms
13 tengig-0-0-0-0-41.vic-up-2.mweb.co.za (196.22.169.210) 400.213 ms 398.913 ms 400.599 ms
14 vl-12.vic-hscore-2.mweb.co.za (196.22.169.243) 398.342 ms 397.748 ms 397.847 ms
15 tengig-0-0-0-92.vic-ipc-1.mweb.co.za (196.22.189.17) 396.083 ms 395.953 ms 395.978 ms
ichigo
Executive Member
start > run > type cmd then enter
then type
tracert [website name] > [Where to save it on PC]
then enter then should save a tracert in text file on your PC
ichigo
Executive Member
Dont see anything terrible in that tracert still inst perfect in some hops, but doesnt look like its the exchange could be ISP, can you try another ISP account?
Last edited:
Pada
Executive Member
You should do the trace route from your PC using the tracert command-line application - like Merenwenrago said 2 posts back.
I think its my line because i'm getting an electric fence "tick" all the time and its not my fence cause i unplugged it & turned it off and still its "ticking". Is it possible that a neighbors fence (i have neighbors on each side with fences) is some how touching their line, cause i checked the Telkom pole (unfortunately its in my garden) and it looked ok.