Starting shortly before 2025-08-19t17:05Z (10:05pm August 19 local time in Pakistan), a very large Internet outage occurred across all of Pakistan. Although not affecting all networks, in many areas 50% or more fo the networks are down, as shown in the following map:
We saw the first outages at 16:30Z, and they quickly ramped up to about half of the networks in most of the country. Since the network outages closely follow the country’s borders, it seems unlikely that this is a weather-related event. As of the time of this post (t20:00Z), the outage appears to be ongoing. We’ll post an update here when we learn more.
Some reports are suggesting it’s a backbone outage caused due to flooding.
We have released a new technical report: “Towards a Non-Binary View of IPv6 Adoption”, available at https://arxiv.org/abs/2507.11678.
From the abstract:
Breakdown of domains hosted by major cloud providers into IPv4-only (red), IPv6-only (black) and IPv6-full, i.e., IPv4+IPv6 (blue). See Section 5 of the technical report for details. (Figure 10 from the paper.)
Twelve years have passed since World IPv6 Launch Day, but what is the current state of IPv6 deployment? Prior work has examined IPv6 status as a binary: can you use IPv6, or not? As deployment increases we must consider a more nuanced, non-binary perspective on IPv6: how much and often can a user or a service use IPv6? We consider this question as a client, server, and cloud provider. Considering the client’s perspective, we observe user traffic. We see that the fraction of IPv6 traffic a user sends varies greatly, both across users and day-by-day, with a standard deviation of over 15%. We show this variation occurs for two main reasons. First, IPv6 traffic is primarily human-generated, thus showing diurnal patterns. Second, some services are IPv6-forward and others IPv6-laggards, so as users do different things their fraction of IPv6 varies. We look at server-side IPv6 adoption in two ways. First, we expand analysis of web services to examine how many are only partially IPv6 enabled due to their reliance on IPv4-only resources. Our findings reveal that only 12.5% of top 100k websites qualify as fully IPv6-ready. Finally, we examine cloud support for IPv6. Although all clouds and CDNs support IPv6, we find that tenant deployment rates vary significantly across providers. We find that ease of enabling IPv6 in the cloud is correlated with tenant IPv6 adoption rates, and recommend best practices for cloud providers to improve IPv6 adoption. Our results suggest IPv6 deployment is growing, but many services lag, presenting a potential for improvement.
This technical report is a joint work of Sulyab Thottungal Valapu from USC, and John Heidemann from USC/ISI. This work was partially supported by the NSF via the PIMAWAT and InternetMap projects.
