anyone having issues in the Western Cape?
I'm seeing intermittent solid blocks of no connectivity LAG with no packets for about 3-4 seconds every 15 minutes or so on quake live today.
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
anyone having issues in the Western Cape?
I'm seeing intermittent solid blocks of no connectivity LAG with no packets for about 3-4 seconds every 15 minutes or so on quake live today.
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\WINDOWS\SYSTEM32>ping vienna.at -t
Pinging vienna.at [194.183.128.94] with 32 bytes of data:
Reply from 194.183.128.94: bytes=32 time=199ms TTL=44
Reply from 194.183.128.94: bytes=32 time=199ms TTL=44
Reply from 194.183.128.94: bytes=32 time=198ms TTL=44
Reply from 194.183.128.94: bytes=32 time=198ms TTL=44
Reply from 194.183.128.94: bytes=32 time=198ms TTL=44
Reply from 194.183.128.94: bytes=32 time=198ms TTL=44
Reply from 194.183.128.94: bytes=32 time=198ms TTL=44
Reply from 194.183.128.94: bytes=32 time=198ms TTL=44
Reply from 194.183.128.94: bytes=32 time=198ms TTL=44
Reply from 194.183.128.94: bytes=32 time=198ms TTL=44
Reply from 194.183.128.94: bytes=32 time=198ms TTL=44
Reply from 194.183.128.94: bytes=32 time=198ms TTL=44
Reply from 194.183.128.94: bytes=32 time=199ms TTL=44
Reply from 194.183.128.94: bytes=32 time=199ms TTL=44
Reply from 194.183.128.94: bytes=32 time=198ms TTL=44
Reply from 194.183.128.94: bytes=32 time=199ms TTL=44
Reply from 194.183.128.94: bytes=32 time=198ms TTL=44
Reply from 194.183.128.94: bytes=32 time=199ms TTL=44
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\WINDOWS\SYSTEM32>tracert vienna.at
Tracing route to vienna.at [194.183.128.94]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms home.gateway.pace.net [192.168.1.1]
2 * * * Request timed out.
3 23 ms 22 ms 23 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 27 ms 23 ms 23 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 22 ms 22 ms 22 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 23 ms 22 ms 23 ms 41.164.52.40
7 28 ms 23 ms 23 ms if-ae-7-0.tcore1.KLT-Cape-Town.as6453.net [41.206.164.53]
8 165 ms 166 ms 167 ms if-ae-5-80.tcore2.PV9-Lisbon.as6453.net [80.231.159.57]
9 173 ms 173 ms 172 ms if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
10 169 ms 173 ms 177 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
11 166 ms 166 ms 166 ms if-ae-19-2.tcore2.L78-London.as6453.net [80.231.138.22]
12 168 ms 168 ms 169 ms if-ae-15-2.tcore2.LDN-London.as6453.net [80.231.131.118]
13 168 ms 165 ms 166 ms ldn-b5-link.telia.net [62.115.9.173]
14 240 ms 165 ms 172 ms ldn-bb3-link.telia.net [213.155.132.194]
15 185 ms 183 ms 183 ms prs-bb3-link.telia.net [62.115.134.100]
16 191 ms 191 ms 192 ms zch-b2-link.telia.net [62.115.135.123]
17 197 ms 197 ms 195 ms russmedia-ic-317231-zch-b2.c.telia.net [62.115.146.227]
18 195 ms 194 ms 194 ms 194-208-001-037.tele.net [194.208.1.37]
19 194 ms 195 ms 195 ms gi0-2-75-cr6-swz1.net.tele.net [194.183.142.167]
20 197 ms 199 ms 198 ms service.tele.net [194.183.128.94]
Trace complete.
C:\WINDOWS\SYSTEM32>
Welcome to hell
Code:Tracing route to google.co.za [216.58.223.3] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 192.---.1.1 2 * * * Request timed out. 3 * * * Request timed out. 4 * * * Request timed out. 5 * * * Request timed out. 6 * * * Request timed out. 7 * * * Request timed out. 8 * * * Request timed out. 9 * * * Request timed out. 10 3474 ms 231 ms 59 ms jnb01s07-in-f3.1e100.net [216.58.223.3] Trace complete. C:\Users\Bashley>tracert afrihost.co.za Tracing route to afrihost.co.za [41.86.112.68] over a maximum of 30 hops: 1 1 ms 2 ms 1 ms 192..1.1 2 * * * Request timed out. 3 * * * Request timed out. 4 * * * Request timed out. 5 * * * Request timed out. 6 * * * Request timed out. 7 * * * Request timed out. 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * 3191 ms * 41.86.112.68 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete.
Hi
Line stats hardly ever stay the same, there are so many factors that bring in change.
Either way, I'll happily log a fault for you - please PM me the affected number and the ticket ref#.
So, update ... the Telkom guy came out. Turns out there was a fault on a line which he replaced while we chatted with him.
SNR is back to 11.5.
The line is syncing at 4megs, despite the disputed distance from the exchange - aaaaand the worlds a happy place.
Live and learn.
Thanks
That is good news.So, update ... the Telkom guy came out. Turns out there was a fault on a line which he replaced while we chatted with him.
SNR is back to 11.5.
The line is syncing at 4megs, despite the disputed distance from the exchange - aaaaand the worlds a happy place.
Live and learn.
Thanks
Nice![]()
That is good news.![]()
Well thank you ..... and its good to be back on the forum![]()
Thats pretty bad. Which area are you in pal?
The reason its timing out to that ip is because you are still on the old system where you get a reply on the 2nd hop. The timing out on the 3rd hop and terrible latency on further hops is pretty bad though.
You sure that's not between you and the exchange? Would you mind posting a ping test to bras.afrihost.com?
my line speed is going down to 1024k, but sometime that will go up to 1750k. original speed should be 2M, so what is the problem?![]()
If it's specific times it could be congestion, could also be Telkom working on the lines or your port messing up. I am not sure if you are on the new or old system, but as your first > second hop always timed out and the bras.afrihost (a ping to the equipment at the exchange) timed out, it is most likely a line fault/exchange issue.No problem.
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
My internet was perfect. 21:30, all hell down the tubes.
And so, I would like to ask. Is it possible for the the exchange to be perfect most of the time, and then shot to hell the rest of the time. The exchange node is about 30 meters from the house.
What's you attenuation/SNR?
don't remember , but I used the clientzone tool to check the line ==> all green.
1 <1 ms <1 ms 2 ms capetown.xxx.local [10.10.20.1]
2 192.168.1.254 reports: Destination net unreachable.
Tracing route to mybroadband.co.za [104.20.72.110]
over a maximum of 30 hops:
Comes and goes.
1 <1 ms <1 ms <1 ms capetown.xxx.local [10.10.20.1]
2 <1 ms <1 ms <1 ms 169.0.116.197
3 * * * Request timed out.
4 * * 32 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
5 27 ms 27 ms 24 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 25 ms 24 ms 26 ms 41.164.52.40
7 29 ms 28 ms 27 ms if-ae-7-0.tcore1.KLT-Cape-Town.as6453.net [41.206.164.53]
8 169 ms 167 ms 168 ms if-ae-5-20.tcore2.PV9-Lisbon.as6453.net [80.231.159.61]
9 168 ms 168 ms 168 ms if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
10 234 ms 279 ms 262 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
11 174 ms 173 ms 178 ms if-ae-19-2.tcore2.L78-London.as6453.net [80.231.138.22]
12 173 ms 173 ms 173 ms if-ae-2-2.tcore1.L78-London.as6453.net [80.231.131.2]
13 169 ms 167 ms 167 ms if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
14 168 ms 170 ms 167 ms 195.219.83.102
15 307 ms 308 ms 309 ms ae-1-9.edge2.SanJose3.Level3.net [4.69.209.181]
16 399 ms 416 ms 413 ms 4.53.210.78
17 298 ms 307 ms 300 ms ae3.bb04.sjc1.tfbnw.net [31.13.26.166]
18 319 ms 388 ms 318 ms ae9.bb03.prn2.tfbnw.net [31.13.25.198]
19 314 ms 313 ms 314 ms ae2.dr13.prn1.tfbnw.net [31.13.27.175]
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 323 ms 319 ms 318 ms edge-star-mini-shv-17-prn1.facebook.com [69.171.230.68]
Trace complete.