M-Lab to the Cloud: Virtual sites in all Google Cloud regions
As of April 2023, we are excited to announce that M-Lab has a virtual site running ndt-server in all 35 GCP regions.
M-Lab to the Cloud
M-Lab is excited to announce “M-Lab to the Cloud”, beginning with our pilot deployment of NDT servers on cloud infrastructure.
Wehe Measurement Service Launched on M-Lab Platform
The M-Lab team is excited to officially announce the launch of the Wehe measurement service on the platform. Working closely with the Wehe research team headed by David Choffnes, Associate Professor at Northeastern University, M-Lab launched the new measurement service, which is focused on net neutrality, in late 2020. The French telecom regulator, Arcep, announced their integration of Wehe in December.
The new ndt7 protocol for the Network Diagnostic Tool (NDT) is now generally available on the M-Lab platform. Since 2009, NDT has been the premier TCP performance measurement service test hosted by M-Lab. During its history on the platform, NDT has produced the largest test volume to date, spanning the longest history. Since late 2018, M-Lab has worked with researcher Simone Basso to develop the ndt7 protocol and archival data format.
New FQDNs for Experiments
If you have integrated NDT into a client that does not use our Locate Service, please be aware of the following change. If your NDT client uses our Locate Service, you should not notice a change.
Fully Qualified Domain Names for M-Lab experiments will be changing soon.
Recent updates regarding the SamKnows experiment
Measurement Lab (M-Lab) has been a supportive partner of the FCC’s Measuring Broadband America program since its beginning due to the program’s commitment to openness, open data and transparency which aligns closely with M-Lab’s mission around open data and open source internet measurement. Measurement Lab began hosting the SamKnows server-side measurement tools in 2009.
As of February 14, 2020, Measurement Lab is unable to host the SamKnows experiment due to SamKnows’ decision to not comply with M-Lab’s long-standing open source requirements. To ensure and encourage transparency for the MBA program, we are publishing this post to document the timeline leading up to that decision.
The 2.0 Platform Has Landed -- Thank you!
After years of planning and steady development, the new M-Lab 2.0 platform has landed. We want to express special thanks to those who have supported the project and helped us get here.
M-Lab 2.0 Platform: Global Pilot Assessment
We deployed the new M-Lab platform to 1/3rd of the M-Lab fleet, and now we need to assess whether or not it is a performance regression, relative to the old platform. As long as we can be sure the performance of the new platform does not constitute a regression, then we can roll out the new platform and be confident that we have not made anything worse.
M-Lab 2.0 Platform: Global Pilot Entry
For a while, we’ve been developing M-Lab 2.0 [1, 2]. This month, we are launching a global pilot for the new software stack. The changes include:
- Stock Linux 4.19 LTS kernels with modern TCP and Cubic congestion control
- Standard instrumentation for all experiments using tcp-info
- Virtualization and container management using Kubernetes and Docker
- Reimplementation of the NDT server
M-Lab 2.0 Platform Migration Update
Last year, we outlined our plans to Modernize the M-Lab Platform. This year, we’re bringing them to life. Here’s a summary of why the platform update is so valuable and what you can expect throughout the year.
Update: Paris Traceroute bug from Early 2018
In December 2017, M-Lab was notified of oddities in the Paris Traceroute data, which we then wrote about in January 2018. Upon investigation, a bug in the Paris Traceroute code was identified. The bug caused bad measurement data in 2.7% of the traceroutes since July 2016.
Paris Traceroute has a bug, and it causes some bad data
In December 2017, M-Lab was notified of oddities in the Paris Traceroute data. Upon investigation, a bug in the Paris Traceroute code was identified. The bug caused bad measurement data in 2.7% of the traceroutes since July 2016.
Modernizing the M-Lab Platform
When the M-Lab platform was initially launched in 2009, the software and operating system running on our servers used the best available boot management, virtualization, and kernel-level measurement instrumentation available. In the years since M-Lab’s initial launch, the state of system administration has improved dramatically. In 2017, the M-Lab team began work to upgrade the platform to adopt modern and flexible system administration components. This post provides a roadmap of that work.
Transitioning to a New Backend Pipeline and Data Availability
M-Lab data is collected from distributed experiments hosted on servers all over the world, processed in a pipeline, and published for free in both raw and parsed (structured) formats. The back end processing component for this has served us well for many years, but it’s been showing its age recently. As M-Lab collects an increasing amount of data thanks to new partnerships, we have been concerned that it will not be as reliable.
Paris Traceroute Brownout
In February 2017, M-Lab was notified of issues with the M-Lab data available in BigQuery. Upon investigation, a problem was identified with the Paris Traceroute collection daemon which resulted in a reduction in Paris Traceroute measurements beginning in June 2016. At the peak of the outage, fourth quarter 2016 - January 2017, approximately 5% of NDT tests had an associated Paris Traceroute test. Additionally, an issue within the data processing pipeline resulted in Paris Traceroute data that was measured and collected, not being inserted into the BigQuery tables and therefore available for use.
Traffic Microbursts and their Effect on Internet Measurement
In August 2015, M-Lab was notified of potential degradation of site performance by a measurement partner based on discrepancies compared to results for their own servers. After a full investigation these patterns were found to have been caused by the unique confluence of several specific conditions. Interim remediation measures were taken in early October 2015, and the resolution of the degradation was confirmed by the partner and others. Due to these administrative actions, the episode, which we are calling the “switch discard issue,” has not affected testing conducted in the United States (the region impacted by this problem) since October 11, 2015, and thus measurements after this period are not affected by the incident. M-Lab has also conducted an evaluation of data collected during the time period in which the issue occurred, and has taken steps to remove affected measurements from its dataset. This incident will not affect use of its dataset, past or present, as a result.