Speed.cloudflare.com
Cloudflare: 455 Mbps down / 73.1 Mbps up / Latency 13.0 ms / Jitter 2.26 ms / Server: Ashburn via IPv6.<p>Netflix (fast.com): 790 Mbps down / 950 Mbps up / Latency 8 ms unloaded, 12 ms loaded / Server: Ashburn via IPv6.<p>Ookla (speedtest.net): 928 Mbps down / 938 Mbps up / Ping 1 ms / Server: Raleigh via IPv4.<p>DSL Reports (<a href="http://www.dslreports.com/speedtest" rel="nofollow">http://www.dslreports.com/speedtest</a>): 611 Mbps down / 929 Mbps up / ping 16-41ms / Servers: Houston, Dallas, Newcastle DE, Nashville TN, Dallas.<p>Location: Raleigh. Provider: AT&T fiber.<p>Test run using Safari, macOS 10.15.4, Thunderbolt Ethernet.<p>Edit: the small file sizes used for some of the tests seem to drag down the overall speed measurement quite a bit. It's biased against upload measurements too since there's download files sizes of 25MB and 100MB whereas upload tests only up to 10MB file size. But even there, something seems off. The upload measurements are much smaller for the same file sizes (e.g. 170 Mbps avg vs 7 Mbs average for a 10 kB file).<p>I question this methodology. I care most about my 1Gps when I'm downloading the latest version of Xcode or some other huge file. I guess the smaller sizes are to better emulate downloading web pages, but in that case, the latency is probably what matters more. Even with 1Gps, when I'm out in CA, sites typically feel faster.<p>Edit 2:<p>speedtest.googlefiber.net: 800-900 Mbps down / 800-900 Mbps up (multiple tests to servers in Charlotte, Raleigh, Atlanta, seems to bounce around each time I reload the page).<p>Speedtest (Ookla) with server manually set to Windstream in Ashburn, VA: 886 Mbps down, 900 Mbps up. Confirmed that my router is measuring the same amount, so Ookla isn't just making up these numbers.