Cool Ideas Fibre ISP - Feedback

[cavedog]

I just regret referring the landlord to install his 10Mbps line with cool ideas. I thought the R499 deal being the best and cool ideas also being one of the best fibre ISP's it's a perfect match. Been 2 weeks of back and forth to get the TP Link delivered from Rosebank to Centurion. After that the line has been working fine but the PPPoE details stopped working today. Support can't say why it stopped working they have created a ticket and pushed it to core networks or someone like that who is going to have a look. Account is paid and not in arrears but PPPoE details has been disabled for some reason.

Line works fine with any other ISP. Probably the last person I will refer to cool ideas.

The actual connection when it's working is pretty good so there is that.

 

[jannier]

Friday night, attempt to watch a Twitch stream, nope! Buffering constantly. Getting really sick of these inconsistently bad international speeds with no resolution

Vuma trenched 100/100 Panorama, CPT

@TheRoDent @PBCool ?!?!?

Structured Communications
View attachment 645260

Corehorizon.io
View attachment 645262

Spitfire
View attachment 645264

Spoiler: International iperf

iperf3 -R -u -b 80M -p 17001 -c queen.cisp.co.za
Connecting to host queen.cisp.co.za, port 17001
Reverse mode, remote host queen.cisp.co.za is sending
[ 4] local 192.168.1.100 port 58160 connected to 62.233.65.195 port 17001
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-1.00 sec 9.74 MBytes 81.7 Mbits/sec 0.107 ms 18/1265 (1.4%)
[ 4] 1.00-2.00 sec 9.31 MBytes 78.1 Mbits/sec 0.076 ms 26/1218 (2.1%)
[ 4] 2.00-3.00 sec 9.35 MBytes 78.5 Mbits/sec 0.085 ms 28/1223 (2.3%)
[ 4] 3.00-4.00 sec 9.52 MBytes 79.8 Mbits/sec 0.069 ms 3/1221 (0.25%)
[ 4] 4.00-5.00 sec 9.08 MBytes 76.2 Mbits/sec 0.119 ms 68/1221 (5.6%)
[ 4] 5.00-6.00 sec 9.34 MBytes 78.3 Mbits/sec 0.088 ms 26/1221 (2.1%)
[ 4] 6.00-7.00 sec 9.53 MBytes 80.0 Mbits/sec 0.078 ms 0/1220 (0%)
[ 4] 7.00-8.00 sec 9.53 MBytes 79.9 Mbits/sec 0.118 ms 12/1221 (0.98%)
[ 4] 8.00-9.00 sec 9.39 MBytes 78.8 Mbits/sec 0.071 ms 22/1221 (1.8%)
[ 4] 9.00-10.00 sec 9.52 MBytes 79.8 Mbits/sec 0.084 ms 6/1220 (0.49%)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 97.1 MBytes 81.4 Mbits/sec 0.091 ms 212/12429 (1.7%)
[ 4] Sent 12429 datagrams
[SUM] 0.0-10.0 sec 29 datagrams received out-of-order

iperf Done.

Spoiler: Local iperf

iperf3 -R -u -b 80M -p 17001 -c trcvmh01.cisp.co.za
Connecting to host trcvmh01.cisp.co.za, port 17001
Reverse mode, remote host trcvmh01.cisp.co.za is sending
[ 4] local 192.168.1.100 port 50667 connected to 154.0.15.181 port 17001
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-1.00 sec 9.75 MBytes 81.7 Mbits/sec 0.164 ms 21/1269 (1.7%)
[ 4] 1.00-2.00 sec 9.52 MBytes 79.9 Mbits/sec 0.132 ms 1/1220 (0.082%)
[ 4] 2.00-3.00 sec 9.54 MBytes 80.0 Mbits/sec 0.174 ms 0/1221 (0%)
[ 4] 3.00-4.00 sec 9.54 MBytes 80.0 Mbits/sec 0.176 ms 0/1221 (0%)
[ 4] 4.00-5.00 sec 9.52 MBytes 80.0 Mbits/sec 0.165 ms 0/1219 (0%)
[ 4] 5.00-6.00 sec 9.55 MBytes 80.0 Mbits/sec 0.147 ms 0/1222 (0%)
[ 4] 6.00-7.00 sec 9.53 MBytes 80.0 Mbits/sec 0.214 ms 0/1220 (0%)
[ 4] 7.00-8.00 sec 9.55 MBytes 80.0 Mbits/sec 0.151 ms 0/1222 (0%)
[ 4] 8.00-9.00 sec 9.47 MBytes 79.4 Mbits/sec 0.129 ms 8/1220 (0.66%)
[ 4] 9.00-10.00 sec 9.53 MBytes 80.0 Mbits/sec 0.173 ms 0/1220 (0%)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 95.7 MBytes 80.3 Mbits/sec 0.163 ms 30/12255 (0.24%)
[ 4] Sent 12255 datagrams

iperf Done.

Did you see this?
https://coolzone.cisp.co.za/index.p...anorama-Parow-North-Boston-and-Tygerdal-.html

 

[DeatheCore]

Did you see this?
https://coolzone.cisp.co.za/index.p...anorama-Parow-North-Boston-and-Tygerdal-.html

Thanks for that. Although it doesn't say that the maintenance is necessarily alleviating congestion or anything specific, and it's only on the 24th. Guess that's better than never

 

[jannier]

Thanks for that. Although it doesn't say that the maintenance is necessarily alleviating congestion or anything specific, and it's only on the 24th. Guess that's better than never

have a look in the notification section, vumatel is making huge changes to their network in Cape Town, starting from the 13 or 14th to accommodate the big change they making on the 24th.

This is my areas preparation for that change:

Network Type Affected:
Active Ethernet
Change Description:
Access switches to be moved, one at a time, to a new distribution switch to accommodate the upcoming Cape Town master node changes

I am hopeful these will be positive changes, not that I have had bad performance in my area.

 

[John Tempus]

Well the higher latency seems to be on the Coreix peering network in London, as it is 140ms on the CISP part.

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                              router.lan -    0 |   24 |   24 |    0 |    0 |    0 |    0 |
|                           102.132.248.1 -    0 |   24 |   24 |    2 |    4 |   11 |    2 |
|                         102.132.175.109 -    0 |   24 |   24 |    1 |    1 |    1 |    1 |
|             cd-backbone.coolideas.co.za -    0 |   24 |   24 |    1 |    1 |    1 |    1 |
|                uwy-cust.coolideas.co.za -    0 |   24 |   24 |    1 |    1 |    1 |    1 |
|                uvu-cust.coolideas.co.za -    0 |   24 |   24 |  140 |  140 |  141 |  140 |
|ge-0-1-0-69.peering2.hex67.lon4.coreix.net -    0 |   24 |   24 |  184 |  186 |  239 |  184 |
|        xe-5-1.edge4.enf.lon5.coreix.net -    0 |   24 |   24 |  169 |  170 |  171 |  170 |
|        85.13.221.178.reverse.coreix.net -    0 |   24 |   24 |  169 |  169 |  170 |  169 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

It is still the response between cisp and coreix hop that adds the final coreix ping response.

So what I tried to say considering it is likely the same route at 141ms and 171ms that something between cisp->coreix is affected every day for at least the last month and considering it seems to actually be the same route it comes down

Case in point, I see we are going via yet another cisp exit router right now compared to your earlier mtr.

Your results went from uvu-cust.coolideas.co.za -> ge-0-1-0-69.peering2.hex67.lon4.coreix.net
My results now from uwu-cust.coolideas.co.za -> ge-0-1-0-69.peering2.hex67.lon4.coreix.net

I will check earlier in the day tomorrow when the final response sits in 140s , I am near certain right now that my exit router will be different again.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 44 | 44 | 0 | 0 | 1 | 0 |
| 155.93.248.1 - 0 | 44 | 44 | 2 | 8 | 48 | 11 |
| c3h-backbone.coolideas.co.za - 0 | 44 | 44 | 1 | 1 | 1 | 1 |
| cd-backbone.coolideas.co.za - 0 | 44 | 44 | 1 | 1 | 2 | 1 |
| c1l-backbone.coolideas.co.za - 0 | 44 | 44 | 1 | 1 | 2 | 1 |
| uwu-cust.coolideas.co.za - 0 | 44 | 44 | 140 | 141 | 147 | 147 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| xe-5-1.edge4.enf.lon5.coreix.net - 0 | 43 | 43 | 182 | 183 | 191 | 183 |
| 85.13.221.178.reverse.coreix.net - 0 | 44 | 44 | 168 | 168 | 170 | 168 |
|________________________________________________|______|______|______|______|______|______|

 

[jannier]

It is still the response between cisp and coreix hop that adds the final coreix ping response.

So what I tried to say considering it is likely the same route at 141ms and 171ms that something between cisp->coreix is affected every day for at least the last month and considering it seems to actually be the same route it comes down

Case in point, I see we are going via yet another cisp exit router right now compared to your earlier mtr.

Your results went from uvu-cust.coolideas.co.za -> ge-0-1-0-69.peering2.hex67.lon4.coreix.net
My results now from uwu-cust.coolideas.co.za -> ge-0-1-0-69.peering2.hex67.lon4.coreix.net

I will check earlier in the day tomorrow when the final response sits in 140s , I am near certain right now that my exit router will be different again.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 44 | 44 | 0 | 0 | 1 | 0 |
| 155.93.248.1 - 0 | 44 | 44 | 2 | 8 | 48 | 11 |
| c3h-backbone.coolideas.co.za - 0 | 44 | 44 | 1 | 1 | 1 | 1 |
| cd-backbone.coolideas.co.za - 0 | 44 | 44 | 1 | 1 | 2 | 1 |
| c1l-backbone.coolideas.co.za - 0 | 44 | 44 | 1 | 1 | 2 | 1 |
| uwu-cust.coolideas.co.za - 0 | 44 | 44 | 140 | 141 | 147 | 147 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| xe-5-1.edge4.enf.lon5.coreix.net - 0 | 43 | 43 | 182 | 183 | 191 | 183 |
| 85.13.221.178.reverse.coreix.net - 0 | 44 | 44 | 168 | 168 | 170 | 168 |
|________________________________________________|______|______|______|______|______|______|

Mine just checked again now and still seems the same as earlier today.

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                              router.lan -    0 |   20 |   20 |    0 |    0 |    0 |    0 |
|                           102.132.248.1 -    0 |   20 |   20 |    2 |    4 |   11 |    3 |
|                         102.132.175.109 -    0 |   20 |   20 |    1 |    1 |    1 |    1 |
|             cd-backbone.coolideas.co.za -    0 |   20 |   20 |    1 |    1 |    1 |    1 |
|                uwy-cust.coolideas.co.za -    0 |   20 |   20 |    1 |    1 |    1 |    1 |
|                uvu-cust.coolideas.co.za -    0 |   20 |   20 |  140 |  140 |  141 |  140 |
|ge-0-1-0-69.peering2.hex67.lon4.coreix.net -    0 |   20 |   20 |  184 |  184 |  196 |  184 |
|        xe-5-1.edge4.enf.lon5.coreix.net -    0 |   20 |   20 |  170 |  170 |  176 |  170 |
|        85.13.221.178.reverse.coreix.net -    0 |   20 |   20 |  169 |  169 |  170 |  169 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

 

[jannier]

It is still the response between cisp and coreix hop that adds the final coreix ping response.

So what I tried to say considering it is likely the same route at 141ms and 171ms that something between cisp->coreix is affected every day for at least the last month and considering it seems to actually be the same route it comes down

Case in point, I see we are going via yet another cisp exit router right now compared to your earlier mtr.

Your results went from uvu-cust.coolideas.co.za -> ge-0-1-0-69.peering2.hex67.lon4.coreix.net
My results now from uwu-cust.coolideas.co.za -> ge-0-1-0-69.peering2.hex67.lon4.coreix.net

I will check earlier in the day tomorrow when the final response sits in 140s , I am near certain right now that my exit router will be different again.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 44 | 44 | 0 | 0 | 1 | 0 |
| 155.93.248.1 - 0 | 44 | 44 | 2 | 8 | 48 | 11 |
| c3h-backbone.coolideas.co.za - 0 | 44 | 44 | 1 | 1 | 1 | 1 |
| cd-backbone.coolideas.co.za - 0 | 44 | 44 | 1 | 1 | 2 | 1 |
| c1l-backbone.coolideas.co.za - 0 | 44 | 44 | 1 | 1 | 2 | 1 |
| uwu-cust.coolideas.co.za - 0 | 44 | 44 | 140 | 141 | 147 | 147 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| xe-5-1.edge4.enf.lon5.coreix.net - 0 | 43 | 43 | 182 | 183 | 191 | 183 |
| 85.13.221.178.reverse.coreix.net - 0 | 44 | 44 | 168 | 168 | 170 | 168 |
|________________________________________________|______|______|______|______|______|______|

Yes there are multiple paths the data can take, I guess it is some sort of load balancing or something,
can see at HOP 4 & 5 on my image.

 

[Tinuva]

It is still the response between cisp and coreix hop that adds the final coreix ping response.

So what I tried to say considering it is likely the same route at 141ms and 171ms that something between cisp->coreix is affected every day for at least the last month and considering it seems to actually be the same route it comes down

Case in point, I see we are going via yet another cisp exit router right now compared to your earlier mtr.

Your results went from uvu-cust.coolideas.co.za -> ge-0-1-0-69.peering2.hex67.lon4.coreix.net
My results now from uwu-cust.coolideas.co.za -> ge-0-1-0-69.peering2.hex67.lon4.coreix.net

I will check earlier in the day tomorrow when the final response sits in 140s , I am near certain right now that my exit router will be different again.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 44 | 44 | 0 | 0 | 1 | 0 |
| 155.93.248.1 - 0 | 44 | 44 | 2 | 8 | 48 | 11 |
| c3h-backbone.coolideas.co.za - 0 | 44 | 44 | 1 | 1 | 1 | 1 |
| cd-backbone.coolideas.co.za - 0 | 44 | 44 | 1 | 1 | 2 | 1 |
| c1l-backbone.coolideas.co.za - 0 | 44 | 44 | 1 | 1 | 2 | 1 |
| uwu-cust.coolideas.co.za - 0 | 44 | 44 | 140 | 141 | 147 | 147 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| xe-5-1.edge4.enf.lon5.coreix.net - 0 | 43 | 43 | 182 | 183 | 191 | 183 |
| 85.13.221.178.reverse.coreix.net - 0 | 44 | 44 | 168 | 168 | 170 | 168 |
|________________________________________________|______|______|______|______|______|______|

I think I know why the latency for CoreIX is high. CISPs BGP announcements needs tweaking, because the return traffic is through IS to JHB then only to CPT

This is what I expect a return traceroute to look like:
Source: https://lg.telia.net/?type=trace&router=ldn-b4&address=155.93.246.141

Network: AS1299 - Telia Carrier
Router: London (Harbour Exchange) (ldn-b4)
Command: traceroute 155.93.246.141 as-number-lookup

traceroute to 155.93.246.141 (155.93.246.141), 30 hops max, 52 byte packets
 1  hurricane-ic-308791-ldn-b3.c.telia.net (80.239.161.222)  0.562 ms  1.682 ms  2.289 ms
 2  100ge4-1.core1.lon3.he.net (184.105.64.238) [AS  6939]  1.757 ms  2.487 ms  0.725 ms
 3  cool-ideas-service-provider.10gigabitethernet5-4.core1.lon1.he.net (216.66.80.170) [AS  6939]  1.233 ms  1.118 ms  0.937 ms
 4  uvt-cust.coolideas.co.za (154.0.4.121) [AS  37680]  141.325 ms  140.309 ms  140.257 ms
 5  uwx-cust.coolideas.co.za (154.0.4.161) [AS  37680]  140.540 ms  140.334 ms  140.319 ms
 6  ce-backbone.coolideas.co.za (154.0.1.14) [AS  37680]  141.916 ms  141.231 ms  140.455 ms
 7  c3i-backbone.coolideas.co.za (154.0.1.126) [AS  37680]  144.960 ms  144.443 ms  142.882 ms
 8  155.93.246.141 (155.93.246.141) [AS  37680]  141.479 ms  141.253 ms  142.655 ms

Or this looks goods:
Source: http://lg.as6453.net/lg/

Router: gin-ldn-tcore1 
Site: GB, London, LDN 
Command: traceroute inet4 155.93.246.141 as-number-lookup



traceroute to 155.93.246.141 (155.93.246.141), 30 hops max, 52 byte packets
 1  be3040.ccr21.lon01.atlas.cogentco.com (130.117.15.177) [AS  174]  0.671 ms  0.867 ms  1.259 ms
 2  cool-ideas-service-provider.10gigabitethernet5-4.core1.lon1.he.net (216.66.80.170) [AS  6939]  0.728 ms  0.633 ms  0.562 ms
 3  uvt-cust.coolideas.co.za (154.0.4.121) [AS  37680]  140.274 ms  140.126 ms  141.223 ms
 4  uwx-cust.coolideas.co.za (154.0.4.161) [AS  37680]  140.392 ms  140.619 ms  140.360 ms
 5  ce-backbone.coolideas.co.za (154.0.1.14) [AS  37680]  140.570 ms  140.493 ms  140.382 ms
 6  c3i-backbone.coolideas.co.za (154.0.1.126) [AS  37680]  147.298 ms  148.639 ms  143.215 ms
 7  155.93.246.141 (155.93.246.141) [AS  37680]  141.662 ms  141.021 ms  142.860 ms

However, some networks prefer to go through IS which then goes JHB then CTN.
Sample1.
Source: https://lg.eurorings.net/index.cgi

Location: London (UK) 




 1  te0-3-1-0.core1b-dock.isnet.net (195.66.224.198)  1.661 ms  2.814 ms  3.195 ms
 2  core1b-pkl-ten-0-1-2-0.ip.isnet.net (168.209.100.16) [AS  3741]  179.789 ms  190.453 ms  177.635 ms
 3  197.96.214.113 (197.96.214.113) [AS  3741]  175.708 ms  177.273 ms  175.739 ms
 4  u129-cust.coolideas.co.za (154.0.5.97) [AS  37680]  167.427 ms  167.166 ms  167.173 ms
 5  uzh-cust.coolideas.co.za (154.0.4.253) [AS  37680]  167.903 ms  167.925 ms  167.836 ms
 6  uvt-cust.coolideas.co.za (154.0.4.121) [AS  37680]  168.795 ms  169.287 ms  168.722 ms
 7  uwx-cust.coolideas.co.za (154.0.4.161) [AS  37680]  168.785 ms  168.699 ms  168.589 ms
 8  ce-backbone.coolideas.co.za (154.0.1.14) [AS  37680]  178.802 ms  168.848 ms  171.420 ms
 9  c3i-backbone.coolideas.co.za (154.0.1.126) [AS  37680]  172.900 ms  170.247 ms  172.202 ms
10  155.93.246.141 (155.93.246.141) [AS  37680]  169.559 ms  172.406 ms  170.175 ms

Sample 2.
Source: https://lookingglass.centurylink.com/

LONDON ENGLAND Traceroute results for:
155.93.246.141 (155.93.246.141)

Tracing route to 155.93.246.141
1 ae-1-3111.edge4.London1.Level3.net (4.69.141.230) 0ms 0ms 0ms
2 195.50.122.230 (195.50.122.230) 1ms 4ms 2ms
3 core1b-pkl-te0-0-0-0.ip.isnet.net (196.26.0.62) 163ms 165ms 163ms
4 core1b-pkl-te0-0-0-0.ip.isnet.net (196.26.0.62) 165ms 164ms 163ms
5 197.96.214.113 (197.96.214.113) 156ms 156ms 156ms
6 u129-cust.coolideas.co.za (154.0.5.97) 157ms 157ms 157ms
7 c41-backbone.coolideas.co.za (154.0.1.145) 157ms 157ms 157ms
8 uvt-cust.coolideas.co.za (154.0.4.121) 158ms 158ms 158ms
9 uwx-cust.coolideas.co.za (154.0.4.161) 158ms 158ms 158ms
10 ce-backbone.coolideas.co.za (154.0.1.14) 158ms 158ms 158ms
11 c3i-backbone.coolideas.co.za (154.0.1.126) 160ms 164ms 178ms
12 0.0.0.0 (0.0.0.0) * * *
13 0.0.0.0 (0.0.0.0) * * *
14 0.0.0.0 (0.0.0.0) * * *

Sample 4:
Source: https://us.ntt.net/support/looking-glass/

Query Results:
Router: London - GB 
Command: traceroute ip 155.93.246.141 

Disclaimer: Traceroute is a useful tool for determining the route a packet takes, but it should not be used as an accurate measure of network performance. For more information please view the Traceroute Disclaimer.


Tracing the route to 155.93.246.141

 1  ae-7.r02.londen03.uk.bb.gin.ntt.net (129.250.4.46) 0 msec  * 
    ae-1.a00.londen12.uk.bb.gin.ntt.net (129.250.2.146) 0 msec 
 2  dimensiondata-xe.r00.londen03.uk.bb.gin.ntt.net (83.231.199.234) 0 msec  3 msec 
    dimensiondata-0.r02.londen03.uk.bb.gin.ntt.net (83.231.235.222) 0 msec 
 3  168.209.100.213 176 msec 
    core1b-pkl-te0-0-0-0.ip.isnet.net (196.26.0.62) 166 msec 
    168.209.100.213 178 msec 
 4  core1b-pkl-te0-0-0-0.ip.isnet.net (196.26.0.62) 170 msec  168 msec  167 msec 
 5  197.96.214.113 164 msec 
    u129-cust.coolideas.co.za (154.0.5.97) 166 msec  165 msec 
 6  uzh-cust.coolideas.co.za (154.0.4.253) 165 msec  165 msec 
    u129-cust.coolideas.co.za (154.0.5.97) 156 msec 
 7  uzh-cust.coolideas.co.za (154.0.4.253) 156 msec  156 msec  156 msec 
 8  uvt-cust.coolideas.co.za (154.0.4.121) 157 msec  157 msec  157 msec 
 9  uwx-cust.coolideas.co.za (154.0.4.161) 157 msec 
    ce-backbone.coolideas.co.za (154.0.1.14) 167 msec  166 msec 
 10 c3i-backbone.coolideas.co.za (154.0.1.126) 187 msec  182 msec 
    ce-backbone.coolideas.co.za (154.0.1.14) 157 msec 
 11 c3i-backbone.coolideas.co.za (154.0.1.126) 165 msec  159 msec  159 msec 
 12  *  *  * 
 13  *  *  *

Unfortunately, CoreIX doesn't have a public route server / looking glass.

@PBCool

 

[John Tempus]

That explains the roughly 20ms increase routing through jhb to capetown.

This is not isolated to coreix only, the latency increase is to every UK based route that I tested when the latency sits in the 140s and above 160s.

So I am wondering what you described could be a general issue with BGP routing to UK for CISP that is now routing back through jhb to capetown leaving us with this 168ms response rather than 141ms it used to be a month ago.

 

[CRE4MPIE]

@PBCool please can you guys look at my ticket ? #COOL-20190412-252395

Jetaime seems to think all my tests were done on WiFi ...

Did 3 tests back to back. Not sure why it's so inconsistent

Thanks CP

 

[DeatheCore]

have a look in the notification section, vumatel is making huge changes to their network in Cape Town, starting from the 13 or 14th to accommodate the big change they making on the 24th.

This is my areas preparation for that change:

Network Type Affected:
Active Ethernet
Change Description:
Access switches to be moved, one at a time, to a new distribution switch to accommodate the upcoming Cape Town master node changes

I am hopeful these will be positive changes, not that I have had bad performance in my area.

It seems that the announcement we were talking about last night no longer exists and all I can find is this:

https://coolzone.cisp.co.za/index.php?rp=/announcements/1148/Vumatel.html#

Nothing under my notification section.

 

[jannier]

It seems that the announcement we were talking about last night no longer exists and all I can find is this:

https://coolzone.cisp.co.za/index.php?rp=/announcements/1148/Vumatel.html#

Nothing under my notification section.

Mmmm I notice, maybe @PBCool or @TheRoDent can enlighten us why it disappeared?

I did get a SMS about the maintenance when those announcements were posted by Vumatel.

Good Day,

Please be advised of the following scheduled change

Start Date:16 April 2019 @ 10h00
End Date:16 April 2019 @ 12h00

Area/s Affected:Eden Park

Description: To stabilize the fibre services

Residents will experience intermittent connectivity during this time.

Regards
Vuma Team

 

[renagade-wolf]

Sigh octotel just went down in Kenilworth. Red light on PON

 

[ChrisJ]

Sigh octotel just went down in Kenilworth. Red light on PON

Also off in Claremont

 

[ThatGuy_ZA]

Also off in Claremont

Yep, also off in Harfield Village.

@PBCool, any idea what's going on? Someone trip over an extension cord at Octotel?

 

[ChrisJ]

Octotel back on in Claremont

 

[Seeyou]

Octotel back on in Claremont

Came up, died again.

 

[image132]

Clearly Octotel haven't migrated to that plastic hardware yet. It rains here and the internet goes off

 

[Seeyou]

Clearly Octotel haven't migrated to that plastic hardware yet. It rains here and the internet goes off

I had the exact same thought, lol.

 

[zll]

Weirdly enough I haven't gone down. Same area. Harfield/Kenilworth/Claremont. (Edit. It might have gone down while I was out, which was around 12ish? But it's online and happy now.)

I do have a weird specific issue though. Latency to League of Legends servers went from the usual 150-160 last night to 190-200 this morning. Other games don't seem to be affected, as Apex is reporting the usual 158 ping to London servers.

Anyone else having a problem like this?

@TheRoDent @PBCool

Edit2. Also noticed my packet loss seems to have reappeared... Going to keep an eye on things again.