Speedchecker LinkedIn

Speed test datasets

SpeedChecker collects extensive amounts of speed test measurements world wide. The tests are collected according to our data collection and measurement methodology. We provide this data in a raw format specified below as well as integrated into our Crowdsourcing system for visual analysis.

Sample speed test dataset map visualization

speed test visualization

See the list of latest speed test reports

Speed test data format

ItemDescription
TestTimeDate and time of the measurement
DownloadSpeedResult of the download test in Mbps
DownloadTransferredMbNumber of MB transferred during download test
UploadSpeedResult of the upload test in Mbps
UploadTransferredMbNumber of MB transferred during upload test
PingTCP latency measurement result in milliseconds
JitterPing test results expressed as the difference between the highest and lowest individual ping results
OSTypeOperating system (Android or iOS)
ModelThe codename of the client's device created by its manufacturer.
ManufacturerThe manufacturer of the clients device and model information
Model2The model of the clients device. User friendly name
ActiveConnectionRadio access type of the connection (optional)
ConnectionTypeType of the internet connection the mobile device was connected to during the test (cellular or wifi)
UniqueIDpseudoanonymous ID of the user device
IPIP address of the device in the dotted quad format.
ISPInternet service provider of the user's connection
CountryCode2 letter ISO country code
LatUser device latitude
LonUser device longitude
lvl1_idID of the geographic region (state level)
lvl1_namename of the geographic region (state level)
lvl2_idID of the geographic region (district level)
lvl2_namename of the geographic region (district level)
ServerServer provider name (typically cloud or CDN name) used for download or upload test
ServerLocationNearest airport code to the measurement server location used for download or upload test
PingServerServer provider name (typically cloud or CDN name) used for ping test
PingServerLocationNearest airport code to the measurement server location used for ping test

Data collection methodology

Our data is collected from end user devices running Android and iOS systems. All measurements are executed towards a CDN that has a large geographical footprint and hosts a significant part of the content that is being accessed by the users. This ensures our results are a good approximation of the user’s actual quality of experience.

collection methodology

All measurements must contain accurate location information using GPS or wi-fi geolocation methods. Measurements are considered only from the apps that have been approved by SpeedChecker. Submitted measurements are checked to see if they are within expected ranges and additional security precautions are implemented to ensure measurement data is not being manipulated

The data collection process aims to deliver a single measurement sample from every device in our crowdsourcing system device pool and we strive to remove all duplicates. Due to privacy settings on some users phones we cannot reliably detect unique devices therefore some devices have contributed to more than 1 measurement into this dataset.

collection methodology

Measurement methodology

The methodology is based on the concept of the [ITU-T Q.3960 (2016)]
https://www.itu.int/itu-t/recommendations/rec.aspx?rec=q.3960

"Framework of Internet related performance measurements" and “Supplement 71 to ITU-T Q-series Recommendations”.

This test methodology aims at delivering an accurate measurement of the maximum bandwidth available over a given internet connection. This is achieved by transferring multiple parallel data streams over separate TCP connections within a predefined amount of time. The transferred data consists of randomly generated data with high entropy.

#ParameterUnitRangeCurrent Setting
1Number of parallel threads#1 ≤ n ≤ 10Dynamic addition from 1 to 10
2Duration of pre-tests0 ≤ Tp ≤ 51s
3Duration of the downlink tests5 ≤ Td ≤ 155s
4Duration of the uplink subtests5 ≤ Tu ≤ 155s
5Number of 'pings' during delay subtest#5 ≤ p ≤ 20p = 10
Contact us for more information