Status
Not open for further replies.
Hi @PBCool

I am having an issue with my download speeds. I have the 10/2 package.

The speed tests show that when I connect to a Cape Town server, I get full speed. The further away I go, the slower it gets, but upload speed is consistent. What's up with that?

https://www.speedtest.net/result/8003719760
https://www.speedtest.net/result/8004984534
https://www.speedtest.net/result/8005623217

Packet loss, typically caused by a congested network, or a bad client link causes worse and worse performance the higher latency servers you access.

Please see https://mybroadband.co.za/forum/thr...-fno-issues-by-providing-information.1003252/ for more of an explanation.

Which area/network are you on?
 
@joeline Has Octotel finished their emergency maintenance and did it fix your problem?
If they did, I did not notice anything different. At once stage ping was 204 where before it was 144/145. It is now 170. Will that make a difference in streaming? As far as speed is concern, the same as any other day. Guess we will see tonight.
 
If they did, I did not notice anything different. At once stage ping was 204 where before it was 144/145. It is now 170. Will that make a difference in streaming? As far as speed is concern, the same as any other day. Guess we will see tonight.

That's probably in relation to the WACS cable maintenance that was done earlier. PBcool said it was completed now though.
 
I have received confirmation today, that a COCT backhaul link to Blouberg, and Westbeach on the Octotel network is awaiting a capacity upgrade, and that it has been congested for a while.

The link is provided by City of Cape Town Fibre, and the upgrade process was meant to happen this morning, at 4am, but has not yet.

Has there been nothing about southern suburbs/claremont/rondebosch?

Thank you for the update.
 
My international latency is back to normal now, reduced by and average of 30+ ms

Cape Town, Brackenfell, Vuma Trenched, 200/200

Multi thread


Single Thread
 
Last edited:
Should be resolved.

I was still on my VPN when I checked. Just ran speedtest without it:



That latency is usually 140ms. Same thing happened last time I got shunted to the 102.xxx range.
 
Cape Town, Claremont/Southern Suburbs. Ocototel 100/25

London (Coreix) Multi-Threaded:
8005725765.png


Mine is higher than normal with speedtest but if I do a ping:

Pinging www.bbc.net.uk [212.58.244.67] with 32 bytes of data:
Reply from 212.58.244.67: bytes=32 time=141ms TTL=53
Reply from 212.58.244.67: bytes=32 time=141ms TTL=53
Reply from 212.58.244.67: bytes=32 time=141ms TTL=53
Reply from 212.58.244.67: bytes=32 time=141ms TTL=53

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

So not 100% sure.
 
Cape Town, Claremont/Southern Suburbs. Ocototel 100/25

Mine is higher than normal with speedtest but if I do a ping:

Pinging www.bbc.net.uk [212.58.244.67] with 32 bytes of data:
Reply from 212.58.244.67: bytes=32 time=141ms TTL=53
Reply from 212.58.244.67: bytes=32 time=141ms TTL=53
Reply from 212.58.244.67: bytes=32 time=141ms TTL=53
Reply from 212.58.244.67: bytes=32 time=141ms TTL=53

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

So not 100% sure.

Ping speedtest.coreix.net. I also get 140ms to BBC. The below is usually 140ms too:

Pinging speedtest.coreix.net [85.13.221.178] with 32 bytes of data:
Reply from 85.13.221.178: bytes=32 time=159ms TTL=53
Reply from 85.13.221.178: bytes=32 time=159ms TTL=53
Reply from 85.13.221.178: bytes=32 time=158ms TTL=53
Reply from 85.13.221.178: bytes=32 time=158ms TTL=53

Ping statistics for 85.13.221.178:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 158ms, Maximum = 159ms, Average = 158ms
 
Ping speedtest.coreix.net. I also get 140ms to BBC. The below is usually 140ms too:

Pinging speedtest.coreix.net [85.13.221.178] with 32 bytes of data:
Reply from 85.13.221.178: bytes=32 time=159ms TTL=53
Reply from 85.13.221.178: bytes=32 time=159ms TTL=53
Reply from 85.13.221.178: bytes=32 time=158ms TTL=53
Reply from 85.13.221.178: bytes=32 time=158ms TTL=53

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

Good call.

Pinging speedtest.coreix.net [85.13.221.178] with 32 bytes of data:
Reply from 85.13.221.178: bytes=32 time=170ms TTL=54
Reply from 85.13.221.178: bytes=32 time=170ms TTL=54
Reply from 85.13.221.178: bytes=32 time=170ms TTL=54
Request timed out.

Ping statistics for 85.13.221.178:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 170ms, Maximum = 170ms, Average = 170ms

Must be related to routing.
 
Good call.

Pinging speedtest.coreix.net [85.13.221.178] with 32 bytes of data:
Reply from 85.13.221.178: bytes=32 time=170ms TTL=54
Reply from 85.13.221.178: bytes=32 time=170ms TTL=54
Reply from 85.13.221.178: bytes=32 time=170ms TTL=54
Request timed out.

Ping statistics for 85.13.221.178:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 170ms, Maximum = 170ms, Average = 170ms

Must be related to routing.

Looks like its sorted now:

Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.0.1 -    0 |    7 |    7 |    0 |    0 |    1 |    0 |
|                            155.93.248.1 -    0 |    7 |    7 |    2 |    2 |    6 |    6 |
|            c3h-backbone.coolideas.co.za -    0 |    7 |    7 |    1 |    1 |    2 |    1 |
|             cd-backbone.coolideas.co.za -    0 |    7 |    7 |    1 |    1 |    2 |    1 |
|                uwu-cust.coolideas.co.za -    0 |    7 |    7 |  140 |  140 |  141 |  140 |
|ge-0-1-0-69.peering2.hex67.lon4.coreix.net -    0 |    7 |    7 |  141 |  141 |  142 |  141 |
|        xe-5-1.edge4.enf.lon5.coreix.net -    0 |    7 |    7 |  141 |  141 |  143 |  141 |
|        85.13.221.178.reverse.coreix.net -    0 |    7 |    7 |  141 |  141 |  142 |  141 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
 
Looks like its sorted now:

Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.0.1 -    0 |    7 |    7 |    0 |    0 |    1 |    0 |
|                            155.93.248.1 -    0 |    7 |    7 |    2 |    2 |    6 |    6 |
|            c3h-backbone.coolideas.co.za -    0 |    7 |    7 |    1 |    1 |    2 |    1 |
|             cd-backbone.coolideas.co.za -    0 |    7 |    7 |    1 |    1 |    2 |    1 |
|                uwu-cust.coolideas.co.za -    0 |    7 |    7 |  140 |  140 |  141 |  140 |
|ge-0-1-0-69.peering2.hex67.lon4.coreix.net -    0 |    7 |    7 |  141 |  141 |  142 |  141 |
|        xe-5-1.edge4.enf.lon5.coreix.net -    0 |    7 |    7 |  141 |  141 |  143 |  141 |
|        85.13.221.178.reverse.coreix.net -    0 |    7 |    7 |  141 |  141 |  142 |  141 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Not for me:

Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                         router.asus.com -    0 |   26 |   26 |    0 |    0 |    0 |    0 |
|                             154.0.0.246 -    5 |   22 |   21 |    0 |    0 |    1 |    0 |
|                             154.0.4.161 -    0 |   26 |   26 |    0 |    0 |    4 |    1 |
|                             154.0.3.106 -    0 |   26 |   26 |  140 |  140 |  142 |  140 |
|                   No response from host -  100 |    6 |    0 |    0 |    0 |    0 |    0 |
|        xe-5-1.edge4.enf.lon5.coreix.net -    0 |   26 |   26 |  168 |  168 |  171 |  168 |
|        85.13.221.178.reverse.coreix.net -    0 |   26 |   26 |  168 |  169 |  172 |  169 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Shrug, I'm not fussed. CISP usually fix it after a few days.
 
Also OK for me,

Pinging speedtest.coreix.net [85.13.221.178] with 32 bytes of data:
Reply from 85.13.221.178: bytes=32 time=141ms TTL=56
Reply from 85.13.221.178: bytes=32 time=141ms TTL=56
Reply from 85.13.221.178: bytes=32 time=141ms TTL=56
Reply from 85.13.221.178: bytes=32 time=141ms TTL=56

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

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| router.lan - 0 | 31 | 31 | 0 | 0 | 1 | 1 |
| 155.93.252.1 - 16 | 19 | 16 | 2 | 4 | 4 | 3 |
| c3h-backbone.coolideas.co.za - 0 | 31 | 31 | 1 | 1 | 2 | 1 |
| cd-backbone.coolideas.co.za - 0 | 31 | 31 | 1 | 1 | 1 | 1 |
| u166-cust.coolideas.co.za - 0 | 31 | 31 | 140 | 140 | 141 | 140 |
|ge-0-1-0-69.peering2.hex67.lon4.coreix.net - 0 | 31 | 31 | 141 | 143 | 184 | 141 |
| xe-5-1.edge4.enf.lon5.coreix.net - 0 | 31 | 31 | 142 | 143 | 148 | 142 |
| 85.13.221.178.reverse.coreix.net - 0 | 31 | 31 | 141 | 141 | 143 | 141 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
 
Indeed, Paul worked his magic it seems:

Pinging speedtest.coreix.net [85.13.221.178] with 32 bytes of data:
Reply from 85.13.221.178: bytes=32 time=141ms TTL=56
Reply from 85.13.221.178: bytes=32 time=141ms TTL=56
Reply from 85.13.221.178: bytes=32 time=141ms TTL=56
Reply from 85.13.221.178: bytes=32 time=141ms TTL=56

Ping statistics for 85.13.221.178:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 141ms, Maximum = 141ms, Average = 141ms
 
8006007390.png


Pinging speedtest.coreix.net [85.13.221.178] with 32 bytes of data:
Reply from 85.13.221.178: bytes=32 time=162ms TTL=57
Reply from 85.13.221.178: bytes=32 time=163ms TTL=57
Reply from 85.13.221.178: bytes=32 time=163ms TTL=57
Reply from 85.13.221.178: bytes=32 time=163ms TTL=57

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

i see you guys testing international is it suppose to be this slow for a 100/100 line. Im metro fibre

local
8006020751.png
 
Last edited:
Thanx Coolideas and Metrofibre for fixing my issues. When ONT was replaced the FSAN number was not updated. Strangely Internet still worked LOL. Today correct FSAN loaded.

Coolideas was very patient with me.. Although I did have to keep phoning them.

Also mikrotik profile and DNS was "messing" with some routes, but luckily figured it out.

For future ref: CISP Dynamic DNS servers work great. Also mikrotik profile should be default-encryption (for me on Metrofibre)...

My apologies @PBCool and @TheRoDent for some past rants..

Great network and patient staff.. ;)
 
Thanx Coolideas and Metrofibre for fixing my issues. When ONT was replaced the FSAN number was not updated. Strangely Internet still worked LOL. Today correct FSAN loaded.

Coolideas was very patient with me.. Although I did have to keep phoning them.

Also mikrotik profile and DNS was "messing" with some routes, but luckily figured it out.

For future ref: CISP Dynamic DNS servers work great. Also mikrotik profile should be default-encryption (for me on Metrofibre)...

My apologies @PBCool and @TheRoDent for some past rants..

Great network and patient staff.. ;)

so your international speed tests are running well? London coreix Ltd ... could you please test. I also moved from mf works to cool ideas
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X