{"id":190,"date":"2020-05-18T14:04:41","date_gmt":"2020-05-18T14:04:41","guid":{"rendered":"https:\/\/blog.mozilla.org\/data\/?p=190"},"modified":"2020-05-20T14:02:18","modified_gmt":"2020-05-20T14:02:18","slug":"sharing-data-on-italys-mid-pandemic-internet-outage","status":"publish","type":"post","link":"https:\/\/blog.mozilla.org\/data\/2020\/05\/18\/sharing-data-on-italys-mid-pandemic-internet-outage\/","title":{"rendered":"Sharing data on Italy\u2019s mid-pandemic internet outage"},"content":{"rendered":"

As a data engineer at Mozilla, my colleagues and I study how internet connectivity changes over time and across regions. Like inclement weather, network outages are simply a fact of life: equipment that powers the internet can fail for numerous reasons in any country. As we know from reports of internet shutdowns and throttling<\/a> by governments in different parts of the world, sometimes outages can also be intentional. But in terms of data, Mozilla measures outages and connection issues through a series of different metrics, including telemetry upload failures.<\/p>\n

Today, we are releasing an aggregate open dataset<\/a> (italy_covid19_outage<\/em>) to show what one example of an outage looks like.<\/p>\n

In Italy, for several hours on March 11, 2020 \u2013 just days after a nationwide COVID-19 lockdown was declared \u2013 life on the internet came to a partial halt for a portion of the country. From news reports (1<\/a>, 2<\/a>) we know that one of the biggest Italian internet service providers, TIM, experienced an internet outage. Many customers of the ISP were unable to use a number of applications requiring network connectivity, and many websites were unreachable.<\/p>\n

As someone living in a small town in Italy, I experienced firsthand the anxiety of losing my connection to the internet in the middle of the pandemic. When out stocking up at the pharmacy a few days after the lockdown was declared, I tried to reach out to my wife over the phone. She wasn\u2019t picking up, so I messaged her over WhatsApp. That didn\u2019t work either. I tried to video call, and that failed. Because my wife\u2019s phone was connected to our WiFi router at home, and due to the technical details of our setup, the outage brought down most of the connectivity on her phone without her noticing.<\/p>\n

So what happened in Italy, exactly? TIM released a statement to the press<\/a> mentioning \u201ca failure on a \u201cforeign network\u201d resulting in some websites and apps hosted abroad to be unavailable. Because of that failure, people like me experienced congestion on the internet \u2013 as though suddenly hitting traffic on a highway that is normally clear. In my case, it wasn\u2019t that WhatsApp was down. It was that the VPN at my house stopped working properly due to connectivity issues, leaving me feeling isolated at the pharmacy during a tense moment.<\/p>\n

In a crisis like this one, any internet outage can be truly unsettling. It adds an edge to the anxiety we may already be experiencing. As the COVID-19 pandemic is forcing entire countries to lock down and practice social distancing, the internet offers people around the world the comfort to stay connected. At Mozilla, we have witnessed this firsthand: our telemetry<\/a> from the Firefox browser shows how more people are spending far more time online<\/a>.<\/p>\n

Mozilla can measure outages and connection issues through telemetry upload failures \u2013 we send small amounts of telemetry called \u201chealth ping<\/a>\u201d that report errors in uploading our normal telemetry data, but does not identify the users who have contributed this information. You can think of this small amount of data as a motorcycle on a congested highway, weaving between cars stuck in traffic. If there is an internet congestion that keeps WhatsApp or Facebook from working properly, for instance, the health pings sent to our servers often still get through, giving us information about whether the browser has connectivity issues.<\/p>\n

In Italy on March 11, we can see clear signals that Firefox users experienced an increase of network timeouts<\/i>. This means a device sent a request to a server, and waited beyond what the browser allows, meaning the server didn\u2019t respond in a timely fashion.<\/p>\n

This is how it looked on our systems:<\/p>\n

\"Network<\/p>\n

The series in the graph represent two reasons why network connections to Mozilla\u2019s telemetry server failed (see detailed description below). For example, on March 11, we saw a sharp increase in reported \u201ctimeouts\u201d (up to ~6%), and terminated connections (up to ~11%). As it happens, this wasn\u2019t the only date with disruptions in Italy. We detected two other spikes in terminated connections, one in January and one in February, which is consistent with reports from the crowdsourced site Downdetector.it<\/a>.<\/p>\n

The outage data<\/h1>\n

The data we are releasing today includes aggregated Firefox Desktop data for Italy from the \u201chealth\u201d ping and some fields of the \u201cmain\u201d ping that were created between January 1, 2020 up until March 31, 2020. To make all of this possible while respecting the privacy of our users, all of our metrics go through an extensive public data-review process<\/a> before collection. Moreover, the different types of failures are aggregated by day. These counts are then normalized by the total number of active daily users, and this gives an indication of how broadly a network problem is affecting a larger percentage of Firefox desktop clients. To further make aggregates safer, days for which there are less than 5,000 samples are discarded and not reported.<\/p>\n

The code used to produce this data lives here<\/a>. The metadata and caveats for the dataset are accessible from here<\/a> (italy_covid19_outage<\/em>).<\/p>\n

Questions or feedback about the data can be directed to publicdata@mozilla.com<\/a>, and press inquiries to press@mozilla.com<\/a>.<\/p>\n

Acknowledgements<\/h2>\n

This article was written in collaboration with Saptarshi Guha, Solana Larsen, Jochai Ben-Avie, Hamilton Ulmer. Thanks to Chris Hutten-Czapski, Jesse McCrosky, Jeff Klukas, Mark Reid and others for reviewing the initial investigation queries and to Anna Scholtz for the help with the dataset generation. And to Andrea Marchesini, for help navigating the Firefox network code and explaining the behaviour of each failure type.<\/p>\n","protected":false},"excerpt":{"rendered":"

As a data engineer at Mozilla, my colleagues and I study how internet connectivity changes over time and across regions. Like inclement weather, network outages are simply a fact of … Read more<\/a><\/p>\n","protected":false},"author":1538,"featured_media":192,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[315988,323282],"tags":[448303,448305,448304],"coauthors":[],"_links":{"self":[{"href":"https:\/\/blog.mozilla.org\/data\/wp-json\/wp\/v2\/posts\/190"}],"collection":[{"href":"https:\/\/blog.mozilla.org\/data\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.mozilla.org\/data\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.mozilla.org\/data\/wp-json\/wp\/v2\/users\/1538"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.mozilla.org\/data\/wp-json\/wp\/v2\/comments?post=190"}],"version-history":[{"count":0,"href":"https:\/\/blog.mozilla.org\/data\/wp-json\/wp\/v2\/posts\/190\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.mozilla.org\/data\/wp-json\/wp\/v2\/media\/192"}],"wp:attachment":[{"href":"https:\/\/blog.mozilla.org\/data\/wp-json\/wp\/v2\/media?parent=190"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.mozilla.org\/data\/wp-json\/wp\/v2\/categories?post=190"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.mozilla.org\/data\/wp-json\/wp\/v2\/tags?post=190"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/blog.mozilla.org\/data\/wp-json\/wp\/v2\/coauthors?post=190"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}