Octotel CPT packet loss+slow speeds

Nutcracker

Active Member
Joined
Dec 19, 2005
Messages
56
I am based in Parklands with Seacom internet.
I have a 100/25Mbps line and for the last 9 months i have had lovely internet.
This evening however I found myself with 5% packet loss and unable to get even 10Mbps download.
Traceroute shows that the packet loss is on hop 1 from my router, so either Seacom's ENNI is congested or Octotel is facing some serious congestion... my money is on the latter.

Any one else facing similar issues?

Code:
  SEQ HOST                                     SIZE TTL TIME  STATUS            
6320 129.205.159.44                             56 255 3ms
6321 129.205.159.44                             56 255 4ms
6322 129.205.159.44                             56 255 4ms
6323 129.205.159.44                             56 255 3ms
6324 129.205.159.44                             56 255 4ms
6325 129.205.159.44                             56 255 3ms
6326 129.205.159.44                             56 255 4ms
6327 129.205.159.44                             56 255 4ms
6328 129.205.159.44                             56 255 4ms
6329 129.205.159.44                             56 255 4ms
6330 129.205.159.44                             56 255 4ms
6331 129.205.159.44                             56 255 4ms
6332 129.205.159.44                             56 255 4ms
6333 129.205.159.44                             56 255 3ms
6334 129.205.159.44                             56 255 4ms
6335 129.205.159.44                             56 255 4ms
    sent=6336 received=5958 packet-loss=5% min-rtt=3ms avg-rtt=5ms max-rtt=91ms
 

Attachments

CrypticZA

Senior Member
Joined
Sep 21, 2019
Messages
820
Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                              172.16.0.1 -    0 |   21 |   21 |   17 |   17 |   18 |   18 |
|                           197.234.241.1 -    0 |   21 |   21 |   18 |   18 |   25 |   19 |
|                           196.223.14.41 -    0 |   21 |   21 |   17 |   20 |   44 |   18 |
|                          74.125.245.209 -    0 |   21 |   21 |   18 |   18 |   19 |   19 |
|                            172.253.66.3 -    0 |   21 |   21 |   18 |   18 |   22 |   19 |
|                                 8.8.8.8 -    0 |   21 |   21 |   17 |   17 |   19 |   18 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
This is using Warp+ which uses SEACOM transit - i am Vumatel Table View + Cool Ideas
 

Nutcracker

Active Member
Joined
Dec 19, 2005
Messages
56
So just to clear up some possible confusion, Seacom is my ISP.
It used to be called Macrolan, but they were bought out a while ago and rebranded.

@CrypticZA - At least it seems that Vumatel and CISP has no issues
Really wish that Seacom would ditch their stupid closed peering policy so that I can get better latencies locally.
Had 360ms latency to my office yesterdayo_O
At least they sorted it after I logged a ticket and called in to explain how routing to local IP's should work.
 

CrypticZA

Senior Member
Joined
Sep 21, 2019
Messages
820
Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                              172.16.0.1 -    0 |   21 |   21 |   17 |   17 |   18 |   18 |
|                           197.234.241.1 -    0 |   21 |   21 |   18 |   18 |   25 |   19 |
|                           196.223.14.41 -    0 |   21 |   21 |   17 |   20 |   44 |   18 |
|                          74.125.245.209 -    0 |   21 |   21 |   18 |   18 |   19 |   19 |
|                            172.253.66.3 -    0 |   21 |   21 |   18 |   18 |   22 |   19 |
|                                 8.8.8.8 -    0 |   21 |   21 |   17 |   17 |   19 |   18 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
This is using Warp+ which uses SEACOM transit - i am Vumatel Table View + Cool Ideas
My trace route is using WARP+ (vpn) which uses SEACOM transit, Cool Ideas only take me to 1.1.1.1 and from there SEACOM transit kicks. Was showing that SEACOM transit is not an issue
 

Nutcracker

Active Member
Joined
Dec 19, 2005
Messages
56
My trace route is using WARP+ (vpn) which uses SEACOM transit, Cool Ideas only take me to 1.1.1.1 and from there SEACOM transit kicks. Was showing that SEACOM transit is not an issue
Gotcha.

I don't believe SEACOM transit is the issue. The fact that I am seeing loss from my router to the ISP means that Octotel's ME network is most probably buckling under the pressure of the lockdown.
It's probably why they didn't over free upgrades unlike most of the other FNO's.
I am curious to know how what their backhaul capacity is to the area?
Actually... thinking about it now, the OLT or the PON port could be the issue as well.
Regardless, it would be good to get some feedback from Octotel.
If my problem persists, I'll log a ticket with SEACOM to log with Octotel for further investigation.
 

CrypticZA

Senior Member
Joined
Sep 21, 2019
Messages
820
Gotcha.

I don't believe SEACOM transit is the issue. The fact that I am seeing loss from my router to the ISP means that Octotel's ME network is most probably buckling under the pressure of the lockdown.
It's probably why they didn't over free upgrades unlike most of the other FNO's.
I am curious to know how what their backhaul capacity is to the area?
Actually... thinking about it now, the OLT or the PON port could be the issue as well.
Regardless, it would be good to get some feedback from Octotel.
If my problem persists, I'll log a ticket with SEACOM to log with Octotel for further investigation.
Run some IPERF tests to see if there is packet loss. I know someone in West Beach who has been struggling to get their backhaul issue fixed for about a year now. During peak his 100/100 drops so low at times he can't even watch 480P Twitxh. Sadly their whole network in Cape Town has issues :/. We have them at work in CBD and it's horrible... 50 meg business account runs like a 10meg
 

Nutcracker

Active Member
Joined
Dec 19, 2005
Messages
56
Took me a while to figure out iperf, but got it right eventually:

Code:
C:\iperf-3.1.3-win64>iperf3.exe -R -V -t 15 -O 3 -c iperf.ct1.napafrica.net -u -b 85M
iperf 3.1.3
CYGWIN_NT-10.0 Nutty-PC 2.5.1(0.297/5/3) 2016-04-21 22:14 x86_64
Time: Sat, 04 Apr 2020 21:17:09 GMT
Connecting to host iperf.ct1.napafrica.net, port 5201
Reverse mode, remote host iperf.ct1.napafrica.net is sending
      Cookie: Nutty-PC.1586035029.882871.755b3f187
[  4] local 192.168.0.69 port 51767 connected to 196.10.99.34 port 5201
Starting Test: protocol: UDP, 1 streams, 8192 byte blocks, omitting 3 seconds, 15 second test
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-1.00   sec  9.12 MBytes  76.4 Mbits/sec  0.391 ms  93/1261 (7.4%)  (omitted)
[  4]   1.00-2.00   sec  9.38 MBytes  78.7 Mbits/sec  0.401 ms  186/1386 (13%)  (omitted)
[  4]   2.00-3.00   sec  9.48 MBytes  79.6 Mbits/sec  0.362 ms  78/1292 (6%)  (omitted)
[  4]   0.00-1.00   sec  9.79 MBytes  82.1 Mbits/sec  0.423 ms  49/1302 (3.8%)
[  4]   1.00-2.00   sec  9.83 MBytes  82.5 Mbits/sec  0.442 ms  35/1293 (2.7%)
[  4]   2.00-3.00   sec  9.72 MBytes  81.4 Mbits/sec  0.479 ms  46/1290 (3.6%)
[  4]   3.00-4.00   sec  9.38 MBytes  78.8 Mbits/sec  0.378 ms  106/1307 (8.1%)
[  4]   4.00-5.00   sec  9.67 MBytes  81.1 Mbits/sec  0.521 ms  53/1291 (4.1%)
[  4]   5.00-6.00   sec  9.59 MBytes  80.5 Mbits/sec  0.375 ms  75/1303 (5.8%)
[  4]   6.00-7.00   sec  10.0 MBytes  83.9 Mbits/sec  0.335 ms  17/1297 (1.3%)
[  4]   7.00-8.00   sec  9.72 MBytes  81.5 Mbits/sec  0.388 ms  52/1296 (4%)
[  4]   8.00-9.00   sec  9.83 MBytes  82.5 Mbits/sec  0.426 ms  39/1297 (3%)
[  4]   9.00-10.00  sec  9.64 MBytes  80.9 Mbits/sec  0.705 ms  63/1297 (4.9%)
[  4]  10.00-11.00  sec  9.87 MBytes  82.7 Mbits/sec  0.421 ms  34/1297 (2.6%)
[  4]  11.00-12.00  sec  9.57 MBytes  80.4 Mbits/sec  0.370 ms  72/1297 (5.6%)
[  4]  12.00-13.00  sec  9.91 MBytes  83.1 Mbits/sec  0.447 ms  30/1298 (2.3%)
[  4]  13.00-14.00  sec  9.68 MBytes  81.2 Mbits/sec  0.413 ms  58/1297 (4.5%)
[  4]  14.00-15.00  sec  9.23 MBytes  77.4 Mbits/sec  0.328 ms  117/1298 (9%)
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-15.00  sec   152 MBytes  85.3 Mbits/sec  0.333 ms  846/19465 (4.3%)
[  4] Sent 19465 datagrams
CPU Utilization: local/receiver 6.0% (2.9%u/3.1%s), remote/sender 0.8% (0.1%u/0.8%s)

iperf Done.
 

CrypticZA

Senior Member
Joined
Sep 21, 2019
Messages
820
Took me a while to figure out iperf, but got it right eventually:

Code:
C:\iperf-3.1.3-win64>iperf3.exe -R -V -t 15 -O 3 -c iperf.ct1.napafrica.net -u -b 85M
iperf 3.1.3
CYGWIN_NT-10.0 Nutty-PC 2.5.1(0.297/5/3) 2016-04-21 22:14 x86_64
Time: Sat, 04 Apr 2020 21:17:09 GMT
Connecting to host iperf.ct1.napafrica.net, port 5201
Reverse mode, remote host iperf.ct1.napafrica.net is sending
      Cookie: Nutty-PC.1586035029.882871.755b3f187
[  4] local 192.168.0.69 port 51767 connected to 196.10.99.34 port 5201
Starting Test: protocol: UDP, 1 streams, 8192 byte blocks, omitting 3 seconds, 15 second test
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-1.00   sec  9.12 MBytes  76.4 Mbits/sec  0.391 ms  93/1261 (7.4%)  (omitted)
[  4]   1.00-2.00   sec  9.38 MBytes  78.7 Mbits/sec  0.401 ms  186/1386 (13%)  (omitted)
[  4]   2.00-3.00   sec  9.48 MBytes  79.6 Mbits/sec  0.362 ms  78/1292 (6%)  (omitted)
[  4]   0.00-1.00   sec  9.79 MBytes  82.1 Mbits/sec  0.423 ms  49/1302 (3.8%)
[  4]   1.00-2.00   sec  9.83 MBytes  82.5 Mbits/sec  0.442 ms  35/1293 (2.7%)
[  4]   2.00-3.00   sec  9.72 MBytes  81.4 Mbits/sec  0.479 ms  46/1290 (3.6%)
[  4]   3.00-4.00   sec  9.38 MBytes  78.8 Mbits/sec  0.378 ms  106/1307 (8.1%)
[  4]   4.00-5.00   sec  9.67 MBytes  81.1 Mbits/sec  0.521 ms  53/1291 (4.1%)
[  4]   5.00-6.00   sec  9.59 MBytes  80.5 Mbits/sec  0.375 ms  75/1303 (5.8%)
[  4]   6.00-7.00   sec  10.0 MBytes  83.9 Mbits/sec  0.335 ms  17/1297 (1.3%)
[  4]   7.00-8.00   sec  9.72 MBytes  81.5 Mbits/sec  0.388 ms  52/1296 (4%)
[  4]   8.00-9.00   sec  9.83 MBytes  82.5 Mbits/sec  0.426 ms  39/1297 (3%)
[  4]   9.00-10.00  sec  9.64 MBytes  80.9 Mbits/sec  0.705 ms  63/1297 (4.9%)
[  4]  10.00-11.00  sec  9.87 MBytes  82.7 Mbits/sec  0.421 ms  34/1297 (2.6%)
[  4]  11.00-12.00  sec  9.57 MBytes  80.4 Mbits/sec  0.370 ms  72/1297 (5.6%)
[  4]  12.00-13.00  sec  9.91 MBytes  83.1 Mbits/sec  0.447 ms  30/1298 (2.3%)
[  4]  13.00-14.00  sec  9.68 MBytes  81.2 Mbits/sec  0.413 ms  58/1297 (4.5%)
[  4]  14.00-15.00  sec  9.23 MBytes  77.4 Mbits/sec  0.328 ms  117/1298 (9%)
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-15.00  sec   152 MBytes  85.3 Mbits/sec  0.333 ms  846/19465 (4.3%)
[  4] Sent 19465 datagrams
CPU Utilization: local/receiver 6.0% (2.9%u/3.1%s), remote/sender 0.8% (0.1%u/0.8%s)

iperf Done.
Yea as you can see there is packet loss on the line
 

Nutcracker

Active Member
Joined
Dec 19, 2005
Messages
56
Definitely getting better as we go out of peak time:

1586036108094.png

I'll give them the few spikes around 23:20 as that might have been me messing around with iperf.
I'll let it run over night and see how it looks in the morning.
 

Nutcracker

Active Member
Joined
Dec 19, 2005
Messages
56
Looking better this morning, but still some blips:

1586076614147.png

I think the spot around 09:30 was me downloading on the media pc, but even so, I wasn't hitting full speed, so there shouldn't packet loss at this time of that time of the morning.

I ran another iperf this morning and just now. Even at 10Mbps I am getting loss, so something is clearly broken...

Code:
C:\iperf-3.1.3-win64>iperf3.exe -R -V -t 15 -O 3 -c iperf.ct1.napafrica.net -u -b 10M
iperf 3.1.3
CYGWIN_NT-10.0 Nutty-PC 2.5.1(0.297/5/3) 2016-04-21 22:14 x86_64
Time: Sun, 05 Apr 2020 06:55:52 GMT
Connecting to host iperf.ct1.napafrica.net, port 5201
Reverse mode, remote host iperf.ct1.napafrica.net is sending
      Cookie: Nutty-PC.1586069752.242583.3775a5024
[  4] local 192.168.0.69 port 49757 connected to 196.10.99.34 port 5201
Starting Test: protocol: UDP, 1 streams, 8192 byte blocks, omitting 3 seconds, 15 second test
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-1.00   sec  1.23 MBytes  10.3 Mbits/sec  0.266 ms  1/159 (0.63%)  (omitted)
[  4]   1.00-2.00   sec  1.19 MBytes  9.95 Mbits/sec  0.122 ms  1/153 (0.65%)  (omitted)
[  4]   2.00-3.00   sec  1.16 MBytes  9.77 Mbits/sec  0.110 ms  3/152 (2%)  (omitted)
[  4]   0.00-1.00   sec  1.11 MBytes  9.31 Mbits/sec  0.103 ms  11/153 (7.2%)
[  4]   1.00-2.00   sec  1.19 MBytes  9.96 Mbits/sec  0.220 ms  0/152 (0%)
[  4]   2.00-3.00   sec  1.19 MBytes  9.94 Mbits/sec  0.294 ms  1/153 (0.65%)
[  4]   3.00-4.00   sec  1.20 MBytes  10.0 Mbits/sec  0.106 ms  0/153 (0%)
[  4]   4.00-5.00   sec  1.18 MBytes  9.89 Mbits/sec  0.156 ms  1/152 (0.66%)
[  4]   5.00-6.00   sec  1.10 MBytes  9.24 Mbits/sec  0.251 ms  12/153 (7.8%)
[  4]   6.00-7.00   sec  1.19 MBytes  9.97 Mbits/sec  0.100 ms  0/152 (0%)
[  4]   7.00-8.00   sec  1.20 MBytes  10.0 Mbits/sec  0.136 ms  0/153 (0%)
[  4]   8.00-9.00   sec  1.19 MBytes  9.98 Mbits/sec  0.195 ms  0/152 (0%)
[  4]   9.00-10.00  sec  1.20 MBytes  10.0 Mbits/sec  0.095 ms  0/153 (0%)
[  4]  10.00-11.00  sec  1.20 MBytes  10.0 Mbits/sec  0.127 ms  0/153 (0%)
[  4]  11.00-12.00  sec  1.18 MBytes  9.89 Mbits/sec  0.122 ms  1/152 (0.66%)
[  4]  12.00-13.00  sec  1.19 MBytes  9.97 Mbits/sec  0.130 ms  1/153 (0.65%)
[  4]  13.00-14.00  sec  1.16 MBytes  9.76 Mbits/sec  0.067 ms  2/151 (1.3%)
[  4]  14.00-15.00  sec  1.18 MBytes  9.89 Mbits/sec  0.057 ms  3/154 (1.9%)
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-15.00  sec  17.9 MBytes  10.0 Mbits/sec  0.067 ms  32/2290 (1.4%)
[  4] Sent 2290 datagrams
CPU Utilization: local/receiver 2.1% (0.7%u/1.4%s), remote/sender 0.7% (0.0%u/0.6%s)

iperf Done.

C:\iperf-3.1.3-win64>iperf3.exe -R -V -t 15 -O 3 -c iperf.ct1.napafrica.net -u -b 10M
iperf 3.1.3
CYGWIN_NT-10.0 Nutty-PC 2.5.1(0.297/5/3) 2016-04-21 22:14 x86_64
Time: Sun, 05 Apr 2020 08:52:23 GMT
Connecting to host iperf.ct1.napafrica.net, port 5201
Reverse mode, remote host iperf.ct1.napafrica.net is sending
      Cookie: Nutty-PC.1586076743.717497.77a6af3b3
[  4] local 192.168.0.69 port 56237 connected to 196.10.99.34 port 5201
Starting Test: protocol: UDP, 1 streams, 8192 byte blocks, omitting 3 seconds, 15 second test
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-1.00   sec  1.24 MBytes  10.4 Mbits/sec  0.156 ms  0/159 (0%)  (omitted)
[  4]   1.00-2.00   sec  1.18 MBytes  9.88 Mbits/sec  0.134 ms  2/153 (1.3%)  (omitted)
[  4]   2.00-3.00   sec  1.20 MBytes  10.0 Mbits/sec  0.139 ms  0/153 (0%)  (omitted)
[  4]   0.00-1.00   sec  1.16 MBytes  9.76 Mbits/sec  0.080 ms  3/152 (2%)
[  4]   1.00-2.00   sec  1.18 MBytes  9.90 Mbits/sec  0.096 ms  2/153 (1.3%)
[  4]   2.00-3.00   sec  1.17 MBytes  9.83 Mbits/sec  0.078 ms  3/153 (2%)
[  4]   3.00-4.00   sec  1.16 MBytes  9.75 Mbits/sec  0.100 ms  3/152 (2%)
[  4]   4.00-5.00   sec  1.19 MBytes  9.97 Mbits/sec  0.091 ms  1/153 (0.65%)
[  4]   5.00-6.00   sec  1.18 MBytes  9.90 Mbits/sec  0.230 ms  1/152 (0.66%)
[  4]   6.00-7.00   sec  1.18 MBytes  9.90 Mbits/sec  0.085 ms  2/153 (1.3%)
[  4]   7.00-8.00   sec  1.11 MBytes  9.31 Mbits/sec  0.147 ms  11/153 (7.2%)
[  4]   8.00-9.00   sec  1.17 MBytes  9.83 Mbits/sec  0.181 ms  2/152 (1.3%)
[  4]   9.00-10.00  sec  1.20 MBytes  10.0 Mbits/sec  0.171 ms  0/153 (0%)
[  4]  10.00-11.00  sec  1.18 MBytes  9.90 Mbits/sec  0.167 ms  1/152 (0.66%)
[  4]  11.00-12.00  sec  1.18 MBytes  9.89 Mbits/sec  0.082 ms  2/153 (1.3%)
[  4]  12.00-13.00  sec  1.11 MBytes  9.31 Mbits/sec  0.366 ms  10/152 (6.6%)
[  4]  13.00-14.00  sec  1.20 MBytes  10.0 Mbits/sec  0.065 ms  0/153 (0%)
[  4]  14.00-15.00  sec  1.20 MBytes  10.0 Mbits/sec  0.124 ms  0/153 (0%)
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-15.00  sec  17.9 MBytes  10.0 Mbits/sec  0.124 ms  41/2289 (1.8%)
[  4] Sent 2289 datagrams
CPU Utilization: local/receiver 1.7% (0.6%u/1.1%s), remote/sender 0.0% (0.0%u/0.0%s)

iperf Done.
 

Nutcracker

Active Member
Joined
Dec 19, 2005
Messages
56
Just an update on the latest. Clear, almost clean drop off after peak time.

1586154940273.png

Code:
C:\iperf-3.1.3-win64>iperf3.exe -R -V -t 15 -O 3 -c iperf.ct1.napafrica.net -u -b 85M
iperf 3.1.3
CYGWIN_NT-10.0 Nutty-PC 2.5.1(0.297/5/3) 2016-04-21 22:14 x86_64
Time: Sun, 05 Apr 2020 12:41:00 GMT
Connecting to host iperf.ct1.napafrica.net, port 5201
Reverse mode, remote host iperf.ct1.napafrica.net is sending
      Cookie: Nutty-PC.1586090460.390203.36fce97b4
[  4] local 192.168.0.69 port 52173 connected to 196.10.99.34 port 5201
Starting Test: protocol: UDP, 1 streams, 8192 byte blocks, omitting 3 seconds, 15 second test
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-1.00   sec  9.27 MBytes  77.6 Mbits/sec  0.314 ms  167/1353 (12%)  (omitted)
[  4]   1.00-2.00   sec  8.55 MBytes  71.8 Mbits/sec  0.356 ms  202/1297 (16%)  (omitted)
[  4]   2.00-3.00   sec  8.85 MBytes  74.3 Mbits/sec  0.400 ms  164/1297 (13%)  (omitted)
[  4]   0.00-1.00   sec  8.97 MBytes  75.2 Mbits/sec  0.431 ms  149/1297 (11%)
[  4]   1.00-2.00   sec  8.95 MBytes  75.0 Mbits/sec  0.435 ms  151/1296 (12%)
[  4]   2.00-3.00   sec  8.27 MBytes  69.4 Mbits/sec  0.361 ms  239/1298 (18%)
[  4]   3.00-4.00   sec  8.93 MBytes  74.9 Mbits/sec  0.464 ms  154/1297 (12%)
[  4]   4.00-5.00   sec  8.93 MBytes  74.9 Mbits/sec  0.541 ms  154/1297 (12%)
[  4]   5.00-6.00   sec  8.88 MBytes  74.4 Mbits/sec  0.517 ms  160/1296 (12%)
[  4]   6.00-7.00   sec  8.73 MBytes  73.3 Mbits/sec  0.465 ms  181/1298 (14%)
[  4]   7.00-8.00   sec  8.84 MBytes  74.1 Mbits/sec  0.471 ms  165/1296 (13%)
[  4]   8.00-9.00   sec  9.04 MBytes  75.8 Mbits/sec  0.426 ms  140/1297 (11%)
[  4]   9.00-10.00  sec  8.26 MBytes  69.2 Mbits/sec  0.487 ms  242/1299 (19%)
[  4]  10.00-11.00  sec  8.84 MBytes  74.2 Mbits/sec  0.448 ms  165/1297 (13%)
[  4]  11.00-12.00  sec  7.76 MBytes  65.1 Mbits/sec  0.932 ms  299/1292 (23%)
[  4]  12.00-13.00  sec  8.74 MBytes  73.3 Mbits/sec  0.380 ms  182/1301 (14%)
[  4]  13.00-14.00  sec  9.21 MBytes  77.2 Mbits/sec  0.370 ms  120/1299 (9.2%)
[  4]  14.00-15.00  sec  9.05 MBytes  76.0 Mbits/sec  0.389 ms  137/1295 (11%)
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-15.00  sec   152 MBytes  85.3 Mbits/sec  0.381 ms  2638/19461 (14%)
[  4] Sent 19461 datagrams
CPU Utilization: local/receiver 4.5% (1.8%u/2.7%s), remote/sender 4.0% (0.3%u/3.7%s)

iperf Done.

C:\iperf-3.1.3-win64>iperf3.exe -R -V -t 15 -O 3 -c iperf.ct1.napafrica.net -u -b 10M
iperf 3.1.3
CYGWIN_NT-10.0 Nutty-PC 2.5.1(0.297/5/3) 2016-04-21 22:14 x86_64
Time: Sun, 05 Apr 2020 19:57:01 GMT
Connecting to host iperf.ct1.napafrica.net, port 5201
Reverse mode, remote host iperf.ct1.napafrica.net is sending
      Cookie: Nutty-PC.1586116621.782512.5795892c6
[  4] local 192.168.0.69 port 63478 connected to 196.10.99.34 port 5201
Starting Test: protocol: UDP, 1 streams, 8192 byte blocks, omitting 3 seconds, 15 second test
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-1.00   sec   992 KBytes  8.11 Mbits/sec  0.417 ms  35/159 (22%)  (omitted)
[  4]   1.00-2.00   sec  1.01 MBytes  8.46 Mbits/sec  0.281 ms  24/153 (16%)  (omitted)
[  4]   2.00-3.00   sec   880 KBytes  7.20 Mbits/sec  0.351 ms  40/150 (27%)  (omitted)
[  4]   0.00-1.00   sec   864 KBytes  7.07 Mbits/sec  0.466 ms  47/155 (30%)
[  4]   1.00-2.00   sec   936 KBytes  7.67 Mbits/sec  0.450 ms  36/153 (24%)
[  4]   2.00-3.00   sec   960 KBytes  7.87 Mbits/sec  0.461 ms  32/152 (21%)
[  4]   3.00-4.00   sec   960 KBytes  7.86 Mbits/sec  0.836 ms  27/147 (18%)
[  4]   4.00-5.00   sec   952 KBytes  7.80 Mbits/sec  1.645 ms  39/158 (25%)
[  4]   5.00-6.00   sec   992 KBytes  8.13 Mbits/sec  0.459 ms  29/153 (19%)
[  4]   6.00-7.00   sec   904 KBytes  7.40 Mbits/sec  1.759 ms  40/153 (26%)
[  4]   7.00-8.00   sec  1008 KBytes  8.26 Mbits/sec  0.821 ms  26/152 (17%)
[  4]   8.00-9.00   sec  1.04 MBytes  8.72 Mbits/sec  0.670 ms  19/152 (12%)
[  4]   9.00-10.00  sec   976 KBytes  7.98 Mbits/sec  0.360 ms  31/153 (20%)
[  4]  10.00-11.00  sec   992 KBytes  8.13 Mbits/sec  0.391 ms  29/153 (19%)
[  4]  11.00-12.00  sec  1.02 MBytes  8.60 Mbits/sec  0.448 ms  22/153 (14%)
[  4]  12.00-13.00  sec  1008 KBytes  8.25 Mbits/sec  1.054 ms  26/152 (17%)
[  4]  13.00-14.00  sec  1.05 MBytes  8.79 Mbits/sec  0.393 ms  19/153 (12%)
[  4]  14.00-15.00  sec  1.04 MBytes  8.73 Mbits/sec  1.151 ms  19/152 (12%)
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-15.00  sec  17.9 MBytes  10.0 Mbits/sec  1.152 ms  441/2292 (19%)
[  4] Sent 2292 datagrams
CPU Utilization: local/receiver 1.0% (0.3%u/0.6%s), remote/sender 0.0% (0.0%u/0.0%s)

iperf Done.

C:\iperf-3.1.3-win64>iperf3.exe -R -V -t 15 -O 3 -c iperf.ct1.napafrica.net -u -b 10M
iperf 3.1.3
CYGWIN_NT-10.0 Nutty-PC 2.5.1(0.297/5/3) 2016-04-21 22:14 x86_64
Time: Mon, 06 Apr 2020 06:33:44 GMT
Connecting to host iperf.ct1.napafrica.net, port 5201
Reverse mode, remote host iperf.ct1.napafrica.net is sending
      Cookie: Nutty-PC.1586154824.945653.7ef296665
[  4] local 192.168.0.69 port 55163 connected to 196.10.99.34 port 5201
Starting Test: protocol: UDP, 1 streams, 8192 byte blocks, omitting 3 seconds, 15 second test
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-1.00   sec  1.24 MBytes  10.4 Mbits/sec  8.560 ms  1/160 (0.62%)  (omitted)
[  4]   1.00-2.00   sec  1.19 MBytes  9.96 Mbits/sec  0.043 ms  0/152 (0%)  (omitted)
[  4]   2.00-3.00   sec  1.19 MBytes  9.96 Mbits/sec  0.058 ms  1/153 (0.65%)  (omitted)
[  4]   0.00-1.00   sec  1.17 MBytes  9.83 Mbits/sec  0.151 ms  2/152 (1.3%)
[  4]   1.00-2.00   sec  1.20 MBytes  10.0 Mbits/sec  0.876 ms  0/153 (0%)
[  4]   2.00-3.00   sec  1.20 MBytes  10.0 Mbits/sec  1.275 ms  0/153 (0%)
[  4]   3.00-4.00   sec  1.16 MBytes  9.69 Mbits/sec  0.382 ms  4/152 (2.6%)
[  4]   4.00-5.00   sec  1.20 MBytes  10.0 Mbits/sec  0.829 ms  0/153 (0%)
[  4]   5.00-6.00   sec  1.18 MBytes  9.90 Mbits/sec  0.144 ms  1/152 (0.66%)
[  4]   6.00-7.00   sec  1.20 MBytes  10.0 Mbits/sec  1.332 ms  0/153 (0%)
[  4]   7.00-8.00   sec  1.20 MBytes  10.0 Mbits/sec  0.697 ms  0/153 (0%)
[  4]   8.00-9.00   sec  1.19 MBytes  9.97 Mbits/sec  0.055 ms  0/152 (0%)
[  4]   9.00-10.00  sec  1.19 MBytes  9.96 Mbits/sec  0.172 ms  1/153 (0.65%)
[  4]  10.00-11.00  sec  1.18 MBytes  9.90 Mbits/sec  0.425 ms  1/152 (0.66%)
[  4]  11.00-12.00  sec  1.16 MBytes  9.76 Mbits/sec  0.351 ms  4/153 (2.6%)
[  4]  12.00-13.00  sec  1.16 MBytes  9.77 Mbits/sec  0.238 ms  3/152 (2%)
[  4]  13.00-14.00  sec  1.19 MBytes  9.96 Mbits/sec  0.107 ms  1/153 (0.65%)
[  4]  14.00-15.00  sec  1.18 MBytes  9.91 Mbits/sec  1.562 ms  1/152 (0.66%)
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-15.00  sec  17.9 MBytes  10.0 Mbits/sec  1.470 ms  18/2289 (0.79%)
[  4] Sent 2289 datagrams
CPU Utilization: local/receiver 0.9% (0.3%u/0.5%s), remote/sender 0.0% (0.0%u/0.0%s)

iperf Done.
I logged a ticket with Seacom/Macrolan yesterday but other than the automatic reply there has been no further comms. I'll check up on them today.
 

i.got~issues

Expert Member
Joined
Apr 21, 2011
Messages
4,273
Thanks for this...

With Octotel + Macrolan 50/50 fibre here, absolutely terrible throughput and whatnot for a while now... reassuring to know it is not me.

Will keep an eye on this thread.

Ta.
 

emptybruwer

Well-Known Member
Joined
Jul 8, 2008
Messages
474
I am with Rsaweb/vumatel. After the speed upgrade yesterday. Speed and spikes are to S, @t
 

Nutcracker

Active Member
Joined
Dec 19, 2005
Messages
56
Gotta love how this picture is taking shape:

1586199563458.png

Clear congestion during peak time. Now it is just a matter of finding the responsible party...
Still waiting on feedback on my ticket that was logged with Seacom. Didn't have time to call them today unfortunately.

Code:
C:\iperf-3.1.3-win64>iperf3.exe -R -V -t 15 -O 3 -c iperf.ct1.napafrica.net -u -b 10M
iperf 3.1.3
CYGWIN_NT-10.0 Nutty-PC 2.5.1(0.297/5/3) 2016-04-21 22:14 x86_64
Time: Mon, 06 Apr 2020 19:00:36 GMT
Connecting to host iperf.ct1.napafrica.net, port 5201
Reverse mode, remote host iperf.ct1.napafrica.net is sending
      Cookie: Nutty-PC.1586199636.280132.02edafc72
[  4] local 192.168.0.69 port 58341 connected to 196.10.99.34 port 5201
Starting Test: protocol: UDP, 1 streams, 8192 byte blocks, omitting 3 seconds, 15 second test
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-1.00   sec   712 KBytes  5.82 Mbits/sec  0.353 ms  69/158 (44%)  (omitted)
[  4]   1.00-2.00   sec   680 KBytes  5.57 Mbits/sec  0.382 ms  69/154 (45%)  (omitted)
[  4]   2.00-3.00   sec   808 KBytes  6.62 Mbits/sec  0.472 ms  48/149 (32%)  (omitted)
[  4]   0.00-1.00   sec   824 KBytes  6.75 Mbits/sec  0.281 ms  53/156 (34%)
[  4]   1.00-2.00   sec   760 KBytes  6.23 Mbits/sec  0.209 ms  56/151 (37%)
[  4]   2.00-3.00   sec   752 KBytes  6.16 Mbits/sec  0.431 ms  59/153 (39%)
[  4]   3.00-4.00   sec   856 KBytes  7.01 Mbits/sec  0.271 ms  46/153 (30%)
[  4]   4.00-5.00   sec   840 KBytes  6.88 Mbits/sec  0.224 ms  48/153 (31%)
[  4]   5.00-6.00   sec   792 KBytes  6.49 Mbits/sec  0.220 ms  53/152 (35%)
[  4]   6.00-7.00   sec   832 KBytes  6.82 Mbits/sec  0.239 ms  49/153 (32%)
[  4]   7.00-8.00   sec   720 KBytes  5.90 Mbits/sec  0.227 ms  63/153 (41%)
[  4]   8.00-9.00   sec   744 KBytes  6.09 Mbits/sec  0.227 ms  59/152 (39%)
[  4]   9.00-10.00  sec   648 KBytes  5.31 Mbits/sec  0.328 ms  69/150 (46%)
[  4]  10.00-11.00  sec   712 KBytes  5.83 Mbits/sec  0.907 ms  65/154 (42%)
[  4]  11.00-12.00  sec   808 KBytes  6.61 Mbits/sec  1.272 ms  52/153 (34%)
[  4]  12.00-13.00  sec   688 KBytes  5.64 Mbits/sec  1.446 ms  68/154 (44%)
[  4]  13.00-14.00  sec   632 KBytes  5.18 Mbits/sec  0.441 ms  73/152 (48%)
[  4]  14.00-15.00  sec   584 KBytes  4.79 Mbits/sec  0.458 ms  75/148 (51%)
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-15.00  sec  17.9 MBytes  10.0 Mbits/sec  0.458 ms  888/2287 (39%)
[  4] Sent 2287 datagrams
CPU Utilization: local/receiver 1.0% (0.7%u/0.3%s), remote/sender 0.0% (0.0%u/0.0%s)

iperf Done.

C:\iperf-3.1.3-win64>iperf3.exe -R -V -t 15 -O 3 -c iperf.ct1.napafrica.net -u -b 85M
iperf 3.1.3
CYGWIN_NT-10.0 Nutty-PC 2.5.1(0.297/5/3) 2016-04-21 22:14 x86_64
Time: Mon, 06 Apr 2020 19:02:37 GMT
Connecting to host iperf.ct1.napafrica.net, port 5201
Reverse mode, remote host iperf.ct1.napafrica.net is sending
      Cookie: Nutty-PC.1586199757.521104.4b7ef2e12
[  4] local 192.168.0.69 port 59360 connected to 196.10.99.34 port 5201
Starting Test: protocol: UDP, 1 streams, 8192 byte blocks, omitting 3 seconds, 15 second test
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-1.00   sec  5.60 MBytes  46.9 Mbits/sec  0.801 ms  635/1352 (47%)  (omitted)
[  4]   1.00-2.00   sec  5.61 MBytes  47.1 Mbits/sec  0.495 ms  579/1297 (45%)  (omitted)
[  4]   2.00-3.00   sec  5.81 MBytes  48.7 Mbits/sec  0.600 ms  555/1299 (43%)  (omitted)
[  4]   0.00-1.00   sec  6.10 MBytes  51.2 Mbits/sec  0.474 ms  515/1296 (40%)
[  4]   1.00-2.00   sec  5.84 MBytes  49.0 Mbits/sec  0.414 ms  550/1298 (42%)
[  4]   2.00-3.00   sec  5.79 MBytes  48.5 Mbits/sec  0.774 ms  553/1294 (43%)
[  4]   3.00-4.00   sec  5.88 MBytes  49.4 Mbits/sec  0.849 ms  546/1299 (42%)
[  4]   4.00-5.00   sec  6.08 MBytes  50.9 Mbits/sec  0.870 ms  520/1298 (40%)
[  4]   5.00-6.00   sec  6.08 MBytes  51.0 Mbits/sec  0.600 ms  518/1296 (40%)
[  4]   6.00-7.00   sec  5.95 MBytes  49.8 Mbits/sec  0.949 ms  537/1298 (41%)
[  4]   7.00-8.00   sec  5.95 MBytes  49.9 Mbits/sec  0.623 ms  532/1293 (41%)
[  4]   8.00-9.00   sec  6.56 MBytes  55.1 Mbits/sec  0.514 ms  462/1302 (35%)
[  4]   9.00-10.00  sec  6.96 MBytes  58.4 Mbits/sec  0.747 ms  405/1296 (31%)
[  4]  10.00-11.00  sec  6.66 MBytes  55.8 Mbits/sec  0.389 ms  445/1297 (34%)
[  4]  11.00-12.00  sec  6.27 MBytes  52.6 Mbits/sec  0.428 ms  495/1297 (38%)
[  4]  12.00-13.00  sec  6.51 MBytes  54.6 Mbits/sec  0.483 ms  464/1297 (36%)
[  4]  13.00-14.00  sec  6.58 MBytes  55.2 Mbits/sec  0.517 ms  452/1294 (35%)
[  4]  14.00-15.00  sec  6.49 MBytes  54.5 Mbits/sec  0.460 ms  466/1297 (36%)
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-15.00  sec   152 MBytes  85.3 Mbits/sec  0.468 ms  7462/19457 (38%)
[  4] Sent 19457 datagrams
CPU Utilization: local/receiver 4.1% (1.3%u/2.8%s), remote/sender 0.7% (0.1%u/0.7%s)

iperf Done.
At least my speeds are looking somewhat better(so at least I can watch some Netflix and youtube), but I suspect that is just to the congestion being a little less overall at the moment.
 

HunterGR

Expert Member
Joined
Nov 30, 2011
Messages
2,141
Octotel is definitely on the blink..... CISP 50/50 business line on Octotel , Woodstock CPT, Business premises closed, Only one machine On (PBX)



Same Premises, backup (Seacom) Macrolan 25/25 on DFA , Same machine

 

Syphonx

Expert Member
Joined
Jun 25, 2008
Messages
3,639
Gotcha.

I don't believe SEACOM transit is the issue. The fact that I am seeing loss from my router to the ISP means that Octotel's ME network is most probably buckling under the pressure of the lockdown.
It's probably why they didn't over free upgrades unlike most of the other FNO's.
I am curious to know how what their backhaul capacity is to the area?
Actually... thinking about it now, the OLT or the PON port could be the issue as well.
Regardless, it would be good to get some feedback from Octotel.
If my problem persists, I'll log a ticket with SEACOM to log with Octotel for further investigation.
IIRC its 10-20Gbps for Blouberg area, but may have been upgraded further. Of course there are multiple hops where the congestion could occur, and the lockdown could have delayed upgrades.
 

Johnatan56

Honorary Master
Joined
Aug 23, 2013
Messages
26,575
IIRC its 10-20Gbps for Blouberg area, but may have been upgraded further. Of course there are multiple hops where the congestion could occur, and the lockdown could have delayed upgrades.
Counts as essential service, so shouldn't have delayed upgrades.
 

CrypticZA

Senior Member
Joined
Sep 21, 2019
Messages
820
Octotel will be performing emergency maintenance.

Date and Time: Tuesday, 7th April 2020, 16:00pm - 16:30pm
Affected Area
: Blouberg
Duration
: 10 Minutes
Upgrade description: Hardware upgrades.
Customer Impact: Residents will have intermittent connectivity during this
 
Top