Frogfoot Gpon FTTH Fibre Performance

I "showed interest" in vumatel, suburb still require 585 "interests". Here's hoping competition helps us get to meaningful solutions faster.

Damn, that's high, I'm showing over three hundred, They must have split Milnerton into Zones. :-(
I believe competition is good. Two FNO's can only be a good thing
 
Yeah FF did also, because Royal Ascott got Fibre 2 years before Milnerton Ridge
 
This is a very depressing thread. Webafrica swapped my account to something else yesterday which improved my throughput to about 6Mbps during the peak, but completely degraded my EU latency dropped the stability of it. Webafrica are apparently working/blaming Liquid Telecom for the international issues.

So now I have 6 out of a possible 100Mbps at the worst of times and a shitty ping all of the times, versus 1 out of a possible 100Mbps at the worst of times and a great ping 95% of the time... sighhh

Streaming at 1080p and a stable/consistent ping. I can't believe that is such a difficult service to deliver given :(

What exactly happened in Milnerton a month ago to cause this nightmare?


Re: What happened: FF say they voluntarily increased backbone with 40 Gig on the Milnerton/Burgandy etc link by upgrading a switch. That was the first story then it was maintenance so I am not sure what story they are going with.

I don't buy voluntary upgrades. No privately owned Telco company in the history of this country will drop cash on enterprise switching gear if they don't need to.

I assume they broke something or it was not properly configured before they went live.
I recon they will probably fix it on the quiet over the next few weeks.

I get and share your frustration. The little joy I have watching my US streaming shows has been taken away and replaced with buffering.

Update - Nap is testing @ 50% of my line speed, better than before. Something must be improving.

Code:
Connecting to host iperf.ct1.napafrica.net, port 5201
Reverse mode, remote host iperf.ct1.napafrica.net is sending
      Cookie: vurlkpesesjp6vzeyq54atlozp5tqk3qbc2r
      TCP MSS: 1448 (default)
[  6] local 10.0.0.154 port 63098 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  11.5 MBytes  96.8 Mbits/sec                  (omitted)
[  6]   1.00-2.00   sec  12.0 MBytes   101 Mbits/sec                  (omitted)
[  6]   2.00-3.00   sec  8.06 MBytes  67.6 Mbits/sec                  (omitted)
[  6]   0.00-1.00   sec  11.6 MBytes  97.5 Mbits/sec                 
[  6]   1.00-2.00   sec  12.8 MBytes   108 Mbits/sec                 
[  6]   2.00-3.00   sec  13.0 MBytes   109 Mbits/sec                 
[  6]   3.00-4.00   sec  13.3 MBytes   111 Mbits/sec                 
[  6]   4.00-5.00   sec  9.16 MBytes  76.8 Mbits/sec                 
[  6]   5.00-6.00   sec  10.9 MBytes  91.7 Mbits/sec                 
[  6]   6.00-7.00   sec  11.5 MBytes  96.2 Mbits/sec                 
[  6]   7.00-8.00   sec  8.04 MBytes  67.5 Mbits/sec                 
[  6]   8.00-9.00   sec  12.8 MBytes   108 Mbits/sec                 
[  6]   9.00-10.00  sec  9.05 MBytes  75.9 Mbits/sec                 
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval           Transfer     Bitrate         Retr
[  6]   0.00-10.00  sec   112 MBytes  94.2 Mbits/sec  362             sender
[  6]   0.00-10.00  sec   112 MBytes  94.2 Mbits/sec                  receiver
CPU Utilization: local/receiver 2.2% (0.4%u/1.8%s), remote/sender 0.0% (0.0%u/0.0%s)
snd_tcp_congestion cubic
 
Re: What happened: FF say they voluntarily increased backbone with 40 Gig on the Milnerton/Burgandy etc link by upgrading a switch. That was the first story then it was maintenance so I am not sure what story they are going with.

I don't buy voluntary upgrades. No privately owned Telco company in the history of this country will drop cash on enterprise switching gear if they don't need to.

I assume they broke something or it was not properly configured before they went live.
I recon they will probably fix it on the quiet over the next few weeks.

I get and share your frustration. The little joy I have watching my US streaming shows has been taken away and replaced with buffering.

Update - Nap is testing @ 50% of my line speed, better than before. Something must be improving.

Code:
Connecting to host iperf.ct1.napafrica.net, port 5201
Reverse mode, remote host iperf.ct1.napafrica.net is sending
      Cookie: vurlkpesesjp6vzeyq54atlozp5tqk3qbc2r
      TCP MSS: 1448 (default)
[  6] local 10.0.0.154 port 63098 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  11.5 MBytes  96.8 Mbits/sec                  (omitted)
[  6]   1.00-2.00   sec  12.0 MBytes   101 Mbits/sec                  (omitted)
[  6]   2.00-3.00   sec  8.06 MBytes  67.6 Mbits/sec                  (omitted)
[  6]   0.00-1.00   sec  11.6 MBytes  97.5 Mbits/sec                 
[  6]   1.00-2.00   sec  12.8 MBytes   108 Mbits/sec                 
[  6]   2.00-3.00   sec  13.0 MBytes   109 Mbits/sec                 
[  6]   3.00-4.00   sec  13.3 MBytes   111 Mbits/sec                 
[  6]   4.00-5.00   sec  9.16 MBytes  76.8 Mbits/sec                 
[  6]   5.00-6.00   sec  10.9 MBytes  91.7 Mbits/sec                 
[  6]   6.00-7.00   sec  11.5 MBytes  96.2 Mbits/sec                 
[  6]   7.00-8.00   sec  8.04 MBytes  67.5 Mbits/sec                 
[  6]   8.00-9.00   sec  12.8 MBytes   108 Mbits/sec                 
[  6]   9.00-10.00  sec  9.05 MBytes  75.9 Mbits/sec                 
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval           Transfer     Bitrate         Retr
[  6]   0.00-10.00  sec   112 MBytes  94.2 Mbits/sec  362             sender
[  6]   0.00-10.00  sec   112 MBytes  94.2 Mbits/sec                  receiver
CPU Utilization: local/receiver 2.2% (0.4%u/1.8%s), remote/sender 0.0% (0.0%u/0.0%s)
snd_tcp_congestion cubic
Test with UDP, just add - u, will show datagrams.
 
100/100Mbps line, still have to watch YT video in 480p because I can't get over 500Kbps consistently due to packet loss, so YT keeps downgrading it randomly. /slow clap for FF.
Code:
Connecting to host iperf.ct1.napafrica.net, port 5201
Reverse mode, remote host iperf.ct1.napafrica.net is sending
      Cookie: Lenovo-PC.1566675374.594759.27bb36dd
[  4] local 192.168.0.110 port 52684 connected to 196.10.99.34 port 5201
Starting Test: protocol: UDP, 1 streams, 1460 byte blocks, omitting 3 seconds, 15 second test
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-1.00   sec  7.65 MBytes  64.1 Mbits/sec  0.218 ms  1004/6496 (15%)  (omitted)
[  4]   1.00-2.00   sec  7.71 MBytes  64.6 Mbits/sec  0.229 ms  1055/6589 (16%)  (omitted)
[  4]   2.00-3.00   sec  7.85 MBytes  65.9 Mbits/sec  0.230 ms  1449/7089 (20%)  (omitted)
[  4]   0.00-1.00   sec  8.46 MBytes  70.9 Mbits/sec  0.211 ms  693/6767 (10%)  
[  4]   1.00-2.00   sec  7.68 MBytes  64.5 Mbits/sec  0.197 ms  1402/6917 (20%)  
[  4]   2.00-3.00   sec  8.51 MBytes  71.3 Mbits/sec  0.238 ms  730/6843 (11%)  
[  4]   3.00-4.00   sec  7.57 MBytes  63.5 Mbits/sec  0.191 ms  1399/6833 (20%)  
[  4]   4.00-5.00   sec  8.82 MBytes  74.0 Mbits/sec  0.239 ms  637/6975 (9.1%)  
[  4]   5.00-6.00   sec  7.36 MBytes  61.8 Mbits/sec  0.226 ms  1424/6709 (21%)  
[  4]   6.00-7.00   sec  8.81 MBytes  73.8 Mbits/sec  0.226 ms  713/7038 (10%)  
[  4]   7.00-8.00   sec  7.04 MBytes  59.0 Mbits/sec  0.251 ms  1585/6638 (24%)  
[  4]   8.00-9.00   sec  9.00 MBytes  75.5 Mbits/sec  0.244 ms  729/7191 (10%)  
[  4]   9.00-10.00  sec  6.84 MBytes  57.4 Mbits/sec  0.200 ms  1572/6488 (24%)  
[  4]  10.00-11.00  sec  8.92 MBytes  74.8 Mbits/sec  0.234 ms  829/7238 (11%)  
[  4]  11.00-12.00  sec  6.93 MBytes  58.1 Mbits/sec  0.244 ms  1471/6446 (23%)  
[  4]  12.00-13.00  sec  9.12 MBytes  76.5 Mbits/sec  0.229 ms  774/7323 (11%)  
[  4]  13.00-14.00  sec  6.93 MBytes  58.1 Mbits/sec  0.224 ms  1380/6355 (22%)  
[  4]  14.00-15.00  sec  9.21 MBytes  77.3 Mbits/sec  0.192 ms  708/7324 (9.7%)  
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-15.00  sec   143 MBytes  80.0 Mbits/sec  0.186 ms  16046/103143 (16%)  
[  4] Sent 103143 datagrams
CPU Utilization: local/receiver 19.0% (4.1%u/14.9%s), remote/sender 0.1% (0.0%u/0.1%s)
 
Test with UDP, just add - u, will show datagrams.

AFRIHOST UDP 08:30 AM

Code:
Stephens-Mac:~ stephen$ iperf3 -4 -V -R -t 10 -O 3 -u -b 80M -l 1440 -c iperf.ct1.napafrica.net
iperf 3.6
Darwin Stephens-Mac.local 19.0.0 Darwin Kernel Version 19.0.0: Fri Aug  9 21:59:46 PDT 2019; root:xnu-6153.0.139.161.2~2/RELEASE_X86_64 x86_64
Control connection MSS 1448
Time: Sun, 25 Aug 2019 06:31:51 GMT
Connecting to host iperf.ct1.napafrica.net, port 5201
Reverse mode, remote host iperf.ct1.napafrica.net is sending
      Cookie: cjwnw3dz6hjrnxpupx3mw4niersl6o6m47ny
[  6] local 10.0.0.154 port 60545 connected to 196.10.99.34 port 5201
Starting Test: protocol: UDP, 1 streams, 1440 byte blocks, omitting 3 seconds, 10 second test, tos 0
[ ID] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
[  6]   0.00-1.00   sec  6.93 MBytes  58.1 Mbits/sec  0.194 ms  1379/6422 (21%)  (omitted)
[  6]   1.00-2.00   sec  9.27 MBytes  77.8 Mbits/sec  0.240 ms  670/7421 (9%)  (omitted)
[  6]   1.00-1.00   sec  9.22 MBytes  38.7 Mbits/sec  0.198 ms  2056/13865 (15%) 
[  6]   1.00-2.00   sec  7.11 MBytes  59.6 Mbits/sec  0.782 ms  1279/6456 (20%) 
[  6]   2.00-3.00   sec  9.26 MBytes  77.7 Mbits/sec  0.216 ms  670/7416 (9%) 
[  6]   3.00-4.00   sec  7.03 MBytes  58.9 Mbits/sec  0.209 ms  642/5758 (11%) 
[  6]   4.00-5.00   sec  9.25 MBytes  77.6 Mbits/sec  0.193 ms  1381/8114 (17%) 
[  6]   5.00-6.00   sec  7.03 MBytes  59.0 Mbits/sec  0.227 ms  639/5761 (11%) 
[  6]   6.00-7.00   sec  9.41 MBytes  78.9 Mbits/sec  0.215 ms  1265/8117 (16%) 
[  6]   7.00-8.00   sec  6.97 MBytes  58.5 Mbits/sec  0.236 ms  688/5763 (12%) 
[  6]   8.00-9.00   sec  9.25 MBytes  77.6 Mbits/sec  0.197 ms  1374/8108 (17%) 
[  6]   9.00-10.00  sec  6.90 MBytes  57.9 Mbits/sec  0.234 ms  711/5739 (12%) 
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
[  6]   0.00-10.00  sec  95.4 MBytes  80.0 Mbits/sec  0.000 ms  0/70007 (0%)  sender
[  6]   0.00-10.00  sec  81.4 MBytes  68.3 Mbits/sec  0.234 ms  9350/68647 (14%)  receiver
CPU Utilization: local/receiver 5.0% (1.0%u/4.0%s), remote/sender 6.5% (0.9%u/5.6%s)

iperf Done.
Stephens-Mac:~ stephen$

This is bad, really bad, going to report to Afrihost. UDP test conducted @ 80% of line capacity.
 
100/100Mbps line, still have to watch YT video in 480p because I can't get over 500Kbps consistently due to packet loss, so YT keeps downgrading it randomly. /slow clap for FF.
Code:
Connecting to host iperf.ct1.napafrica.net, port 5201
Reverse mode, remote host iperf.ct1.napafrica.net is sending
      Cookie: Lenovo-PC.1566675374.594759.27bb36dd
[  4] local 192.168.0.110 port 52684 connected to 196.10.99.34 port 5201
Starting Test: protocol: UDP, 1 streams, 1460 byte blocks, omitting 3 seconds, 15 second test
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-1.00   sec  7.65 MBytes  64.1 Mbits/sec  0.218 ms  1004/6496 (15%)  (omitted)
[  4]   1.00-2.00   sec  7.71 MBytes  64.6 Mbits/sec  0.229 ms  1055/6589 (16%)  (omitted)
[  4]   2.00-3.00   sec  7.85 MBytes  65.9 Mbits/sec  0.230 ms  1449/7089 (20%)  (omitted)
[  4]   0.00-1.00   sec  8.46 MBytes  70.9 Mbits/sec  0.211 ms  693/6767 (10%)
[  4]   1.00-2.00   sec  7.68 MBytes  64.5 Mbits/sec  0.197 ms  1402/6917 (20%)
[  4]   2.00-3.00   sec  8.51 MBytes  71.3 Mbits/sec  0.238 ms  730/6843 (11%)
[  4]   3.00-4.00   sec  7.57 MBytes  63.5 Mbits/sec  0.191 ms  1399/6833 (20%)
[  4]   4.00-5.00   sec  8.82 MBytes  74.0 Mbits/sec  0.239 ms  637/6975 (9.1%)
[  4]   5.00-6.00   sec  7.36 MBytes  61.8 Mbits/sec  0.226 ms  1424/6709 (21%)
[  4]   6.00-7.00   sec  8.81 MBytes  73.8 Mbits/sec  0.226 ms  713/7038 (10%)
[  4]   7.00-8.00   sec  7.04 MBytes  59.0 Mbits/sec  0.251 ms  1585/6638 (24%)
[  4]   8.00-9.00   sec  9.00 MBytes  75.5 Mbits/sec  0.244 ms  729/7191 (10%)
[  4]   9.00-10.00  sec  6.84 MBytes  57.4 Mbits/sec  0.200 ms  1572/6488 (24%)
[  4]  10.00-11.00  sec  8.92 MBytes  74.8 Mbits/sec  0.234 ms  829/7238 (11%)
[  4]  11.00-12.00  sec  6.93 MBytes  58.1 Mbits/sec  0.244 ms  1471/6446 (23%)
[  4]  12.00-13.00  sec  9.12 MBytes  76.5 Mbits/sec  0.229 ms  774/7323 (11%)
[  4]  13.00-14.00  sec  6.93 MBytes  58.1 Mbits/sec  0.224 ms  1380/6355 (22%)
[  4]  14.00-15.00  sec  9.21 MBytes  77.3 Mbits/sec  0.192 ms  708/7324 (9.7%)
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-15.00  sec   143 MBytes  80.0 Mbits/sec  0.186 ms  16046/103143 (16%)
[  4] Sent 103143 datagrams
CPU Utilization: local/receiver 19.0% (4.1%u/14.9%s), remote/sender 0.1% (0.0%u/0.1%s)


Same I am a bit of a YouTube Junkie and my videos are defaulting to 480, I force to 1080 and then they buffer.
@Johnatan56 don't you remember when all the ads said: NO BUFFERING as a selling point of Fibre
 
FAQ from the FNNO Operator website.

ff_faq.png

Maybe we should ad a FAQ line.

Q

What happens if something goes wrong with my line speeds, are you able to diagnose and troubleshoot, restoring my service to normal?


A

Well you see these are home lines, so we don't really care. You're all dumb users with little technical knowledge so we know you can't test these things properly.

Even if you can we will first waste three weeks of your life accusing you of being stupid, not testing correctly, and force you to your ISP. If sending numerous test results to your ISP that we first ignore does not break your spirit then we will just flat out ignore you. We'll keep doing this until you go away.

:rolleyes:

EDIT: Frogfoot is currently testing and troubleshooting, Maybe they could provide an update. Suppose they will once done.
 
Last edited:
There is something up according to Afrihost: here is the tech support reply. There are looking into it. Not sure if its FF or Afrihost. Will let you know once its resolved.


704119
 
FAQ from the FNNO Operator website.

View attachment 704115

Maybe we should ad a FAQ line.

Q

What happens if something goes wrong with my line speeds, are you able to diagnose and troubleshoot, restoring my service to normal?


A

Well you see these are home lines, so we don't really care. You're all dumb users with little technical knowledge so we know you can't test these things properly.

Even if you can we will first waste three weeks of your life accusing you of being stupid, not testing correctly, and force you to your ISP. If sending numerous test results to your ISP that we first ignore does not break your spirit then we will just flat out ignore you. We'll keep doing this until you go away.

:rolleyes:

EDIT: Frogfoot is currently testing and troubleshooting, Maybe they could provide an update. Suppose they will once done.
GPON is not at fault, this is purely FF implementation issue.
There is one dude at FF, he's a dude that keeps calling, told me "yeah, we fixed it and want to run a test your side to make sure it's fixed", so I asked when fixed, dude couldn't give me a time, and after running tests he says to me that the results are "inconclusive", which is BS as you get instant results and you already know what you're testing for. Obviously my packet loss was still there.

There are the professional networking people at FF, then there are the business people who will keep saying they fixed it, any issue is on your side, passing the buck, and thinking that we can be kept in the dark even though it us that are suffering from the issue, we are the ones paying for their mistakes.

Anyways, I'll make sure they release me from contract end of month if they can't deliver, I've had enough, this has been ongoing for 6 months, 2 months with my current ISP.
704177

It's sad though as it's not my ISP at fault, it's FF, and they're damaging the reputation of the ISP for those who don't know better, e.g. like with TT Connect.
 
GPON is not at fault, this is purely FF implementation issue.
There is one dude at FF, he's a dude that keeps calling, told me "yeah, we fixed it and want to run a test your side to make sure it's fixed", so I asked when fixed, dude couldn't give me a time, and after running tests he says to me that the results are "inconclusive", which is BS as you get instant results and you already know what you're testing for. Obviously my packet loss was still there.

There are the professional networking people at FF, then there are the business people who will keep saying they fixed it, any issue is on your side, passing the buck, and thinking that we can be kept in the dark even though it us that are suffering from the issue, we are the ones paying for their mistakes.

Anyways, I'll make sure they release me from contract end of month if they can't deliver, I've had enough, this has been ongoing for 6 months, 2 months with my current ISP.
View attachment 704177

It's sad though as it's not my ISP at fault, it's FF, and they're damaging the reputation of the ISP for those who don't know better, e.g. like with TT Connect.

This is a valid point. Worth exploring.
 
Anybody know the latest on the Frogfoot issue affecting PE and CPT, which started on Fri, 23 Aug at 3pm?
Afrihost is reporting the issue on their website\app, but I don't see it on the Frogfoot network status page?
 
Hi guys

I see that there was a major Frogfoot outage on Friday, so that might have affected some of the users in this thread. However, if you can connect and are not getting a good experience on the Afrihost network, then it's something we need to troubleshoot on our side. Generally speaking, issues like latency and packet loss should also occur on other providers, becuase the backbone is the same - we haven't been seeing anything in general.

But please PM if you are having problems with Afrihost connections. If there is a common issue, we can collate the info and submit to Frogfoot for further investigation :(
 
Noice.

I'm in the Sunningdale area and I've got a 20/20 line. Up until Friday, I made peace with the fact that in reality I could only expect about half of that at any given time. Guess I'll need to set my expectations even lower now?

I have no other Fibre options in my area. Telkom ADSL is looking rather attractive again, as much as it pains me to say that out loud.
 
Hi guys

I see that there was a major Frogfoot outage on Friday, so that might have affected some of the users in this thread. However, if you can connect and are not getting a good experience on the Afrihost network, then it's something we need to troubleshoot on our side. Generally speaking, issues like latency and packet loss should also occur on other providers, becuase the backbone is the same - we haven't been seeing anything in general.

But please PM if you are having problems with Afrihost connections. If there is a common issue, we can collate the info and submit to Frogfoot for further investigation :(

Hello AfriMan, still a problem. the Facebook thread is exploding. All different ISPs.
Can you provide us with feedback AfriMan?

Code:
Stephens-Mac:~ stephen$ iperf3 -4 -V -R -t 10 -O 3 -u -b 80M -l 1440 -c iperf.ct1.napafrica.net
iperf 3.6
Darwin Stephens-Mac.local 19.0.0 Darwin Kernel Version 19.0.0: Fri Aug  9 21:59:46 PDT 2019; root:xnu-6153.0.139.161.2~2/RELEASE_X86_64 x86_64
Control connection MSS 1448
Time: Mon, 26 Aug 2019 08:17:03 GMT
Connecting to host iperf.ct1.napafrica.net, port 5201
Reverse mode, remote host iperf.ct1.napafrica.net is sending
      Cookie: zemsh72azxve4l3mxm4fx7dxyp2hptftg4mr
[  6] local 10.0.0.154 port 64271 connected to 196.10.99.34 port 5201
Starting Test: protocol: UDP, 1 streams, 1440 byte blocks, omitting 3 seconds, 10 second test, tos 0
[ ID] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
[  6]   0.00-1.00   sec  6.79 MBytes  56.9 Mbits/sec  0.190 ms  1484/6425 (23%)  (omitted)
[  6]   1.00-2.00   sec  9.32 MBytes  78.2 Mbits/sec  0.206 ms  622/7408 (8.4%)  (omitted)
[  6]   2.00-3.00   sec  7.06 MBytes  59.2 Mbits/sec  0.213 ms  1315/6456 (20%)  (omitted)
[  6]   0.00-1.00   sec  9.29 MBytes  77.9 Mbits/sec  0.206 ms  651/7417 (8.8%) 
[  6]   1.00-2.00   sec  6.99 MBytes  58.6 Mbits/sec  1.001 ms  1357/6446 (21%) 
[  6]   2.00-3.00   sec  9.29 MBytes  78.0 Mbits/sec  0.225 ms  654/7421 (8.8%) 
[  6]   3.00-4.00   sec  6.99 MBytes  58.7 Mbits/sec  0.233 ms  692/5784 (12%) 
[  6]   4.00-5.00   sec  9.29 MBytes  77.9 Mbits/sec  0.217 ms  1312/8078 (16%) 
[  6]   5.00-6.00   sec  7.41 MBytes  62.2 Mbits/sec  0.211 ms  555/5953 (9.3%) 
[  6]   6.00-7.00   sec  9.20 MBytes  77.2 Mbits/sec  0.191 ms  1200/7898 (15%) 
[  6]   7.00-8.00   sec  7.14 MBytes  59.9 Mbits/sec  0.231 ms  600/5802 (10%) 
[  6]   8.00-9.00   sec  9.24 MBytes  77.5 Mbits/sec  0.221 ms  1355/8082 (17%) 
[  6]   9.00-10.00  sec  6.97 MBytes  58.4 Mbits/sec  0.205 ms  700/5773 (12%) 
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
[  6]   0.00-10.00  sec  95.4 MBytes  80.0 Mbits/sec  0.000 ms  0/69983 (0%)  sender
[  6]   0.00-10.00  sec  81.8 MBytes  68.6 Mbits/sec  0.205 ms  9076/68654 (13%)  receiver
CPU Utilization: local/receiver 5.4% (1.1%u/4.3%s), remote/sender 1.8% (0.0%u/1.8%s)

iperf Done.
Stephens-Mac:~ stephen$
 
Noice.

I'm in the Sunningdale area and I've got a 20/20 line. Up until Friday, I made peace with the fact that in reality I could only expect about half of that at any given time. Guess I'll need to set my expectations even lower now?

I have no other Fibre options in my area. Telkom ADSL is looking rather attractive again, as much as it pains me to say that out loud.

@PandaB - that's the problem. ADSL is being pulled. So in Milnerton we also left just with Frogfoot or LTE.
Not looking good.
 
Top
Sign up to the MyBroadband newsletter
X