Tutela Technologies Ltd. (“Tutela”) declares itself in compliance with the 2020 Code of Conduct established by Arcep, in concert with the ecosystem’s stakeholders, for the design of Tutela’s test protocols and the aggregate publication of the resulting measurements.
Every measurement tool wanting to declare its compliance with the Code of conduct must complete and publish the Table from annex 1 containing information on its measurement methodologies.
| Measurement protocol | HTTPS |
| TCP or UDP port used | TCP 443 |
| Number of connections used simultaneously during the speed test | Single |
| Length of each test (provided the volume threshold has not been reached) | Variable time taken to download the test file. Most tests are 2MB or 5MB in size although a smaller number of tests are conducted with 10MB file sizes. The timeout delay for the Download test is 25 seconds, 15 seconds for the Upload test. |
| Maximum volume of data exchanged | 50MB |
| Speed test stream encryption | HTTPS |
| Information on whether or not slow start has been removed | Not removed |
| Version of the Internet Protocol (IP) and selection method used | Both, decided between the device and the network and CDN |
| Explanations of the displayed indicators | Download Throughput The measured download throughput on the current wireless connection. The download throughput is measuring the duration it takes to download a file (typically 2MB or 5MB) from Tutela CDN test server over a TCP connection. 2MB is selected to simulate loading a webpage or beginning a video session. Upload Throughput The measured upload throughput on the current wireless connection. The upload throughput is calculated by measuring the duration it takes to upload a 1MB file to a Tutela test server over a TCP connection. 1MB is selected to simulate uploading a medium definition image to social media. |
| Measurement protocol | UDP and ICMP The Metro Ethernet Forum (MEF) 10 specification is used to calculate the latency |
| TCP or UDP port used | UDP 10050 |
| Number of latency unit tests (if overall time-out has not expired) | 100 packets |
| Number of bytes typically exchanged for each latency unit test | 32 bytes |
| Length of the time-out in seconds, for each latency unit test | 5 seconds |
| Length of the time-out in seconds, for all latency test | 5 seconds |
| Latency test stream encryption | No encryption, just test bytes over UDP |
| Version of the Internet Protocol (IP) and selection method used | Both, decided between the device and the network and CDN |
| Explanations of the displayed indicators | The median measured latency on the current wireless connection. The latency is calculated as half of the round-trip duration of sending a UDP packet to a Tutela test server. UDP is selected to simulate latency sensitive applications, such as video and VoIP calling. Additional detail is available here: https://support.tutela.com/hc/en-us/articles/115001790249-UDP-Latency-Jitter-and-Packet-Loss-Test-Methodology |
| List of the URLs of the websites used | n/a |
| Length of the time-out in seconds, for each web browsing unit test | n/a |
| Length of the time-out in seconds, for all web browsing tests | n/a |
| Web cache status | n/a |
| Explanations of the displayed indicators | n/a |
| Video platforms tested and resolutions (if the resolution is set in advance) | n/a |
| Number of videos tested and selection method | n/a |
| Length of each video test | n/a |
| Length of the time-out in seconds, for each video streaming unit test | n/a |
| Explanations of the displayed indicators | n/a |
| Generic information given to users on factors that might influence the different measurements, notably speed, web browsing and video streaming | Crowdsourced data is inherently weighted to populations where people and population reside. There is a bias to urban data but generally this is not seen as a sharp rise or bias in the data. Tutela measures the end to end experience and measures from the actual device to one of the CDNs to test typical user experience. This simulates typical user download behaviour (downloading a web page). Tests are triggered by a timer, network change or location change. |
| Type of background tests performed | Tutela currently has five major test types: • Passive • Server Response • ICMP • Throughput • Video Each test type is run on a different frequency based on the end user impact. Passive tests are run very frequently, while throughput tests are run at most once every 24 hours. These frequencies are configurable but only changed rarely. Passive tests include all measurements taken directly from the device through an API call and not a result of sending traffic over the network. The Active tests result from a measured payload sent over the network. |
Every measurement tool wanting to declare its compliance with the Code of conduct must complete and publish the table from annex 2 containing information on their test servers.
The three examples given in the table are provided solely for the purpose of illustration.
| Method for selecting the default test server | Download tests are performed using Amazon’s CloudFront, Google Cloud and Akamai Content Delivery Networks (CDNs) over HTTPS. This allows test files to be downloaded with a low latency through one of the edge test servers located around the world. This service is commonly used to host popular websites and other web applications. The payload is requested via URL. The actual end server that delivers the payload is determined by the CDN - each CDN service determines the closest edge test server to serve the download test file based on the IP address of the device. Some of the locations below have multiple servers. |
| Sponsor (optional) | City | Region | IPv4/IPv6 protocol | Connection capacity (not for CDNs | Port used | TCP congestion protocol (optional) | Host name | AS (Autonomous System) |
| Marseille | Provence-Alpes-Côte d'Azur | Both | 443 | Amazon CloudFront - d2763msf1wgvw2.cloudfront.net |
16509 |
| Sponsor (optional) | City | Region | IPv4/IPv6 protocol | Connection capacity (not for CDNs | Port used | TCP congestion protocol (optional) | Host name | AS (Autonomous System) |
| Marseille | Provence-Alpes-Côte d'Azur | Both | 443 | Google - storage.googleapis.com | 16509 |
Note: both Google and Amazon sites in Marseille host multiple servers.
| Sponsor (optional) | City | Region | IPv4/IPv6 protocol | Connection capacity (not for CDNs | Port used | TCP congestion protocol (optional) | Host name | AS (Autonomous System) |
| Aixesurvienne | Nouvelle-Aquitaine | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Andancette | Auvergne-Rhône-Alpes | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Angres | Hauts-de-France | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Annecy | Auvergne-Rhône-Alpes | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Arbois | Bourgogne-Franche-Comté | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Aubervilliers | Île-de-France | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Aubiere | Auvergne-Rhône-Alpes | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Bezannes | Grand Est | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Bollene | Provence-Alpes-Côte d'Azur | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Bonneval | Centre-Val de Loire | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Breviandes | Champagne-Ardenne | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Bruay | Hauts-de-France | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Bruguieres | Occitanie | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Buzancais | Centre-Val de Loire | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Carnoules | Provence-Alpes-Côte d'Azur | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Carvin | Hauts-de-France | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Casson | Pays de la Loire | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Comines | Hauts-de-France | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Compiegne | Picardy | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Corbenay | Bourgogne-Franche-Comté | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Corte | Corsica | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Courtenay | Centre-Val de Loire | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Deauville | Normandy | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Digoin | Saône-et-Loire | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Dreux | Région du Centre | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Echirolles | Auvergne-Rhône-Alpes | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Ermont | Val d'Oise | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Flevy | Grand Est | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Floirac | Occitanie | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Formerie | Hauts-de-France | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Fourques | Occitanie | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Grignan | Auvergne-Rhône-Alpes | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Hennebont | Brittany | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Lacq | Nouvelle-Aquitaine | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Lagrandemotte | Occitanie | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Lehaillan | Nouvelle-Aquitaine | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Lescale | Lescale | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Lespinasse | Provence-Alpes-Côte d'Azur | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Lespins | Nouvelle-Aquitaine | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Lessablesdolonne | Pays de la Loire | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Linselles | Hauts-de-France | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Longlaville | Grand Est | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Lor | Hauts-de-France | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Loriolsurdrome | Auvergne-Rhône-Alpes | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Luxeuillesbains | Bourgogne-Franche-Comté | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Malville | Brittany | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Marennes | Poitou-Charentes | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Marseille | Provence-Alpes-Côte d'Azur | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Montsaintaignan | Normandy | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Moretsurloing | Île-de-France | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Nanterre | Île-de-France | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Nogentsurmarne | Île-de-France | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Ouistreham | Normandy | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Palaiseau | Île-de-France | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Paris | Île-de-France | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Phalsbourg | Grand Est | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Piscop | Île-de-France | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Plessisbouchard | Île-de-France | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Pontoise | Île-de-France | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Quincyvoisins | Île-de-France | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Romaneche | Bourgogne | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Saintalban | Brittany | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Saintandredapchon | Auvergne-Rhône-Alpes | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Saintesteve | Occitanie | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Saintfons | Auvergne-Rhône-Alpes | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Saintsauveur | Provence-Alpes-Côte d'Azur | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Saintvallier | Auvergne-Rhône-Alpes | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Toul | Grand Est | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Tressin | Hauts-de-France | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Uxegney | Grand Est | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Vannes | Brittany | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Vanves | Île-de-France | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Varney | Grand Est | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Vaux | Grand Est | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Velizy | Île-de-France | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Verrie | Pays de la Loire | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Villepinte | Occitanie | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Vittel | Grand Est | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 | |||
| Wittelsheim | Grand Est | Both | 443 | Akamai - qt-edge.akamaized.net | 20940 |
At Tutela we take data privacy seriously and do not collect any sensitive personal information. Please read our Privacy Charter (PDF) to learn more. Opt out (Do Not Sell My Info)
+1 (855) 6-TUTELA
