Status
Not open for further replies.
Yes this unfortunately is area related not just line related so will take some time to get movement from TTConnect.

same issue today. 1 mbps down 100 up
http://www.speedtest.net/result/6961742253.png

What is the issue ? The day is switched to cool ideas I encountered the problem. When I was on Fredd my line was 100/100. Doesnt make sense that its a widespread issue. It would most likely go away if I switched back to Fredd again.
 
My connection (from Illovo) is terrible today as well - I can barely load speed-tests.
 
same issue today. 1 mbps down 100 up
http://www.speedtest.net/result/6961742253.png

What is the issue ? The day is switched to cool ideas I encountered the problem. When I was on Fredd my line was 100/100. Doesnt make sense that its a widespread issue. It would most likely go away if I switched back to Fredd again.
Area related to us as the ISP, multiple clients experiencing the same thing.
 
Issue seems to be directly on Cool Ideas hop to London

Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                            172.18.7.225 -    0 |  100 |  100 |    0 |    0 |    0 |    0 |
|                            155.93.251.1 -    2 |   97 |   96 |    0 |    4 |   86 |    1 |
|                             154.0.1.125 -    0 |  100 |  100 |    0 |    0 |    2 |    0 |
|                              154.0.1.13 -    0 |  100 |  100 |    1 |    1 |    4 |    1 |
|                             154.0.3.106 -    0 |  100 |  100 |  189 |  190 |  192 |  190 |
|            bbr01.lon01.networklayer.com -    0 |  100 |  100 |  190 |  190 |  225 |  190 |
|   ae5.cbs02.tg01.lon01.networklayer.com -    0 |  100 |  100 |  191 |  191 |  200 |  191 |
|    c5.13.2da9.ip4.static.sl-reverse.com -    0 |  100 |  100 |  191 |  191 |  219 |  191 |
|    79.76.32a9.ip4.static.sl-reverse.com -    0 |  100 |  100 |  191 |  192 |  205 |  192 |
|    cd.76.32a9.ip4.static.sl-reverse.com -    0 |  100 |  100 |  191 |  191 |  209 |  191 |
|                  eu-london3.restream.io -    0 |  100 |  100 |  191 |  191 |  252 |  191 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
 
Issue seems to be directly on Cool Ideas hop to London

Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                            172.18.7.225 -    0 |  100 |  100 |    0 |    0 |    0 |    0 |
|                            155.93.251.1 -    2 |   97 |   96 |    0 |    4 |   86 |    1 |
|                             154.0.1.125 -    0 |  100 |  100 |    0 |    0 |    2 |    0 |
|                              154.0.1.13 -    0 |  100 |  100 |    1 |    1 |    4 |    1 |
|                             154.0.3.106 -    0 |  100 |  100 |  189 |  190 |  192 |  190 |
|            bbr01.lon01.networklayer.com -    0 |  100 |  100 |  190 |  190 |  225 |  190 |
|   ae5.cbs02.tg01.lon01.networklayer.com -    0 |  100 |  100 |  191 |  191 |  200 |  191 |
|    c5.13.2da9.ip4.static.sl-reverse.com -    0 |  100 |  100 |  191 |  191 |  219 |  191 |
|    79.76.32a9.ip4.static.sl-reverse.com -    0 |  100 |  100 |  191 |  192 |  205 |  192 |
|    cd.76.32a9.ip4.static.sl-reverse.com -    0 |  100 |  100 |  191 |  191 |  209 |  191 |
|                  eu-london3.restream.io -    0 |  100 |  100 |  191 |  191 |  252 |  191 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
I don't see latency on this only packets transmitted?
 
Please state your area and fibre provider when doing so, no core, backhaul or longhaul issues.
 
I don't see latency on this only packets transmitted?

Best | Avrg | Wrst | Last |
These are the pings.
so avg of 190 to your london hop at 154.0.3.106

Vumatel Trenched 100/100
Bellville Cape Town
 
I'm not on cool ideas. I use Aeonova360 so this is from a A360 fibre provider for what it's worth.

cisp_trace1.png
 
Last edited:
Seems to have settled back down again

Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                            172.18.7.225 -    0 |  101 |  101 |    0 |    0 |    0 |    0 |
|                            155.93.251.1 -    0 |  101 |  101 |    0 |    2 |   47 |    1 |
|                             154.0.1.125 -    0 |  101 |  101 |    0 |    0 |    2 |    0 |
|                              154.0.1.13 -    0 |  101 |  101 |    1 |    1 |    4 |    1 |
|                             154.0.3.106 -    0 |  101 |  101 |  141 |  141 |  142 |  141 |
|            bbr01.lon01.networklayer.com -    0 |  101 |  101 |  141 |  143 |  224 |  141 |
|   ae5.cbs01.tg01.lon01.networklayer.com -   20 |   57 |   46 |  142 |  145 |  266 |  142 |
|    c1.13.2da9.ip4.static.sl-reverse.com -    0 |  101 |  101 |  142 |  142 |  162 |  142 |
|    7d.76.32a9.ip4.static.sl-reverse.com -    0 |  101 |  101 |  143 |  144 |  155 |  146 |
|    c9.76.32a9.ip4.static.sl-reverse.com -    0 |  101 |  101 |  143 |  145 |  373 |  143 |
|                  eu-london4.restream.io -    0 |  101 |  101 |  142 |  142 |  145 |  142 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
 
I'm not on cool ideas. I use Aeonova360 so this is from a A360 fibre provider for what it's worth.

cisp_trace1.png
So this means A360 is peering with HE locally and setting a pref on their peer as per HEs guidelines which then routes return via London, correction it looks like their upstream is Seacom which is even more of a surprise.
 
So this means A360 is peering with HE locally and setting a pref on their peer as per HEs guidelines which then routes return via London, correction it looks like their upstream is Seacom which is even more of a surprise.

To be honest I have no idea what that means but the fact that you are surprise does it mean it's bad?

EDIT: okay sorry now I understand what you meant. I did a trace route to that IP specifically to test the latency as some were complaining that that router is the one that was giving increased latency.
 
Last edited:
I'm not on cool ideas. I use Aeonova360 so this is from a A360 fibre provider for what it's worth.

cisp_trace1.png

So this means A360 is peering with HE locally and setting a pref on their peer as per HEs guidelines which then routes return via London, correction it looks like their upstream is Seacom which is even more of a surprise.

I think you both are confused :P

1. The ip address 154.0.3.106 is in fact on a London router (I am sure @PBCool knows this)
2. Latency and routing between A360 and CISP looks fine at JHB.
--> Looks like A360 doesn't peer at Nap, they use seacom, and seacom and cisp routes fine between each other at nap when looking at traceroutes from both sides.

@cavedog, rather do a traceroute to a CISP IP address, like www.cisp.co.za / 154.0.13.95

Code:
~ # mtr --report-wide --show-ips 160.20.252.129
Start: Sat Jan 13 12:52:19 2018
HOST: monitor.heaven.za.net                                Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- router.heaven.za.net (192.168.241.1)                  0.0%    10    0.5   0.5   0.4   0.5   0.0
  2.|-- 155.93.251.1                                          0.0%    10    1.3   1.5   1.3   2.6   0.0
  3.|-- 154.0.1.125                                           0.0%    10    1.2   1.2   1.0   1.3   0.0
  4.|-- 154.0.1.13                                            0.0%    10    1.3   1.5   1.3   1.7   0.0
  5.|-- seacom.ixp.capetown (196.10.140.66)                   0.0%    10    2.1   2.5   2.0   4.9   0.6
  6.|-- ae-2.cr-02-cpt.za.seacomnet.com (105.16.30.2)         0.0%    10   20.9  20.6  18.8  22.4   1.1
  7.|-- xe-0-0-0-8.cr-02-jnb.za.seacomnet.com (105.16.9.181)  0.0%    10   21.9  21.2  19.2  22.8   1.0
  8.|-- xe-0-0-0-0.er-02-jnb.za.seacomnet.com (105.16.28.10)  0.0%    10   18.6  18.7  18.5  19.9   0.3
  9.|-- 105.22.42.106                                         0.0%    10   18.5  18.7  18.5  19.2   0.0
 10.|-- 160.20.252.5                                          0.0%    10   18.6  18.7  18.5  18.9   0.0
 11.|-- 160.20.252.129                                        0.0%    10   20.9  21.6  20.9  22.8   0.3
 
I think you both are confused :P

1. The ip address 154.0.3.106 is in fact on a London router (I am sure @PBCool knows this)
2. Latency and routing between A360 and CISP looks fine at JHB.
--> Looks like A360 doesn't peer at Nap, they use seacom, and seacom and cisp routes fine between each other at nap when looking at traceroutes from both sides.

@cavedog, rather do a traceroute to a CISP IP address, like www.cisp.co.za / 154.0.13.95

Code:
~ # mtr --report-wide --show-ips 160.20.252.129
Start: Sat Jan 13 12:52:19 2018
HOST: monitor.heaven.za.net                                Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- router.heaven.za.net (192.168.241.1)                  0.0%    10    0.5   0.5   0.4   0.5   0.0
  2.|-- 155.93.251.1                                          0.0%    10    1.3   1.5   1.3   2.6   0.0
  3.|-- 154.0.1.125                                           0.0%    10    1.2   1.2   1.0   1.3   0.0
  4.|-- 154.0.1.13                                            0.0%    10    1.3   1.5   1.3   1.7   0.0
  5.|-- seacom.ixp.capetown (196.10.140.66)                   0.0%    10    2.1   2.5   2.0   4.9   0.6
  6.|-- ae-2.cr-02-cpt.za.seacomnet.com (105.16.30.2)         0.0%    10   20.9  20.6  18.8  22.4   1.1
  7.|-- xe-0-0-0-8.cr-02-jnb.za.seacomnet.com (105.16.9.181)  0.0%    10   21.9  21.2  19.2  22.8   1.0
  8.|-- xe-0-0-0-0.er-02-jnb.za.seacomnet.com (105.16.28.10)  0.0%    10   18.6  18.7  18.5  19.9   0.3
  9.|-- 105.22.42.106                                         0.0%    10   18.5  18.7  18.5  19.2   0.0
 10.|-- 160.20.252.5                                          0.0%    10   18.6  18.7  18.5  18.9   0.0
 11.|-- 160.20.252.129                                        0.0%    10   20.9  21.6  20.9  22.8   0.3

Yeah now I understand what @PBCool meant. I tested that IP specifically to check what the latency it has to that IP from A360 because the CPT people were complaining of increased latency on that specific router....

The peering seems 100% fine at JHB at JINX I think.

cisp_trace2.png
 
My Voip quality has gone terrible as of this morning. 5 phones through hosted pbx (hosted in Jburg). Everything worked 100% for last 3 months up to today. The calls connect but lots of breakups. If I use our 3G backup all is fine. Any ideas?

Vumatel Durbanville, trenched.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X