wingnut771
Honorary Master
and no mention of last mile between customer and datacenter.Hmm.. FF rep last seen Saturday after posting that 1 and only response.
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
and no mention of last mile between customer and datacenter.Hmm.. FF rep last seen Saturday after posting that 1 and only response.
Hi FFValued Customers,
This is an official response from Frogfoot.
Frogfoot takes feedback seriously as Frogfoot is committed to be the fibre provider of choice, and we pride ourselves on putting the customer first.
Frogfoot supplies the ISP a connection between the home and Teraco Data Centre in Rondebosch. The ISP is then responsible for supplying internet bandwidth to the home user.
When investigating performance issues, there are usually various factors involved,
- User’s wifi connectivity.
- Device that is used for testing.
- The connection to the Teraco Data Centre.
- The ISP’s links to the internet.
- The ISP’s links between international ISPs.
- The capacity of servers to which the customer connects..
Frogfoot experienced capacity issues in the Milnerton, Parklands and Burgundy areas in early July 2019. This was resolved when the network capacity was upgraded on the evening of 8 July 2019.
There were also a few other individual reports of which the root cause was identified, for each case raised, and successfully resolved after confirming with the customer involved.
Recently Frogfoot has only had a report from a single ISP and has been working with this ISP for the past week to try and get to the bottom of these complaints.
Preliminary testing of the Frogfoot portion of the network has shown no issues. Frogfoot together with the ISP started installing extra testing points in 16 August 2019. Installing all the relevant testing points should be completed by 19 August 2019. Thereafter more testing will be done in order to narrow down the issue, based on the results and trends identified.
Frogfoot, together with this ISP’s assistance, is committed to get to the bottom of any issues that users have been experiencing.
Frogfoot encourages any users to please log speed related issues with their ISP. Please insist that the ISP supply you with a Frogfoot ticket number to confirm that it has been logged.
Kind Regards,
The Frogfoot Team


The GPON/Active Ethernet argument is generally moot as the uplink from the switch is also contended. The whole debate is overrated as both have pros and cons and if managed correctly shouldn't be much of a difference to the end user. Frogfoot is probably overcontended/oversubscribed at some point if the ISP is not to blame which is most likely causing the issue or there may be an issue with your physical strand - they should be able to test this though.
Okay time for some sharing, just like I promised I would. Seeing as though I was so vocal about this I am giving all the detail to be fair to Frogfoot as they are open access I'm sure they won't mind.
(In lay terms before I get flamed by the Godfathers of the internet for using the wrong lingo. ;-) )
There are two tests, the one is the Frogfoot layer two test and the other is speed tests and iperf to Teraco, will post that separate.
This is feedback from MY site, in Milnerton, I am not giving out my address for obvious reasons.
If you want to get closer its Milnerton central opposite Woodbridge Island. I connect to the Milpark Node, which is that really tall building in Milnerton on Koeberg Road. I have no idea of back-haul from the FF node to Teraco, I'm assuming its DFA, as they have the monopoly but that is an assumption.
Frogfoot sent out their network peeps yesterday. And installed a snazzy expensive looking piece of testing gear that looks like this:
View attachment 702957
Layer 2 testing equipment, obviously as they provide the layer2 and that is what all the fuss is about.
One ethernet port plugs into the ONT and the Other into your router/lan.
View attachment 702963
They accessed it remotely and performed tests. (3 were shared) They shared the results with my ISP, Atomic who they are working closely with. The tests were conducted during peak hours, i.e. after 20h00 pm as this is when the issues were reported.
The results were - "No packet loss on the tests they conducted from my location to Teraco." See test results file.
Here are the test results, all three merged into 1 file. Frogfoot-results
You'll see there's two ONT's in the pic. That's because I have installed another 100meg line through Afrihost to conduct the IPERF tests tonight after 20h00.
FF was here yesterday to install it, its a new Fibre that has been installed. There were problems with the route but senior Frogfoot techies arrived today to fix the route and get the link up. Thanks to FF tech support for sorting this out. Will post those results later.
The results were - "No packet loss on the tests they conducted from my location to Teraco." See test results file.
So if the line is not the issue what is? Packeloss is usually the main culprit with slow speeds on international.
Forgive my ignorance as I'm not familiar with that device but I'm assuming the status "Fail (3) - Frame loss failure (3)," is acceptable at 0.1% frame loss or not?
So if the line is not the issue what is? Packeloss is usually the main culprit with slow speeds on international.
Nice I see you have 2 linesMaybe I should get another 200Mbps Openserve line
![]()
So as you know Frogfoot tested the line their fancy testing device and cleared it as "no packet loss". Basically saying that I am full of sh*t with my 0.1% loss. So here't the layer three tests, very basic but best I know how to do from my Mac, wired connection. Cat6. Lan network idle.
Atomic line, 200 Meg connection, testing to Teraco cpt. I'm testing an perf server @ nap Africa in Teraco.
BEFORE PEAK (After 19h00)
Stephens-Mac:~ stephen$ iperf3 -R -4 -V -t 10 -O 3 -c iperf.ct1.napafrica.net
iperf 3.6
Darwin Stephens-Mac.local 19.0.0 Darwin Kernel Version 19.0.0: Tue Jul 23 01:19:36 PDT 2019; root:xnu-6153.0.103.151.1~4/RELEASE_X86_64 x86_64
Control connection MSS 1448
Time: Wed, 21 Aug 2019 17:25:43 GMT
Connecting to host iperf.ct1.napafrica.net, port 5201
Reverse mode, remote host iperf.ct1.napafrica.net is sending
Cookie: m4cbkuegwartrpdnjy4znubt3xi6ymd7gh2e
TCP MSS: 1448 (default)
[ 6] local 10.0.0.154 port 65320 connected to 196.10.99.34 port 5201
Starting Test: protocol: TCP, 1 streams, 131072 byte blocks, omitting 3 seconds, 10 second test, tos 0
[ ID] Interval Transfer Bitrate
[ 6] 0.00-1.00 sec 20.4 MBytes 171 Mbits/sec (omitted)
[ 6] 1.00-2.00 sec 22.1 MBytes 186 Mbits/sec (omitted)
[ 6] 2.00-3.00 sec 22.3 MBytes 187 Mbits/sec (omitted)
[ 6] 0.00-1.00 sec 22.8 MBytes 191 Mbits/sec
[ 6] 1.00-2.00 sec 22.6 MBytes 189 Mbits/sec
[ 6] 2.00-3.00 sec 22.6 MBytes 189 Mbits/sec
[ 6] 3.00-4.00 sec 22.6 MBytes 190 Mbits/sec
[ 6] 4.00-5.00 sec 22.7 MBytes 190 Mbits/sec
[ 6] 5.00-6.00 sec 22.7 MBytes 190 Mbits/sec
[ 6] 6.00-7.00 sec 20.9 MBytes 175 Mbits/sec
[ 6] 7.00-8.00 sec 20.5 MBytes 172 Mbits/sec
[ 6] 8.00-9.00 sec 22.6 MBytes 190 Mbits/sec
[ 6] 9.00-10.00 sec 22.3 MBytes 187 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval Transfer Bitrate Retr
[ 6] 0.00-10.00 sec 223 MBytes 187 Mbits/sec 130 sender
[ 6] 0.00-10.00 sec 222 MBytes 186 Mbits/sec receiver
CPU Utilization: local/receiver 14.2% (2.6%u/11.6%s), remote/sender 0.0% (0.0%u/0.0%s)
snd_tcp_congestion cubic
iperf Done.
Stephens-Mac:~ stephen$
During PEAK (20h51), still on Atomic, same server.
Stephens-Mac:~ stephen$ iperf3 -R -4 -V -t 10 -O 3 -c iperf.ct1.napafrica.net
iperf 3.6
Darwin Stephens-Mac.local 19.0.0 Darwin Kernel Version 19.0.0: Tue Jul 23 01:19:36 PDT 2019; root:xnu-6153.0.103.151.1~4/RELEASE_X86_64 x86_64
Control connection MSS 1448
Time: Wed, 21 Aug 2019 18:15:38 GMT
Connecting to host iperf.ct1.napafrica.net, port 5201
Reverse mode, remote host iperf.ct1.napafrica.net is sending
Cookie: p3beh2cezqqy72yq7zbakabegpw2t3bvfrh2
TCP MSS: 1448 (default)
[ 6] local 10.0.0.154 port 53524 connected to 196.10.99.34 port 5201
Starting Test: protocol: TCP, 1 streams, 131072 byte blocks, omitting 3 seconds, 10 second test, tos 0
[ ID] Interval Transfer Bitrate
[ 6] 0.00-1.00 sec 10.6 MBytes 89.1 Mbits/sec (omitted)
[ 6] 1.00-2.00 sec 16.6 MBytes 140 Mbits/sec (omitted)
[ 6] 2.00-3.00 sec 11.4 MBytes 95.4 Mbits/sec (omitted)
[ 6] 0.00-1.00 sec 11.8 MBytes 99.0 Mbits/sec
[ 6] 1.00-2.00 sec 8.07 MBytes 67.7 Mbits/sec
[ 6] 2.00-3.00 sec 14.8 MBytes 124 Mbits/sec
[ 6] 3.00-4.00 sec 10.3 MBytes 86.1 Mbits/sec
[ 6] 4.00-5.00 sec 10.5 MBytes 87.7 Mbits/sec
[ 6] 5.00-6.00 sec 6.84 MBytes 57.4 Mbits/sec
[ 6] 6.00-7.00 sec 6.86 MBytes 57.6 Mbits/sec
[ 6] 7.00-8.00 sec 10.6 MBytes 88.5 Mbits/sec
[ 6] 8.00-9.00 sec 11.3 MBytes 94.7 Mbits/sec
[ 6] 9.00-10.00 sec 9.19 MBytes 77.1 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval Transfer Bitrate Retr
[ 6] 0.00-10.00 sec 100 MBytes 84.0 Mbits/sec 387 sender
[ 6] 0.00-10.00 sec 100 MBytes 84.0 Mbits/sec receiver
CPU Utilization: local/receiver 3.1% (0.5%u/2.6%s), remote/sender 0.0% (0.0%u/0.0%s)
snd_tcp_congestion cubic
iperf Done.
Stephens-Mac:~ stephen$
Basically the speed halves during peak times. Draw your own conclusions.
If you add a -P 4 to add parallel connections - does the peak still show the same?
If you add a -P 4 to add parallel connections - does the peak still show the same?
Stephen O'Reilly, [21.08.19 21:42]
Stephens-Mac:~ stephen$ iperf3 -P 4 -R -4 -V -t 10 -O 3 -c iperf.ct1.napafrica.net
iperf 3.6
Darwin Stephens-Mac.local 19.0.0 Darwin Kernel Version 19.0.0: Tue Jul 23 01:19:36 PDT 2019; root:xnu-6153.0.103.151.1~4/RELEASE_X86_64 x86_64
Control connection MSS 1448
Time: Wed, 21 Aug 2019 19:39:33 GMT
Connecting to host iperf.ct1.napafrica.net, port 5201
Reverse mode, remote host iperf.ct1.napafrica.net is sending
Cookie: 2dqdci3gsuottkorsvqu54a74vux5lfmy6il
TCP MSS: 1448 (default)
[ 6] local 10.0.0.154 port 59874 connected to 196.10.99.34 port 5201
[ 8] local 10.0.0.154 port 59875 connected to 196.10.99.34 port 5201
[ 10] local 10.0.0.154 port 59876 connected to 196.10.99.34 port 5201
[ 12] local 10.0.0.154 port 59877 connected to 196.10.99.34 port 5201
Starting Test: protocol: TCP, 4 streams, 131072 byte blocks, omitting 3 seconds, 10 second test, tos 0
[ ID] Interval Transfer Bitrate
[ 6] 0.00-1.00 sec 5.54 MBytes 46.4 Mbits/sec (omitted)
[ 8] 0.00-1.00 sec 5.65 MBytes 47.4 Mbits/sec (omitted)
[ 10] 0.00-1.00 sec 5.84 MBytes 49.0 Mbits/sec (omitted)
[ 12] 0.00-1.00 sec 5.75 MBytes 48.2 Mbits/sec (omitted)
[SUM] 0.00-1.00 sec 22.8 MBytes 191 Mbits/sec (omitted)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 6] 1.00-2.00 sec 5.45 MBytes 45.7 Mbits/sec (omitted)
[ 8] 1.00-2.00 sec 5.74 MBytes 48.1 Mbits/sec (omitted)
[ 10] 1.00-2.00 sec 5.76 MBytes 48.3 Mbits/sec (omitted)
[ 12] 1.00-2.00 sec 5.77 MBytes 48.4 Mbits/sec (omitted)
[SUM] 1.00-2.00 sec 22.7 MBytes 191 Mbits/sec (omitted)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 6] 2.00-3.00 sec 5.49 MBytes 46.1 Mbits/sec (omitted)
[ 8] 2.00-3.00 sec 5.65 MBytes 47.4 Mbits/sec (omitted)
[ 10] 2.00-3.00 sec 5.85 MBytes 49.1 Mbits/sec (omitted)
[ 12] 2.00-3.00 sec 5.71 MBytes 47.9 Mbits/sec (omitted)
[SUM] 2.00-3.00 sec 22.7 MBytes 190 Mbits/sec (omitted)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 6] 0.00-1.00 sec 6.30 MBytes 52.9 Mbits/sec
[ 8] 0.00-1.00 sec 6.46 MBytes 54.2 Mbits/sec
[ 10] 0.00-1.00 sec 5.06 MBytes 42.5 Mbits/sec
[ 12] 0.00-1.00 sec 4.91 MBytes 41.1 Mbits/sec
[SUM] 0.00-1.00 sec 22.7 MBytes 191 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 6] 1.00-2.00 sec 6.13 MBytes 51.4 Mbits/sec
[ 8] 1.00-2.00 sec 6.56 MBytes 55.0 Mbits/sec
[ 10] 1.00-2.00 sec 4.99 MBytes 41.9 Mbits/sec
[ 12] 1.00-2.00 sec 5.02 MBytes 42.1 Mbits/sec
[SUM] 1.00-2.00 sec 22.7 MBytes 190 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 6] 2.00-3.00 sec 6.18 MBytes 51.8 Mbits/sec
[ 8] 2.00-3.00 sec 6.31 MBytes 52.9 Mbits/sec
[ 10] 2.00-3.00 sec 5.19 MBytes 43.6 Mbits/sec
[ 12] 2.00-3.00 sec 5.03 MBytes 42.2 Mbits/sec
[SUM] 2.00-3.00 sec 22.7 MBytes 191 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 6] 3.00-4.00 sec 5.66 MBytes 47.5 Mbits/sec
[ 8] 3.00-4.00 sec 5.79 MBytes 48.5 Mbits/sec
[ 10] 3.00-4.00 sec 4.81 MBytes 40.3 Mbits/sec
[ 12] 3.00-4.00 sec 6.39 MBytes 53.6 Mbits/sec
[SUM] 3.00-4.00 sec 22.6 MBytes 190 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 6] 4.00-5.00 sec 7.22 MBytes 60.6 Mbits/sec
[ 8] 4.00-5.00 sec 5.28 MBytes 44.3 Mbits/sec
Stephen O'Reilly, [21.08.19 21:42]
[ 10] 4.00-5.00 sec 4.42 MBytes 37.1 Mbits/sec
[ 12] 4.00-5.00 sec 5.90 MBytes 49.5 Mbits/sec
[SUM] 4.00-5.00 sec 22.8 MBytes 192 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 6] 5.00-6.00 sec 7.10 MBytes 59.5 Mbits/sec
[ 8] 5.00-6.00 sec 5.19 MBytes 43.5 Mbits/sec
[ 10] 5.00-6.00 sec 4.48 MBytes 37.6 Mbits/sec
[ 12] 5.00-6.00 sec 5.98 MBytes 50.1 Mbits/sec
[SUM] 5.00-6.00 sec 22.7 MBytes 191 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 6] 6.00-7.00 sec 6.75 MBytes 56.6 Mbits/sec
[ 8] 6.00-7.00 sec 5.31 MBytes 44.6 Mbits/sec
[ 10] 6.00-7.00 sec 4.63 MBytes 38.9 Mbits/sec
[ 12] 6.00-7.00 sec 6.04 MBytes 50.7 Mbits/sec
[SUM] 6.00-7.00 sec 22.7 MBytes 191 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 6] 7.00-8.00 sec 6.23 MBytes 52.2 Mbits/sec
[ 8] 7.00-8.00 sec 6.34 MBytes 53.2 Mbits/sec
[ 10] 7.00-8.00 sec 4.55 MBytes 38.2 Mbits/sec
[ 12] 7.00-8.00 sec 5.60 MBytes 47.0 Mbits/sec
[SUM] 7.00-8.00 sec 22.7 MBytes 191 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 6] 8.00-9.00 sec 6.57 MBytes 55.1 Mbits/sec
[ 8] 8.00-9.00 sec 5.55 MBytes 46.6 Mbits/sec
[ 10] 8.00-9.00 sec 4.84 MBytes 40.6 Mbits/sec
[ 12] 8.00-9.00 sec 5.74 MBytes 48.1 Mbits/sec
[SUM] 8.00-9.00 sec 22.7 MBytes 190 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 6] 9.00-10.00 sec 6.54 MBytes 54.9 Mbits/sec
[ 8] 9.00-10.00 sec 5.51 MBytes 46.2 Mbits/sec
[ 10] 9.00-10.00 sec 4.84 MBytes 40.6 Mbits/sec
[ 12] 9.00-10.00 sec 5.84 MBytes 49.0 Mbits/sec
[SUM] 9.00-10.00 sec 22.7 MBytes 191 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval Transfer Bitrate Retr
[ 6] 0.00-10.00 sec 64.6 MBytes 54.2 Mbits/sec 10 sender
[ 6] 0.00-10.00 sec 64.7 MBytes 54.3 Mbits/sec receiver
[ 8] 0.00-10.00 sec 58.4 MBytes 49.0 Mbits/sec 5 sender
[ 8] 0.00-10.00 sec 58.3 MBytes 48.9 Mbits/sec receiver
[ 10] 0.00-10.00 sec 47.5 MBytes 39.9 Mbits/sec 9 sender
[ 10] 0.00-10.00 sec 47.8 MBytes 40.1 Mbits/sec receiver
[ 12] 0.00-10.00 sec 56.5 MBytes 47.4 Mbits/sec 17 sender
[ 12] 0.00-10.00 sec 56.4 MBytes 47.3 Mbits/sec receiver
[SUM] 0.00-10.00 sec 227 MBytes 190 Mbits/sec 41 sender
[SUM] 0.00-10.00 sec 227 MBytes 191 Mbits/sec receiver
CPU Utilization: local/receiver 12.0% (2.0%u/10.0%s), remote/sender 0.3% (0.0%u/0.2%s)
snd_tcp_congestion cubic
iperf Done.
Stephens-Mac:~ stephen$
But even the normal one is back to normal, with the "p" and the "4" almost ten o clock, always gets back to normal.
Stephens-Mac:~ stephen$ iperf3 -R -4 -V -t 10 -O 3 -c iperf.ct1.napafrica.net
iperf 3.6
Darwin Stephens-Mac.local 19.0.0 Darwin Kernel Version 19.0.0: Tue Jul 23 01:19:36 PDT 2019; root:xnu-6153.0.103.151.1~4/RELEASE_X86_64 x86_64
Control connection MSS 1448
Time: Wed, 21 Aug 2019 19:43:29 GMT
Connecting to host iperf.ct1.napafrica.net, port 5201
Reverse mode, remote host iperf.ct1.napafrica.net is sending
Cookie: b7hpw6jjrga5fxipkxq5jry7ey6uvqpwvauv
TCP MSS: 1448 (default)
[ 6] local 10.0.0.154 port 60153 connected to 196.10.99.34 port 5201
Starting Test: protocol: TCP, 1 streams, 131072 byte blocks, omitting 3 seconds, 10 second test, tos 0
[ ID] Interval Transfer Bitrate
[ 6] 0.00-1.00 sec 22.2 MBytes 186 Mbits/sec (omitted)
[ 6] 1.00-2.00 sec 22.7 MBytes 191 Mbits/sec (omitted)
[ 6] 2.00-3.00 sec 22.7 MBytes 191 Mbits/sec (omitted)
[ 6] 0.00-1.00 sec 22.7 MBytes 191 Mbits/sec
[ 6] 1.00-2.00 sec 22.7 MBytes 191 Mbits/sec
[ 6] 2.00-3.00 sec 22.7 MBytes 191 Mbits/sec
[ 6] 3.00-4.00 sec 22.7 MBytes 191 Mbits/sec
[ 6] 4.00-5.00 sec 22.7 MBytes 191 Mbits/sec
[ 6] 5.00-6.00 sec 22.7 MBytes 191 Mbits/sec
[ 6] 6.00-7.00 sec 22.7 MBytes 191 Mbits/sec
[ 6] 7.00-8.00 sec 22.7 MBytes 191 Mbits/sec
[ 6] 8.00-9.00 sec 22.7 MBytes 191 Mbits/sec
[ 6] 9.00-10.00 sec 22.7 MBytes 191 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval Transfer Bitrate Retr
[ 6] 0.00-10.00 sec 228 MBytes 191 Mbits/sec 2 sender
[ 6] 0.00-10.00 sec 227 MBytes 191 Mbits/sec receiver
CPU Utilization: local/receiver 10.5% (2.0%u/8.5%s), remote/sender 0.0% (0.0%u/0.0%s)
snd_tcp_congestion cubic
iperf Done.
Stephens-Mac:~ stephen$