<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>Renesys Blog</title>
    <link rel="alternate" type="text/html" href="http://www.renesys.com/blog/" />
    <link rel="self" type="application/atom+xml" href="http://www.renesys.com/blog/atom.xml" />
    <id>tag:www.renesys.com,2008-10-18:/blog//1</id>
    <updated>2013-05-23T20:35:50Z</updated>
    
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.37</generator>

<entry>
    <title>&apos;Crecimiento&apos; in Latin America</title>
    <link rel="alternate" type="text/html" href="http://www.renesys.com/blog/2013/05/growth-in-latin-america.shtml" />
    <id>tag:www.renesys.com,2013:/blog//1.243</id>

    <published>2013-05-23T20:17:09Z</published>
    <updated>2013-05-23T20:35:50Z</updated>

    <summary> Two weeks ago, I had the great pleasure of visiting Medellin, Colombia to present at the Latin American and Caribbean Network Operators Group (LACNOG) portion of LACNIC 19. Medellin is a vibrant place, recently recognized as the world&apos;s most...</summary>
    <author>
        <name>Doug Madory</name>
        <uri>http://www.renesys.com</uri>
    </author>
    
        <category term="Latin America" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.renesys.com/blog/">
        <![CDATA[<table>
<tr><td>
<p>Two weeks ago, I had the great pleasure of visiting Medellin, Colombia to <a href="http://www.renesys.com/tech/presentations/pdf/lacnic19-madory.pdf">present</a> at the Latin American and Caribbean Network Operators Group (LACNOG) portion of <a href="http://www.lacnic.net/web/eventos/lacnic19-agenda">LACNIC 19</a>. Medellin is a vibrant place, recently recognized as the <a href="http://www.bbc.co.uk/news/world-latin-america-21638308">world's most innovative city</a> by the <a href="http://www.uli.org">Urban Land Institute</a> due to the city's investments in public infrastructure and civic spaces.</p>

</td><td>
<a href="http://www.renesys.com/blog/assets_c/2013/05/LACNIC19-1b-1078.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/05/LACNIC19-1b-1078.shtml','popup','width=268,height=106,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/05/LACNIC19-1b-thumb-300x118-1078.jpg" width="300" height="118" alt="LACNIC19-1b.jpg" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></a>
</td></tr></table>

<p>Perhaps equally innovative is Colombia's <a href="http://www.internexa.com/default.aspx">Internexa</a>, which in recent years has been building the region's first <em>international terrestrial</em> telecommunications network. Meanwhile, another remarkable regional story is the exponential growth of the domestic Internet in Brazil &mdash; especially when contrasted with the stagnation in Mexico. While government initiatives in Brazil, the region's largest economy, were able to foster much of its recent growth, the current regulatory overhaul in Mexico hopes to achieve something similar in the region's second largest economy.</p>

<strong><p>Internet Growth in Latin America</p></strong>

<p>In the presentation, I discussed where we <em>did</em> and <em>did not</em> see Internet growth (<em>crecimiento</em> in Spanish) in the Latin American region. To measure growth, I borrowed a metric, domestic ASN growth, from my colleague Jim Cowie's <a href="http://www.renesys.com/tech/presentations/pdf/menog12-cowie.pdf">recent presentation</a> on the growth of the Internet of the Middle East at <a href="http://www.menog.org/meetings/previous/menog-12/">MENOG 12</a> in Dubai.
</p>

<p>For each country, we counted up the number of domestic Autonomous Systems (ASNs), where an  <a href="http://en.wikipedia.org/wiki/Autonomous_System_(Internet)">ASN</a> is considered <em>domestic in a country</em> when at least 70% of its customer base is in that country. Of course, ASNs can vary dramatically in size, from large companies to small non-profits. But regardless of size, our metric accurately captures the "number of Internet players" in a country. It is the relative change in this count over time that is most informative, as shown in the following table for a subset of Latin American countries:
</p>

<a href="http://www.renesys.com/blog/assets_c/2013/05/latam_growth-table-1099.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/05/latam_growth-table-1099.shtml','popup','width=773,height=208,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/05/latam_growth-table-thumb-450x121-1099.png" width="450" height="121" alt="latam_growth-table.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></a>

<p>Our data illustrates very robust growth in Brazil, Argentina and Costa Rica since January 2010. During this period, Brazil grew by 340% and now exceeds the size of the rest of the region combined. <em>By this metric, Brazil adds the equivalent of two Mexicos to its domestic Internet each year.</em></p>

<em><strong><p>Costa Rica</p></strong></em>

<p>Dramatic growth of the Internet in Costa Rica is a result of the <a href="http://www.telegeography.com/products/commsupdate/articles/2008/06/09/liberalisation-law-signed/">telecommunications regulatory reform of 2008</a>. The reform was a requirement of the <a href="http://en.wikipedia.org/wiki/Dominican_Republic-Central_America_Free_Trade_Agreement">CAFTA-DR trade agreement</a>, which mandated that the government of Costa Rica end the monopoly of <a href="http://www.grupoice.com/wps/portal/">ICE</a>, set up a telecoms regulator <a href="http://sutel.go.cr">Sutel</a>, and allow new competition. Although Costa Rica was one of the smaller countries in our analysis, it had the largest relative growth in the region. New players in Costa Rica include <a href="http://www.telegeography.com/products/commsupdate/articles/2009/03/26/eight-companies-pass-first-hurdle-to-offer-telecoms-services/">new telecommunications providers</a> as well as new enterprises operating in the country.<p>

<em><strong><p>Brazil</p></strong></em>

<p>Brazil's tremendous growth has been a result of a national program of infrastructure investment and government incentives, which <a href="https://www.dropbox.com/sh/tdbgc0wffbg3iil/ugQkx9E7vr/Sesión%20de%20la%20mañana/Sala%20Antioquia/20130506-LACNIC_ArturCoimbra_interconexion_internacional.pptx">was described</a> at LACNIC 19 by <a href="http://www.mc.gov.br/o-ministerio/quem-e-quem/180-institucional/secretaria-de-telecomunicacoes/25198-perfil-diretor-do-departamento-de-banda-larga">Artur Coimbra</a> of the Brazilian Ministry of Communications. In addition to upgrading and expanding the domestic backbone of Telebras, Brazil has established <a href="http://www.ptt.br/localidades/atuais">22 municipal Internet exchange points</a> called PTTs (<em>Pontos de Troca de Tráfego</em>) to facilitate domestic exchange of Internet traffic.  In his presentation, Wardner Maia, President of the <a href="http://abrint.com.br"> Association of Brazilian Internet Providers (ABRINT) </a> discussed the recent explosion of <a href="https://www.dropbox.com/sh/tdbgc0wffbg3iil/2eJmfYuYPc/Sesión%20de%20la%20mañana/Sala%20Antioquia/Provedores%20Regionais-es_revisado.pdf">small regional Internet service providers</a> serving parts of Brazil that hadn't previously had access to the Internet. On average, he said, the Brazilian government was issuing over 700 licenses per year to these new providers, 78% percent of which are considered small companies. When we compared our data, it was clear that the growth of domestic ASNs matched the growth in licensing that his organization was witnessing. </p>

<p>We're not the only ones witnessing Brazil's growth. In their most recent <a href="http://www.akamai.com/stateoftheinternet/">State of the Internet</a> report, content provider <a href="http://www.akamai.com">Akamai</a> noted the largest year-to-year increase in unique IP addresses reaching their servers was from Brazil (a 33% increase).

<em><strong><p>Argentina</p></strong></em>

<table><tr><td style="vertical-align:top">
<p>Like Brazil, Argentina's growth was due to infrastructure development. A relatively competitive market like Brazil, Argentina also had a program of developing regional IXPs to foster domestic connectivity. Argentina's CABASE program has established <a href="http://www.cabase.org.ar/wordpress/naps-en-funcionamiento/">10 municipal IXPs</a> and is facilitating the growth we're seeing in that country.</p>

<p>This growth has vaulted Argentina past Mexico in the number of players in the domestic Internet. Argentina has the <a href="http://en.wikipedia.org/wiki/List_of_Latin_American_countries_by_GDP_(nominal)">third largest economy</a> in Latin America, behind Mexico and Brazil.</p>
</td><td>
<a href="http://www.renesys.com/blog/assets_c/2013/05/AR_MX.dat-1069.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/05/AR_MX.dat-1069.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/05/AR_MX.dat-thumb-300x257-1069.png" width="200" height="150" alt="AR_MX.dat.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></a>
</td></tr></table>

<p><em><strong>Mexico</strong></em></p>

<p>On the other end of the spectrum is Mexico, where we have observed negligible growth in its domestic Internet.</p>

<p>One of the least competitive markets in Latin America, Mexico is dominated by its incumbent <a href="http://en.wikipedia.org/wiki/Telmex">Telmex</a>. Last year, the <a href="http://www.oecd.org">OECD</a> concluded that, <a href="http://www.oecd.org/sti/broadband/50550219.pdf">"inefficient telecommunication markets impose a significant cost on the Mexican economy and the welfare of its population"</a> to the tune of US$129Bn per year or 1.8% of the GDP of Mexico.</p>

<p> The lack of competition is such a major problem that newly elected Mexican President <a href="http://en.wikipedia.org/wiki/Enrique_Peña_Nieto">Enrique Peña Nieto</a> has made telecom reform one of the key features of his <a href="http://pactopormexico.org/objetivos-de-la-reforma-de-telecomunicaciones/"><em>Pacto por México</em></a>. Among other measures, the legislation would cap market share at 50% and remove the limit on foreign ownership of telecommunications companies. Once instituted, the market share cap may require the break-up of Telmex and pit Peña Nieto against Telmex's owner and CEO, billionaire <a href="http://en.wikipedia.org/wiki/Carlos_Slim">Carlos Slim</a>, the <a href="http://en.wikipedia.org/wiki/Forbes_list_of_billionaires#2013_Top_10">richest man in the world</a>.
</p>

<p>As of this writing, the Mexican telecom reform has <a href="http://www.forbes.com/sites/doliaestevez/2013/05/01/mexicos-congress-passes-monopoly-busting-telecom-bill-threatening-tycoon-carlos-slims-business-empire/">passed both houses of congress</a> and has been <a href="http://www.bloomberg.com/news/2013-05-14/majority-of-mexico-states-approve-telecom-bill-official-says.html">ratified by a majority of Mexican states</a>. America Movil, the parent company of Telmex, has already warned shareholders that the new legislation could have a <a href="http://www.reuters.com/article/2013/04/30/us-mexico-americamovil-idUSBRE93T0RE20130430">material impact on its Mexican business</a>.
</p>

<p>In separate development, several mid-sized Mexican telecommunications companies have united to establish <a href="http://www.madeinmexicoinc.com/the-internet-exchange-point-ixp-in-mexico/">the first domestic Internet Exchange Point (IXP)</a> in Mexico, the only country in the OECD not to currently have one. However, without Telmex on board, the impact on Mexican domestic connectivity as a whole may be limited.</p>

<p>The regulatory reform in Mexico won't take effect until 2014. If Costa Rica can serve as a model of what to expect in Mexico, it may take a couple of years until we observe a meaningful increase in growth. However, given the size and richness of the Mexican economy, perhaps there is reason to believe that a long-awaited expansion could occur at a much faster rate once facilitated by this reform.</p>

<br>
<strong><p>Regional Terrestrial Connectivity</p></strong>

<p>In many parts of the world, the promise of regional terrestrial connectivity that directly connects neighboring countries has proven elusive. The Program for International Development in Africa (<a href="http://www.afdb.org/en/topics-and-sectors/initiatives-partnerships/programme-for-infrastructure-development-in-africa-pida/">PIDA</a>) has been pushing for this in Africa, while <a href="http://lirneasia.net/">LIRNEasia</a> has been advocating for the <a href="http://www.totaltele.com/view.aspx?ID=465754">same thing for South and Southeast Asia</a>. The <a href="http://www.gccix.net/aboutus/network-map.html">GCCIX project</a> has begun to address this in the Middle East. Without terrestrial connectivity, countries in these regions are reliant on submarine cables to carry their traffic to neighboring countries. This implies that Internet traffic must often traverse long distances to reach geographically close locations, resulting in longer latencies and poorer performance. In addition, submarine cables <a href="http://www.renesys.com/blog/2013/02/faraway-fallout-from-black-sea.shtml">occasionally</a> <a href="http://www.renesys.com/blog/2013/03/intrigue-surrounds-smw4-cut.shtml">suffer</a> <a href="http://www.renesys.com/blog/2012/07/large-outage-in-lebanon.shtml">faults</a> and undersea repairs take significantly more time than those on land.</p>

<table><tr><td style="vertical-align:top">
<p>Until recently, South America could also be defined much in the same way, but that is changing. Miami is still the common international connection point for Internet providers in Latin  America (Los Angeles and Dallas for Mexico). However, Colombian company <a href="http://www.capacitymagazine.com/Article/3026655/Internexa-Creating-an-IP-backbone-across-Latin-America.html?eventcookielogin=Login&cookielogin=1&actionname=cookielogin&eid=E017">Internexa</a> is leveraging the international network of power lines owned by its parent company <a href="http://www1.isa.com.co/irj/portal/anonymous?NavigationTarget=navurl://0422af976f9410393368e3670dc26437">ISA</a> to build the region's first multi-country terrestrial network (pictured at right). At LACNIC 19, Internexa <a href="https://www.dropbox.com/sh/etd1kqlr2mxpotp/jfhVpLVoBe/1%20Alejandro-escobar-InterconexiónregionalV3.pptx">presented statistics</a> about how much regional Internet traffic they are currently carrying that no longer needs to leave the continent in order to reach its destination. They currently have direct terrestrial connections between Brazil,  Argentina and Chile as well as between Venezuela, Colombia, Ecuador and Peru. Ultimately, their goal is to build a terrestrial network spanning all the countries of South America to provide the fastest and most direct service in the region.</p>
<p>
In my talk, I used the screenshots below from our upcoming product, Internet Business Intelligence, to illustrate which Internet provider combinations provided the lowest latency paths from the city hosting the conference (Medellin, Colombia) to nearby Quito, Ecuador. By eliminating the need to send Internet traffic out of the region, Internexa was the fastest option to Ecuador. When looking at performance over time in the graphic below and to the right, we can see that the Ecuadorian government-owned provider <a href="http://www.cnt.com.ec">Corporacion Nacional de Telecomunicaciones (CNT)</a> experienced some brief performance issues, while Internexa's subsidiary in Ecuador, <a href="http://www.transnexa.com">Transnexa</a>, provided the most stable low-latency path between these two cities during this time period.
</p>


</td><td>
<a href="http://www.renesys.com/blog/assets_c/2013/05/APR_MAY 2012_Co. Strategy_Internexa_revised-1063.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/05/APR_MAY 2012_Co. Strategy_Internexa_revised-1063.shtml','popup','width=300,height=300,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/05/APR_MAY 2012_Co. Strategy_Internexa_revised-thumb-300x302-1063.jpg" width="300" height="302" alt="APR_MAY 2012_Co. Strategy_Internexa_revised.jpg" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></a>
</td></tr></table>

<table><tr><td>
<a href="http://www.renesys.com/blog/assets_c/2013/05/ibi-1091.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/05/ibi-1091.shtml','popup','width=1416,height=1125,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/05/ibi-thumb-300x238-1091.png" width="300" height="238" alt="ibi.png" class="mt-image-center" style="text-align: center; display: block; margin: 20px 20px 20px;" /></a>

</td><td>
<a href="http://www.renesys.com/blog/assets_c/2013/05/ibi2-1094.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/05/ibi2-1094.shtml','popup','width=1417,height=1125,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/05/ibi2-thumb-300x238-1094.png" width="300" height="238" alt="ibi2.png" class="mt-image-center" style="text-align: center; display: block; margin: 20px 20px 20px;" /></a>

</td></tr></table>

<p><strong>Looking to the Future</strong></p>

<p>Developments such as Internexa's terrestrial network and Brazil's amazing Internet boom have been fascinating to observe. However, the most important story for the region in the coming years may be whether or not Peña Nieto is successful at breaking up Carlos Slim's Telmex and its grip on the Mexican telecom market. Solo el tiempo lo dirá &mdash; <em>only time will tell.</em></p>]]>
        
    </content>
</entry>

<entry>
    <title>Cuba-Jamaica Link Activated</title>
    <link rel="alternate" type="text/html" href="http://www.renesys.com/blog/2013/05/cuba-jamaica-link-activated.shtml" />
    <id>tag:www.renesys.com,2013:/blog//1.244</id>

    <published>2013-05-20T21:33:38Z</published>
    <updated>2013-05-23T20:45:55Z</updated>

    <summary> In January, we reported the news that the ALBA-1 submarine cable connecting Cuba to Venezuela had started carrying Internet traffic two years after its construction, answering the question of what happened to the mystery cable to Cuba. In the...</summary>
    <author>
        <name>Doug Madory</name>
        <uri>http://www.renesys.com</uri>
    </author>
    
        <category term="Caribbean" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Submarine Cables" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.renesys.com/blog/">
        <![CDATA[<table><tr><td style="vertical-align:top">
<p>In January, we <a href="http://www.renesys.com/blog/2013/01/cuban-mystery-cable-activated.shtml">reported the news</a> that the ALBA-1 submarine cable connecting Cuba to Venezuela had started carrying Internet traffic two years after its construction, answering the question of what happened to the <a href="http://latino.foxnews.com/latino/news/2012/05/21/cuba-mystery-over-undersea-internet-cable/">mystery</a> <a href="http://laredcubana.blogspot.com/2012/05/what-happened-to-alba-1-undersea-cable.html">cable</a> to <a href="http://globalvoicesonline.org/2013/01/10/what-happened-to-the-cable-cubans-discuss-internet-access/">Cuba</a>. </p>

<p>In the last week, we have observed a second non-satellite connection established for Cuban state telecom, <a href="http://www.etecsa.cu">ETECSA</a>. This time a different segment of the ALBA-1 submarine cable is being used to connect Cuba to the neighboring island nation of Jamaica. At 15:04 UTC on 13 May 2013, we observed ETECSA beginning to receive international Internet service through <a href="http://www.cwc.com/nearfar/our-regions/caribbean/jamaica.html">Cable & Wireless Jamaica</a>.</p>

</td><td style="vertical-align:top">
<a href="http://www.renesys.com/blog/assets_c/2013/01/alba_cable-836.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/01/alba_cable-836.shtml','popup','width=825,height=679,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/01/alba_cable-thumb-300x246-836.png" width="200" height="146" alt="alba_cable.png" class="mt-image-center" style="text-align: center; display: block; margin: 0px 10px 10px;" /></a>
</td></tr></table>
]]>
        <![CDATA[
<br><table><tr><td style="vertical-align:top">
<p>The graphic on the right shows the make up of Internet transit providers used by ETECSA to reach the global Internet since 1&nbsp;January 2013. Telefonica showed up on 10 January when ALBA-1 began carrying Internet traffic. C&W Jamaica appears in yellow on 13 May. There is a brief dip in the Telefonica plot as ALBA-1 was offline for about eight hours on 15 March and for two hours on 17 March, something we <a href="https://twitter.com/renesys/status/318819671321239552">tweeted</a>.<p>

<p>This past March, C&W Caribbean <a href="http://www.telegeography.com/products/commsupdate/articles/2013/03/01/cwc-pinpoints-cuba-domrep-puerto-rico-for-expansion/">listed Cuba</a> as one of the markets they planned to enter and fulfill the relationship signed three years prior when C&W Jamaica <a href="http://www.telegeography.com/products/commsupdate/articles/2010/03/24/new-jamaica-cuba-cable-deal-inked/">signed a partnership</a> with 
the company established to oversee the ALBA-1 cable project, Cuban-Venezuelan joint venture <a href="http://www.telecom.gob.ve/index.php?option=com_content&view=article&id=45&Itemid=59">Telecomunicaciones Gran Caribe (TGC)</a>.</p>

</td><td>
<a href="http://www.renesys.com/blog/assets_c/2013/05/11960_CU-1081.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/05/11960_CU-1081.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/05/11960_CU-thumb-300x257-1081.png" width="300" height="257" alt="11960_CU.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 10px 20px;" /></a>
</td></tr></table>

<p>Two weeks ago, I had the opportunity to present at <a href="http://www.lacnic.net/web/eventos/lacnic19-agenda">LACNIC 19</a> in Medellin, Colombia. While there, I was able to speak to a manager from ETECSA. He said he and his staff had seen our blogs from January and confirmed that we were right about the initial asymmetric traffic misconfiguration of ALBA-1, which <a href="http://www.renesys.com/blog/2013/01/cuban-fiber-completo.shtml">they fixed after a couple of days</a>. It was pleasure to meet some of the people involved with this historic activation.</p>

<br>
<table><tr><td style="vertical-align:top">
<p>When we look at our recent traceroute measurement data into Cuba, we can see that the 13 May activation of ETECSA's link to Jamaica followed some connectivity problems on 10 May, as there were brief decreases in the rate of completing measurements on that day, regardless of upstream provider. This was followed by a reduction in connectivity through Telefonica (purple) and then the C&W Jamaica (green) activation.</p>

</td><td>
<a href="http://www.renesys.com/blog/assets_c/2013/05/10292_11960-1.traces3.ASedges.upstreamsof11960-1087.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/05/10292_11960-1.traces3.ASedges.upstreamsof11960-1087.shtml','popup','width=840,height=719,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/05/10292_11960-1.traces3.ASedges.upstreamsof11960-thumb-300x256-1087.png" width="300" height="256" alt="10292_11960-1.traces3.ASedges.upstreamsof11960.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 10px 20px;" /></a>
</td></tr>
</table>

<p>On the Telecom Venezuela website <a href="http://www.telecom.gob.ve/index.php?option=com_content&view=article&id=45&Itemid=59">describing the ALBA-1 cable project</a>, it mentions that the link to Jamaica is for restoration purposes (<em>"El otro segmento para fines de restauración será entre Cuba y Jamaica"</em>). So perhaps this activation is to help alleviate some minor connectivity issues experienced recently by ETECSA. Regardless, it is great news to see another submarine cable connection get activated for Cuba.</p>]]>
    </content>
</entry>

<entry>
    <title>Syrian Internet.. Fragility?</title>
    <link rel="alternate" type="text/html" href="http://www.renesys.com/blog/2013/05/syrian-internet-fragility.shtml" />
    <id>tag:www.renesys.com,2013:/blog//1.242</id>

    <published>2013-05-08T15:03:00Z</published>
    <updated>2013-05-23T20:47:11Z</updated>

    <summary><![CDATA[Update (15:26 UTC, 15 May): Routes to Syrian networks have been restored, at 18:26 Damascus time. Outage duration: 8h25m &nbsp;&nbsp; &nbsp;&nbsp; Update (14:20 UTC, 15 May): Plot of latency measurements to Syrian hosts from various locations, indicating that replies stopped...]]></summary>
    <author>
        <name>James Cowie</name>
        
    </author>
    
        <category term="Engineering" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Internet" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Middle East" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Politics" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="South Asia" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="antifragility" label="Antifragility" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="epeg" label="EPEG" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="fragility" label="Fragility" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="internetblackout" label="Internet blackout" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="pakistan" label="Pakistan" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="syria" label="Syria" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://www.renesys.com/blog/">
        <![CDATA[<p><a href="http://www.renesys.com/blog/assets_c/2013/05/SY_outa_1368576000-1054.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/05/SY_outa_1368576000-1054.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/05/SY_outa_1368576000-thumb-300x257-1054.png" width="300" height="257" alt="SY_outa_1368576000.png" class="mt-image-right" style="float: right; margin: 0 20px 20px 0;" /></a><blockquote><em><strong>Update (15:26 UTC, 15 May): Routes to Syrian networks have been restored, at 18:26 Damascus time. Outage duration: 8h25m</strong></em></p>
<p>&nbsp;</p><p>&nbsp;</p>
<p>&nbsp;</p><p>&nbsp;</p>

<p><a href="http://www.renesys.com/blog/assets_c/2013/05/syria.live.15may.1400-1051.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/05/syria.live.15may.1400-1051.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/05/syria.live.15may.1400-thumb-300x257-1051.png" width="300" height="257" alt="syria.live.15may.1400.png" class="mt-image-left" style="float: left; margin: 0 20px 20px 0;" /></a><blockquote><em><strong>Update (14:20 UTC, 15 May): Plot of latency measurements to Syrian hosts from various locations, indicating that replies stopped returning shortly after 7am UTC, aligned with the withdrawal of routes to Syrian networks. (Click image for details)</strong></em></p>

<p><blockquote><em><strong>Update (07:30 UTC, 15 May): <a href="https://twitter.com/renesys/status/334577020170280960">Syrian Internet down again</a> since 07:01 UTC (10:00 Damascus time), Wednesday, 15 May 2013.  <a href="https://twitter.com/syrianewsco/status/334599708603473920">Syrian news agency reports</a> that they're working to fix.  Potentially related to <a href="https://twitter.com/jimcowie/status/334584116580331521">forthcoming UN decision </a>today?</strong></em></blockquote></p>
<p>&nbsp;</p>
<p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p>
<p>&nbsp;</p><hr/>

<p><blockquote><em>Older Update: Syrian Internet has returned.  Outage lasted 19.5 hours, from 18:45 UTC May 7th to 14:13 UTC May 8th. </em></blockquote></p>

<p>As we write, the Syrian people are still disconnected from the global Internet at the most fundamental level, nearly all of their paths <a href="https://twitter.com/renesys/status/331864272055435264">withdrawn from the global routing table.</a>  Since 18:45 UTC on May 7th, Renesys hasn't seen a flicker of activity.  We haven't been able to successfully send a ping or a traceroute to any host inside Syria.  Government websites, universities, domain name servers, core infrastructure routers, banks, businesses, DSL customers, smartphones: all silent. </p> <a href="http://www.renesys.com/blog/assets_c/2013/05/Syria07May2013-1042.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/05/Syria07May2013-1042.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/05/Syria07May2013-thumb-300x257-1042.png" width="300" height="257" alt="Syria07May2013.png" class="mt-image-right" style="float: right; margin: 0 0 20px 20px;" /></a>
]]>
        <![CDATA[
<p>As I look back at what we've written about Internet outage over the years, I see a sort of evolution in our perspective.  We've covered Internet failures due to <a href="http://www.renesys.com/blog/2008/08/georgia-clings-to-the-net.shtml">war,</a> <a href="http://www.renesys.com/blog/2011/03/what-libya-learned-from-egypt.shtml">politics,</a> <a href="http://www.renesys.com/blog/2008/02/pakistan-hijacks-youtube-1.shtml">censorship,</a> <a href="http://www.renesys.com/blog/2012/07/large-outage-in-lebanon.shtml">central planning, </a><a href="http://www.renesys.com/blog/2011/03/japan-quake.shtml">earthquakes,</a> <a href="http://www.renesys.com/blog/2008/09/ike-brings-biggest-multistate.shtml">hurricanes,</a> <a href="http://www.renesys.com/blog/2008/12/deja-vu-all-over-again-cables.shtml">cable cuts,</a> <a href="http://www.renesys.com/blog/2008/10/wrestling-with-the-zombie-spri.shtml">business disputes,</a> <a href="http://www.renesys.com/blog/2012/10/blast-in-turkey-impacts-iran-i.shtml">terrorism,</a>  <a href="http://www.renesys.com/blog/2013/02/faraway-fallout-from-black-sea.shtml">undersea mud volcanoes, </a>and (perhaps) <a href="http://www.renesys.com/blog/2013/03/north-korea-suffers-outage.shtml">cyberwarfare.</a> </p>

<p> In the early days, we reported each outage breathlessly, shocked that the Internet could fail in such spectacular ways.  If you look around the web this morning, you'll see a lot of that same shock-and-awe reporting from companies who are just discovering the fragilities visible in Internet data. </p>

<p>In this case, however, what strikes me is the depressing <em>sameness</em> of the sequence of Syrian Internet disconnections.  Just as in <a href="http://www.renesys.com/blog/2011/06/tracing-the-syrian-blackout.shtml">June 2011</a>, <a href="http://www.renesys.com/blog/2012/07/syria-leaves-the-internet.shtml">July 2012,</a> <a href="http://www.renesys.com/blog/2012/08/china-keeps-syria-connected.shtml">August 2012,</a> and <a href="http://www.renesys.com/blog/2012/11/syria-off-the-air.shtml">November 2012,</a> the entire nation disappeared from the Internet in 30 seconds, as if a switch had been thrown.  Everyone in the Twittersphere seems to share the same strange lack of perspective about these events &mdash; in the middle of the chaos and tragedy of civil war, why is anyone <em>surprised </em>when the Internet stops working?  
Isn't it actually more shocking and noteworthy that the Internet in Syria <em>actually functions pretty well 360 days out of the year?</em> </p>

<p>If you're looking for a different way to think about events like these, you might enjoy reading Nassim Nicholas Taleb's book, <a href="http://www.amazon.com/Antifragile-Things-That-Gain-Disorder/dp/1400067820">Antifragile</a> (ironically, published just days before the last major Syrian Internet disconnection). </p>

<p>Antifragility is a property of systems that get stronger when they are challenged by stresses.  It's not merely robustness, or resilience (systems that return to stable state after stresses have passed) &mdash; an antifragile system like the Internet actually gets <em>better</em> when you try to break it.  Systems of systems attain antifragility because their individual elements are so fragile.  For example, Taleb writes:</p>

<p><blockquote><em>"Restaurants are fragile; they compete with each other, but the collective of local restaurants is antifragile for that very reason.  Had restaurants been individually robust, hence immortal, the overall business would be either stagnant or weak, and would deliver nothing better than cafeteria food &mdash; and I mean Soviet-style cafeteria food.  Further, it would be marred with systemic shortages, with, once in a while, a complete crisis and government bailout.  All that quality, stability, and reliability are owed to the fragility of the restaurant itself." </em></blockquote></p>

<p>If you've been reading all of our Internet outage case study blogs, you might see a familiar pattern.   The Internet fails in some way, taking individual institutions (or even entire countries or geographic regions) offline.   The outage exposes fundamental undetected weaknesses &mdash; lack of submarine or terrestrial cable diversity,  <a href="http://www.renesys.com/blog/2012/11/could-it-happen-in-your-countr.shtml">lack of Internet provider diversity</a>, underinvestment in alternative forms of transport, political control over Internet chokepoints.  If the Internet damage is painful enough, engineers (or revolutionaries) are forced to take creative steps to address those weaknesses.  Repeat...  forever.</p>

<p>Take Pakistan, for example.  This cycle of insult-and-repair is what made Pakistan Telecom serious about buying eastbound backup transit to Asia in the wake of the first round of Mediterranean cable cuts in 2008.  It's what led (indirectly or directly) to the establishment of <a href="http://www.renesys.com/blog/2012/06/smw4-break-on-south-asia.shtml">competing providers in Pakistan</a>, with foreign investment and additional cable resources connecting Pakistan to the Gulf States.</p>

<p>And because Internet is easily exportable, Pakistan's improved Internet connectivity spilled over to improve the situation in their historically fragile neighbor,  Afghanistan.  Here's a picture of one slice of Afghanistan's diverse connectivity over the last few weeks (click to zoom):</p>
<a href="http://www.renesys.com/blog/assets_c/2013/05/AfghanCW-1045.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/05/AfghanCW-1045.shtml','popup','width=1574,height=599,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/05/AfghanCW-thumb-500x190-1045.png" width="500" height="190" alt="AfghanCW.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></a>

Note three paths from Afghan providers to Cable and Wireless in Europe.   Borrowing from Pakistan's diversity, one route goes through Pakistan's competitive provider, Transworld Associates, then to Omantel and <a href="http://www.renesys.com/blog/2013/04/gulf-states-iran.shtml">over the EPEG cable through Iran and the Russian Caucasus</a> to Europe.  Another goes by satellite to Bahrain's Batelco, then over to Omantel and out through Iran on the same EPEG route.   A third goes north through Uzbekistan's Intal Telecom, then through two Russian routes to Europe.  The Iranian EPEG route is itself an<a href="http://www.renesys.com/blog/2013/04/gulf-states-iran.shtml"> improbably antifragile innovation,</a> inspired by multiple years of Mediterranean cable cuts and avoidance of the demonstrably fragile <a href="http://www.renesys.com/blog/2013/03/intrigue-surrounds-smw4-cut.shtml">Egyptian transit corridor. </a></p>

<p>So what does all this mean for Syria and its Internet neighborhood?  One has to look past short-term dysfunction and think about what comes next.  Every significant Internet disconnection, and the<a href="https://www.eff.org/deeplinks/2013/05/syrian-internet-goes-dark-leaving-questions-and-uncertainty-0"> local and global reaction of outrage and dismay</a>, sends an important signal about the fragility of the underlying system.   It makes single points of failure and control visible, so that those fragilities can be found and fixed, and the Internet as a whole can continue to gain strength from disorder.</p>      ]]>
    </content>
</entry>

<entry>
    <title>Gulf States Turn to Iran, Russia for Internet</title>
    <link rel="alternate" type="text/html" href="http://www.renesys.com/blog/2013/04/gulf-states-iran.shtml" />
    <id>tag:www.renesys.com,2013:/blog//1.241</id>

    <published>2013-04-22T21:00:00Z</published>
    <updated>2013-05-23T20:55:08Z</updated>

    <summary> Sometimes, it takes a real disaster to create something genuinely new. March 2013 was a month of disasters in the Middle Eastern, South Asian, and East African Internet, with major submarine cable cuts affecting SMW3, SMW4, IMEWE, EIG, SEACOM,...</summary>
    <author>
        <name>James Cowie</name>
        
    </author>
    
        <category term="Caucasus" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Internet" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Middle East" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Politics" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Security" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Submarine Cables" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="azerbaijan" label="Azerbaijan" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="cableandwireless" label="Cable and Wireless" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="epeg" label="EPEG" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="egypt" label="Egypt" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="iran" label="Iran" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="kenya" label="Kenya" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="omantel" label="Omantel" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="russia" label="Russia" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="smw4" label="SMW4" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="terrestrial" label="terrestrial" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://www.renesys.com/blog/">
        <![CDATA[

<p>Sometimes, it takes a real disaster to create something genuinely new.   March 2013 was a <a href="http://www.renesys.com/blog/2013/03/intrigue-surrounds-smw4-cut.shtml">month of disasters </a>in the Middle Eastern, South Asian, and East African Internet, with major submarine cable cuts affecting SMW3, SMW4, IMEWE, EIG, SEACOM, and TE-North. </p>  

<p>One of the "genuinely new" Internet traffic paths that emerged in response is a <a href="http://www.epegcable.com">counterintuitive terrestrial route</a>, linking the ancient Indian Ocean trade empire of Oman with the Internet markets of Western Europe, by way of Iran, Azerbaijan, and the Russian Caucasus.  As we'll see, its effects are now being felt across the region, from Pakistan, to Gulf states like Bahrain and Oman, to Kenya.</p>

<p> <a href="http://www.renesys.com/blog/assets_c/2013/04/epeg-homepage-1022.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/04/epeg-homepage-1022.shtml','popup','width=1500,height=991,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/04/epeg-homepage-thumb-450x297-1022.png" width="450" height="297" alt="epeg-homepage.png" class="mt-image-right" style="float: right; margin: 0 0 20px 20px;" /></a>  The <a href="http://www.youtube.com/watch?v=90Fmplr5JeU">EPEG (Europe-Persia Express Gateway) consortium</a> was actually born in June 2011, as an alternative to the congested, <a href="http://www.renesys.com/blog/2011/01/egypt-leaves-the-internet.shtml">politically uncertain</a> Suez transit corridor. EPEG links together existing fiber routes from the Iranian, Azeri, and Russian incumbents, connected to Cable and Wireless's network to approximate a <a href="http://en.wikipedia.org/wiki/Great_circle">Great Circle route</a> to Frankfurt.   With the aid of one final submarine hop across the Strait of Hormuz to  Muscat, EPEG promised to deliver a major new low-latency, high-capacity terrestrial route to carry the Gulf states' traffic to Europe. </p> 

<p>EPEG was scheduled to begin service in the summer of 2012, but delays on the final submarine links between Iran and Oman caused the start date to be pushed, and pushed again.   When Vodafone acquired Cable and Wireless in July 2012, one of the attractions of the deal may have been the prospect of participating in EPEG &mdash; when the project reached completion, Vodafone/C&W would sit astride the first low-latency terrestrial link connecting the Gulf region to the financial and content markets of Western Europe.</p>

<p>We reported in February 2013 that in the wake of Russian service interruptions in the Black Sea, <a href="http://www.renesys.com/blog/2013/02/faraway-fallout-from-black-sea.shtml">Iran's DCI had begun receiving Internet transit from Omantel</a>, indicating that the missing link in the southern path was alive at last.   We began watching intently for signs of end-to-end service activation on EPEG.   </p>

<p>Last month, we saw them.</p>
<p>&nbsp;</p>
<p>&nbsp;<hr style="height:1px"></p>
]]>
        <![CDATA[
<p><strong><large>EPEG in Action in Oman</large></strong><a href="http://www.renesys.com/blog/assets_c/2013/04/epeg_2-1025.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/04/epeg_2-1025.shtml','popup','width=977,height=803,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/04/epeg_2-thumb-450x369-1025.png" width="450" height="369" alt="epeg_2.png" class="mt-image-right" style="float: right; margin: 0 0 20px 20px;" /></a></p>

<p>To some within the GCC, EPEG may seem <a href="http://www.alarabiya.net/articles/2011/05/02/147594.html">geopolitically implausible</a>, but as a lower-latency alternative to Egyptian transit, it makes a lot of sense.  </p>

<p>Here are some screenshots from our new Internet Business Intelligence suite, due out later this year, showing the emergence of Cable and Wireless transit as the fastest transit path into Oman (click on image for higher resolution).  The new transit path from Omantel to Cable and Wireless emerges on March 31st (in green), some 15 milliseconds faster than existing transit paths from Frankfurt to Oman.  Note the impact of the cable cuts before March 31st.  By comparison, latency variance on the new path is tight, suggesting that the Iranian path has ample capacity and is still lightly loaded.</p>

<p>&nbsp;</p>

<p>&nbsp;<hr style="height:1px"></p>

<p><strong><large>Bahrain taking advantage of EPEG</large></strong><a href="http://www.renesys.com/blog/assets_c/2013/04/epeg_0-1028.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/04/epeg_0-1028.shtml','popup','width=968,height=532,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/04/epeg_0-thumb-450x247-1028.png" width="450" height="247" alt="epeg_0.png" class="mt-image-right" style="float: right; margin: 0 0 20px 20px;" /></a></p>

<p>Batelco, Bahrain's incumbent provider, wasted no time in taking advantage of the new, lower-latency path to Europe for<a href="http://mi.renesys.com/mi/browse.do?net=8529&geo=country:BH&&section=transits&ipfam=v4&"> selected customers</a>. </p>
 
<p>As this screenshot illustrates, we estimate that transit through Omantel and on to Cable and Wireless through Iran reduces the round trip time for Bahraini traffic to Frankfurt by as much as 30ms.   Despite the ongoing political tensions between Bahrain and Iran, that's a pretty compelling argument.  </p>

<p>&nbsp;</p>

<p><br/>&nbsp;<br/><hr style="height:1px"></p>

<p><strong>Pakistan's Transworld Transiting EPEG</strong><a href="http://www.renesys.com/blog/assets_c/2013/04/38193_PK_b-1039.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/04/38193_PK_b-1039.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/04/38193_PK_b-thumb-450x385-1039.png" width="430" height="320" alt="38193_PK_b.png" class="mt-image-right" style="float: right; margin: 0 0 40px 20px;" /></a></p>

<p>Pakistani competitive provider Transworld (AS38193) partners with Omantel to operate the <a href="http://en.wikipedia.org/wiki/Transworld_Associates">TWA-1</a> submarine cable, so it wasn't a big surprise to see Omantel appear at the end of March as a remedy for the transit confusion caused by the SMW4 cut off Alexandria, Egypt.   In short order, a significant portion of all the traffic to Transworld's 2,000+ routed prefixes has begun to traverse the EPEG link through Oman and Iran.</p>

<p><br/>&nbsp;<br/></p>
<p><br/>&nbsp;<br/></p><p><br/>&nbsp;<br/></p><p>&nbsp;</p>

<p>&nbsp;<hr style="height:1px"></p>

<p><strong>Faster Transit for East Africa</strong><a href="http://www.renesys.com/blog/assets_c/2013/04/epeg_4-1035.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/04/epeg_4-1035.shtml','popup','width=973,height=781,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/04/epeg_4-thumb-450x361-1035.png" width="450" height="361" alt="epeg_4.png" class="mt-image-right" style="float: right; margin: 0 0 20px 20px;" /></a></p>

<p>We even see EPEG's benefits reaching into East Africa, where AccessKenya (AS15808) picked up Omantel transit, creating a path that's more than 20 milliseconds faster than the previous alternatives to Frankfurt. </p>

<p> <a href="http://www.renesys.com/blog/2012/02/east-african-cable-breaks.shtml">As we've seen before</a>, East African providers are very quick to adapt to changes in the transit environment, and Omantel may do very well if other providers in Kenya, Uganda, and Tanzania get on board. </p>

<p>A lot will depend on the price &mdash;  Omantel is probably able to command a significant premium for the uniqueness and low latency of the EPEG route.   When competing cables return to service, we'll see how that pricing affects the new market equilibrium.</p>


<p> <br/>&nbsp;</p>

<p> <br/>&nbsp;<hr style="height:1px"></p>

<p><strong>Conclusion</strong></p>
<p>If you'd told me five years ago that we would one day see Iranian and Russian terrestrial Internet transit serving the countries of the Indian Ocean, from Pakistan to East Africa, I wouldn't have believed it. </p>  

<p>Today, I'm a believer.   Middle Eastern and East African network operators are using the <a href="http://renesys.com/products_services/index.shtml">Renesys Internet Intelligence tools</a> to sniff out new transit opportunities in the market, and finding creative ways to recover from almost unimaginable connectivity challenges. </p>

<p>  We've seen all kinds of strategies emerge in the wake of the SMW4 cuts, from Telecom Egypt transit (as far away as Afghanistan), to Israeli transit, to Iraqi transit, to Syrian transit through a war zone.  In the hands of Omantel, EPEG is the first solution that appears to be delivering globally visible terrestrial routes to a diverse set of regional providers.   </p>

<p>It remains to be seen whether an Internet path through Iran and the Russian Caucasus region will have the kind of stability that enterprises require.   But frankly, compared to the submarine cable competition, they're already looking pretty good.</p>]]>
    </content>
</entry>

<entry>
    <title>Intrigue Surrounds SMW4 Cut</title>
    <link rel="alternate" type="text/html" href="http://www.renesys.com/blog/2013/03/intrigue-surrounds-smw4-cut.shtml" />
    <id>tag:www.renesys.com,2013:/blog//1.240</id>

    <published>2013-03-28T15:04:54Z</published>
    <updated>2013-05-15T11:45:35Z</updated>

    <summary>It has been a rough few weeks for the global Internet, given numerous submarine cable failures and the largest DDOS attack ever reported. While we&apos;re hard-pressed to find evidence of the purported global Internet slowdown due to the DDOS attack,...</summary>
    <author>
        <name>Doug Madory</name>
        <uri>http://www.renesys.com</uri>
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://www.renesys.com/blog/">
        <![CDATA[<p>It has been a rough few weeks for the global Internet, given numerous submarine cable failures and the <a href="http://www.bbc.co.uk/news/technology-21954636">largest DDOS attack ever reported</a>. While we're hard-pressed to find evidence of the purported global Internet slowdown due to the DDOS attack, the dramatic impacts of yesterday's SMW4 submarine cable cut were profound. Recent reports that the cable break was the <a href="http://www.washingtonpost.com/world/middle_east/egypt-naval-forces-capture-3-scuba-divers-trying-to-sabotage-undersea-internet-cable/2013/03/27/dd2975ec-9725-11e2-a976-7eb906f9ed9b_story.html">result of sabotage</a> make the incident even more intriguing. In this blog, we detail what happened to some of the providers in four countries <a href="http://submarinecablemap.com">along the route of the cable</a>: Egypt, Saudi Arabia, Pakistan and India.</p>]]>
        <![CDATA[<br><br>
<p><strong>Impacts of the loss of SeaMeWe-4</strong></p>

<p>This month's submarine cable outages have profoundly degraded connectivity to the Middle East, Asia and Africa. In particular, last week's <a href="http://www.techzim.co.zw/2013/03/eassy-cable-operator-speaks-on-undersea-cable-outage/">EASSy</a> and <a href="http://www.itnewsafrica.com/2013/03/seacom-suffers-internet-outage-off-african-coast/">SEACOM</a> outages wiped out connectivity in parts of East Africa from Djibouti to South Africa. As if that weren't bad enough, the biggest submarine cable connecting Europe and Asia, <a href="http://en.wikipedia.org/wiki/SEA-ME-WE_4">SeaMeWe-4</a>, suffered a failure at <a href="https://twitter.com/renesys/status/316933864977215488">6:20 UTC</a>, 27 March.</p> 

<p>Later in the day, the <a href="http://www.facebook.com/media/set/?set=a.435169449900970.1073741825.146063395478245&type=1">Egyptian Naval forces</a> claimed that they had <a href="http://www.washingtonpost.com/world/middle_east/egypt-naval-forces-capture-3-scuba-divers-trying-to-sabotage-undersea-internet-cable/2013/03/27/dd2975ec-9725-11e2-a976-7eb906f9ed9b_story.html">caught divers sabotaging a submarine cable</a> off the coast of Alexandria, Egypt. In any event, SMW4 clearly suffered a major failure, and as we will see below, caused widespread disruption of Internet services from Egypt to Pakistan.</p>

<p>These plots of latency measurements below show that westbound transit to Europe for many of these providers was either degraded or unavailable due to the SMW4 cut off the coast of Alexandria, Egypt. These providers fell back on eastbound transit through the Far East, but these backup paths weren't always up to carrying the load.</p>

<br><br>
<p><strong>Egypt</strong></p>

<p>Immediately following the cut (marked with a red line), Egyptian incumbent, <a href="http://telecomegypt.com.eg">Telecom Egypt</a>, experienced a brief disruption in Internet transit followed by a reshuffling of its transit providers as it lost service from Level3 and NTT.</p>

<table><tr><td>
<a href="http://www.renesys.com/blog/assets_c/2013/03/8452latencies_Frankfurt_bgp02.fra1_s-944.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/03/8452latencies_Frankfurt_bgp02.fra1_s-944.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/03/8452latencies_Frankfurt_bgp02.fra1_s-thumb-300x257-944.png" width="300" height="257" alt="8452latencies_Frankfurt_bgp02.fra1_s.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" /></a>
</td><td>
<a href="http://www.renesys.com/blog/assets_c/2013/03/8452latencies_SG_vps01.sin1_s-947.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/03/8452latencies_SG_vps01.sin1_s-947.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/03/8452latencies_SG_vps01.sin1_s-thumb-300x257-947.png" width="300" height="257" alt="8452latencies_SG_vps01.sin1_s.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></a>
</td></tr></table>

<p>The loss of service from Level3 and NTT and gain of eastbound providers Bharti and Singapore Telecom (SingTel) is much clearer when the same data is viewed as a stacked graph of counts of traceroutes crossing through various providers into TE's network:</p>
<a href="http://www.renesys.com/blog/assets_c/2013/03/8452-1.scad.ASedges.upstreamsof8452-995.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/03/8452-1.scad.ASedges.upstreamsof8452-995.shtml','popup','width=840,height=719,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/03/8452-1.scad.ASedges.upstreamsof8452-thumb-300x256-995.png" width="300" height="256" alt="8452-1.scad.ASedges.upstreamsof8452.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></a>

<br><br>
<p><strong>Saudi Arabia</strong></p>

<p>Saudi Arabian incumbent, <a href="http://www.stc.com.sa">Saudi Telecom</a> (STC), experienced dramatic increases in latencies to Europe as traffic shifted away from the severed submarine cable. </p>

<table><tr><td>
<a href="http://www.renesys.com/blog/assets_c/2013/03/39386latencies_Amsterdam_vps01.ams2_s-977.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/03/39386latencies_Amsterdam_vps01.ams2_s-977.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/03/39386latencies_Amsterdam_vps01.ams2_s-thumb-300x257-977.png" width="300" height="257" alt="39386latencies_Amsterdam_vps01.ams2_s.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" /></a>
</td><td>
<a href="http://www.renesys.com/blog/assets_c/2013/03/39386latencies_LAX_bgp02.lax1_s-980.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/03/39386latencies_LAX_bgp02.lax1_s-980.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/03/39386latencies_LAX_bgp02.lax1_s-thumb-300x257-980.png" width="300" height="257" alt="39386latencies_LAX_bgp02.lax1_s.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" /></a>
</td></tr></table>

<p>Headed the other direction from Saudi Arabia to Hong Kong, the cut caused STC to reshuffle its transit, but without the dramatic rises in latencies.</p>

<table><tr><td>
<a href="http://www.renesys.com/blog/assets_c/2013/03/39386latencies_HKG_vps01.hkg1_s-983.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/03/39386latencies_HKG_vps01.hkg1_s-983.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/03/39386latencies_HKG_vps01.hkg1_s-thumb-300x257-983.png" width="300" height="257" alt="39386latencies_HKG_vps01.hkg1_s.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" /></a>
</td><td>
<a href="http://www.renesys.com/blog/assets_c/2013/03/39386latencies_SG_vps01.sin1_s-986.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/03/39386latencies_SG_vps01.sin1_s-986.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/03/39386latencies_SG_vps01.sin1_s-thumb-300x257-986.png" width="300" height="257" alt="39386latencies_SG_vps01.sin1_s.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" /></a>
</td></tr></table>


<br><br>
<p><strong>UAE <em>(added 2 April)</em></strong></p>

<p>As was the case with other Middle Eastern providers, <a href="http://www.etisalat.ae/eportal/en/home/index.html">Etisalat</a> experienced a dramatic shift in traffic from Europe and the west, but less so from the east.</p>

<table><tr><td>
<a href="http://www.renesys.com/blog/assets_c/2013/04/8966latencies_AMS_vps01.ams2_s-998.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/04/8966latencies_AMS_vps01.ams2_s-998.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/04/8966latencies_AMS_vps01.ams2_s-thumb-300x257-998.png" width="300" height="257" alt="8966latencies_AMS_vps01.ams2_s.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" /></a>
</td><td>
<a href="http://www.renesys.com/blog/assets_c/2013/04/8966latencies_LAX_bgp01.lax1_s-1001.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/04/8966latencies_LAX_bgp01.lax1_s-1001.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/04/8966latencies_LAX_bgp01.lax1_s-thumb-300x257-1001.png" width="300" height="257" alt="8966latencies_LAX_bgp01.lax1_s.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" /></a>
</td></tr></table>

<br><br>

<table><tr><td>
<a href="http://www.renesys.com/blog/assets_c/2013/04/8966latencies_FRA_bgp02-1.fra1_s-1004.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/04/8966latencies_FRA_bgp02-1.fra1_s-1004.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/04/8966latencies_FRA_bgp02-1.fra1_s-thumb-300x257-1004.png" width="300" height="257" alt="8966latencies_FRA_bgp02-1.fra1_s.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" /></a>
</td><td>
<a href="http://www.renesys.com/blog/assets_c/2013/04/8966latencies_HKG_vps01.hkg1_s-1007.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/04/8966latencies_HKG_vps01.hkg1_s-1007.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/04/8966latencies_HKG_vps01.hkg1_s-thumb-300x257-1007.png" width="300" height="257" alt="8966latencies_HKG_vps01.hkg1_s.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" /></a>
</td></tr></table>

<p><a href="http://en.wikipedia.org/wiki/Emirates_Integrated_Telecommunications_Company">Emirates Integrated Telecommunications Company</a> also known by its retail name, "Du", appears to have weathered the cable cut without significant disruptions to either the west or the east.</p>

<table><tr><td>
<a href="http://www.renesys.com/blog/assets_c/2013/04/15802latencies_LHR_bgp02.lhr1_s-1010.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/04/15802latencies_LHR_bgp02.lhr1_s-1010.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/04/15802latencies_LHR_bgp02.lhr1_s-thumb-300x257-1010.png" width="300" height="257" alt="15802latencies_LHR_bgp02.lhr1_s.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" /></a>
</td><td>
<a href="http://www.renesys.com/blog/assets_c/2013/04/15802latencies_AMS_vps01.ams2_s-1013.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/04/15802latencies_AMS_vps01.ams2_s-1013.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/04/15802latencies_AMS_vps01.ams2_s-thumb-300x257-1013.png" width="300" height="257" alt="15802latencies_AMS_vps01.ams2_s.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" /></a>
</td></tr></table>


<table><tr><td>
<a href="http://www.renesys.com/blog/assets_c/2013/04/15802latencies_HKG_vps01-1.hkg1_s-1016.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/04/15802latencies_HKG_vps01-1.hkg1_s-1016.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/04/15802latencies_HKG_vps01-1.hkg1_s-thumb-300x257-1016.png" width="300" height="257" alt="15802latencies_HKG_vps01-1.hkg1_s.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" /></a>
</td><td>
<a href="http://www.renesys.com/blog/assets_c/2013/04/15802latencies_LAX_bgp01.lax1_s-1019.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/04/15802latencies_LAX_bgp01.lax1_s-1019.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/04/15802latencies_LAX_bgp01.lax1_s-thumb-300x257-1019.png" width="300" height="257" alt="15802latencies_LAX_bgp01.lax1_s.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" /></a>
</td></tr></table>

<br><br>
<p><strong>Pakistan</strong></p>

<p>The impact of the SMW4 cut on the Pakistani Internet has been severe, <a href="http://tribune.com.pk/story/527643/underwater-cable-damaged-internet-speed-plummets-by-60-nationwide/">as reported by the Pakistani media</a>.</p>

<p>Pakistani incumbent, <a href="http://www.ptcl.com.pk">PTCL</a>, was already struggling due to the recent loss of <a href="http://www.thenews.com.pk/article-91972-Undersea-cable-fault-dents-Internet-services-in-Pakistan">another major submarine cable</a>. The graph on the left shows that latencies from Frankfurt to PTCL went through the roof as traffic was re-routed around the world to get to Pakistan. From Singapore, (on the right) there was a minor disturbance, but not nearly as crippling as for westbound traffic.</p>

<table><tr><td>
<a href="http://www.renesys.com/blog/assets_c/2013/03/45595latencies_Frankfurt_bgp02.fra1_s-938.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/03/45595latencies_Frankfurt_bgp02.fra1_s-938.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/03/45595latencies_Frankfurt_bgp02.fra1_s-thumb-300x257-938.png" width="300" height="257" alt="45595latencies_Frankfurt_bgp02.fra1_s.png" class="mt-image-right" style="float: right; margin: 0 20px 20px;" /></a>
</td><td>
<a href="http://www.renesys.com/blog/assets_c/2013/03/45595latencies_SG_vps01.sin1_s-941.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/03/45595latencies_SG_vps01.sin1_s-941.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/03/45595latencies_SG_vps01.sin1_s-thumb-300x257-941.png" width="300" height="257" alt="45595latencies_SG_vps01.sin1_s.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" /></a>
</td></tr></table>

<p>For Pakistan's other international gateway, <a href="http://www.tw1.com">Transworld</a>, the impacts were severe when connecting to both the west and the east.</p>

<table><tr><td>
<a href="http://www.renesys.com/blog/assets_c/2013/03/38193latencies_NYC_vps01.nyc1_s-953.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/03/38193latencies_NYC_vps01.nyc1_s-953.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/03/38193latencies_NYC_vps01.nyc1_s-thumb-300x257-953.png" width="300" height="257" alt="38193latencies_NYC_vps01.nyc1_s.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" /></a>
</td><td>
<a href="http://www.renesys.com/blog/assets_c/2013/03/38193latencies_HKG_vps01.hkg1_s-956.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/03/38193latencies_HKG_vps01.hkg1_s-956.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/03/38193latencies_HKG_vps01.hkg1_s-thumb-300x257-956.png" width="300" height="257" alt="38193latencies_HKG_vps01.hkg1_s.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" /></a>
</td></tr></table>

<br><br>
<p><strong>India</strong></p>

<p>With the loss of SMW4, India-based <a href="http://www.bharti.com/home">Bharti</a> lost its main route to the west. Delays for Internet traffic coming from western Europe spiked. From the east, things were fine.</p>

<table><tr><td>
<a href="http://www.renesys.com/blog/assets_c/2013/03/9498latencies_Frankfurt_bgp02.fra1_s-965.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/03/9498latencies_Frankfurt_bgp02.fra1_s-965.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/03/9498latencies_Frankfurt_bgp02.fra1_s-thumb-300x257-965.png" width="300" height="257" alt="9498latencies_Frankfurt_bgp02.fra1_s.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" /></a>
</td><td>
<a href="http://www.renesys.com/blog/assets_c/2013/03/9498latencies_HKG_vps01.hkg1_s-968.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/03/9498latencies_HKG_vps01.hkg1_s-968.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/03/9498latencies_HKG_vps01.hkg1_s-thumb-300x257-968.png" width="300" height="257" alt="9498latencies_HKG_vps01.hkg1_s.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" /></a>
</td></tr></table>

<p>Like Bharti, <a href="https://www.vodafone.in">Vodafone India</a> experienced dramatic increases in latencies for connections to and through Europe.</p>

<table><tr><td>
<a href="http://www.renesys.com/blog/assets_c/2013/03/55410latencies_Frankfurt_bgp02.fra1_s-959.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/03/55410latencies_Frankfurt_bgp02.fra1_s-959.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/03/55410latencies_Frankfurt_bgp02.fra1_s-thumb-300x257-959.png" width="300" height="257" alt="55410latencies_Frankfurt_bgp02.fra1_s.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" /></a>
</td><td>
<a href="http://www.renesys.com/blog/assets_c/2013/03/55410latencies_London_bgp02.lhr1_s-962.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/03/55410latencies_London_bgp02.lhr1_s-962.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/03/55410latencies_London_bgp02.lhr1_s-thumb-300x257-962.png" width="300" height="257" alt="55410latencies_London_bgp02.lhr1_s.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" /></a>
</td></tr></table>

<p>When connecting through the East, Vodafone India was largely stable. In fact, from Los Angeles, latencies <em>improved</em> slightly as traffic from LA was allowed to go a slightly shorter (and presumably more expensive) path across the Pacific Ocean instead of the Atlantic to get to India.</p>

<table><tr><td>
<a href="http://www.renesys.com/blog/assets_c/2013/03/55410latencies_HKG_vps01.hkg1_s-971.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/03/55410latencies_HKG_vps01.hkg1_s-971.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/03/55410latencies_HKG_vps01.hkg1_s-thumb-300x257-971.png" width="300" height="257" alt="55410latencies_HKG_vps01.hkg1_s.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" /></a>
</td><td>
<a href="http://www.renesys.com/blog/assets_c/2013/03/55410latencies_LAX_bgp02.lax1_s-974.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/03/55410latencies_LAX_bgp02.lax1_s-974.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/03/55410latencies_LAX_bgp02.lax1_s-thumb-300x257-974.png" width="300" height="257" alt="55410latencies_LAX_bgp02.lax1_s.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" /></a>
</td></tr></table>

<strong><p>Conclusions</p></strong>

<p>For me, one of the takeaways from the above analysis is that many of these providers have carefully engineered geographic diversity into their submarine cable strategy. However, the backup paths don't always deliver relief. In Pakistan, for example, the loss of westbound transit has virtually crippled the Internet despite the fact that eastbound routes stayed up. It is almost the mirror image of the impact on Bangladesh in last year's <a href="http://www.bbc.co.uk/news/technology-18366007">SMW4 cable cut near Singapore</a>. In that case, <a href="http://www.renesys.com/blog/2012/06/smw4-break-on-south-asia.shtml">Bangladesh lost eastbound transit due to the cable cut</a> and the westbound backup just didn't have the bandwidth to handle the load, leaving the country essentially cut off.</p>

<p>Finally, I'll be giving a talk next month in Paris about visualizing the impacts of submarine cable breaks such as yesterday's SMW4 cut at <a href="http://www.suboptic.org">Suboptic 2013</a>, the world's largest conference about the submarine cable business. We obviously have a lot more to discuss now as an industry. If you are attending, please stop by and introduce yourself.</p>]]>
    </content>
</entry>

<entry>
    <title>Cyber Escalation in Korea?</title>
    <link rel="alternate" type="text/html" href="http://www.renesys.com/blog/2013/03/more-outages-in-koreas.shtml" />
    <id>tag:www.renesys.com,2013:/blog//1.239</id>

    <published>2013-03-20T15:39:00Z</published>
    <updated>2013-03-30T10:51:39Z</updated>

    <summary> On Friday, we published a blog confirming a disruption in Internet connectivity affecting the Internet of North Korea. This morning, South Korean authorities reported that they have been the victims of a cyber attack which impacted TV News organizations...</summary>
    <author>
        <name>Doug Madory</name>
        <uri>http://www.renesys.com</uri>
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://www.renesys.com/blog/">
        <![CDATA[<table><tr><td>
<p>On Friday, we published a blog confirming a <a href="http://www.renesys.com/blog/2013/03/north-korea-suffers-outage.shtml">disruption in Internet connectivity</a> affecting the <a href="https://twitter.com/renesys/status/289463913383358464">Internet of North Korea</a>. 
</p>
<p>This morning, <a href="http://www.nytimes.com/2013/03/21/world/asia/south-korea-computer-network-crashes.html?_r=0">South Korean authorities reported</a> that they have been the victims of a cyber attack which impacted TV News organizations as well as banking institutions. 
</p>
<p>Renesys can confirm that at least some of today's incidents escalated to the point of global visibility, as both South and North Koreans networks experienced actual disconnections. We note similarly timed outages affecting South Korea's largest natural gas company.
</p>

</td><td>
<a href="http://www.renesys.com/blog/assets_c/2013/03/120725_FRC_northandsouthkoreaflagsEX.png.CROP.rectangle3-large-929.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/03/120725_FRC_northandsouthkoreaflagsEX.png.CROP.rectangle3-large-929.shtml','popup','width=568,height=346,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/03/120725_FRC_northandsouthkoreaflagsEX.png.CROP.rectangle3-large-thumb-300x182-929.png" width="300" height="182" alt="120725_FRC_northandsouthkoreaflagsEX.png.CROP.rectangle3-large.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" /></a>
</td></tr></table>
<br><br>]]>
        <![CDATA[<p><strong>South Korea News Media Outages</strong></p>

<p>We observed 5 routed networks of <a href="http://www.kbs.co.kr">Korea Broadcasting System</a> go down at 05:54:18 UTC this morning (20 March). At the time of this writing they are still down. The <a href="http://www.yonhapnews.co.kr/">Yonhap News Network</a> (YTN) also experienced outages of two of its networks today at 05:54:30 UTC and 06:29:26 UTC. 
</p>

<a href="http://www.renesys.com/blog/assets_c/2013/03/South_Korea_News_Media_Networks-926.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/03/South_Korea_News_Media_Networks-926.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/03/South_Korea_News_Media_Networks-thumb-300x257-926.png" width="300" height="257" alt="South_Korea_News_Media_Networks.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></a>

<p><strong>South Korea Banking and Energy Outages</strong></p>

<p>About thirty minutes after the South Korean media outages, we observed <a href="http://www.kogas.or.kr/kogas_eng/html/main/main.jsp">Korea Gas Corporation</a> (Kogas, AS9857), the <a href="http://en.wikipedia.org/wiki/Korea_Gas_Corporation">largest liquefied natural gas import company in the world</a>, go completely offline as its 10 routed networks went down at 06:26:30 UTC and stayed down for over two hours. At the same time, we saw three routed networks of <a href="http://www.shinhan.com">Shinhan Bank</a> taken down as well.
</p>

<a href="http://www.renesys.com/blog/assets_c/2013/03/South_Korea_Banking_and_Energy_Networks-932.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/03/South_Korea_Banking_and_Energy_Networks-932.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/03/South_Korea_Banking_and_Energy_Networks-thumb-300x257-932.png" width="300" height="257" alt="South_Korea_Banking_and_Energy_Networks.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></a>

<p>
For context, remember that South Korea normally routes over 15,000 networks. On a typical day, 40-50 of these networks are down temporarily for various technical reasons.
However, networks from these sectors (Media, Energy, and Banking) are typically some of the most stable, and the timing of their simultaneous outages seems suspicious.
</p>

<p><strong>Additional outages in North Korea</strong></p>

Since last week's disruption in connectivity in North Korea, we have observed additional brief routing outages for the four routed networks of North Korea. On Monday (18 March) and this morning (20 March), we observed outages lasting for just a few minutes in North Korea. It should be noted that although North Korea's Internet is small, it is very stable. Until last week, North Korean outages had been very rare.
<br><br>
<table><tr><td>
<a href="http://www.renesys.com/blog/assets_c/2013/03/KP_outa_1363642200-920.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/03/KP_outa_1363642200-920.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/03/KP_outa_1363642200-thumb-300x257-920.png" width="300" height="257" alt="KP_outa_1363642200.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" /></a>
</td><td>
<a href="http://www.renesys.com/blog/assets_c/2013/03/KP_outa_1363750200-923.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/03/KP_outa_1363750200-923.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/03/KP_outa_1363750200-thumb-300x257-923.png" width="300" height="257" alt="KP_outa_1363750200.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" /></a>
</td></tr></table>
<br><br>

<p><strong>Summary</strong></p>
<p>
It is impossible to know from connectivity measurements alone whether these outages were the direct result of cyber attacks. However, given the <a href="http://www.cnn.com/2013/03/12/world/asia/koreas-tensions">recent rhetoric</a> between these two nations, it is hard not to see these as ominous developments on the Korean peninsula.</p>]]>
    </content>
</entry>

<entry>
    <title>North Korea Suffers Outage</title>
    <link rel="alternate" type="text/html" href="http://www.renesys.com/blog/2013/03/north-korea-suffers-outage.shtml" />
    <id>tag:www.renesys.com,2013:/blog//1.238</id>

    <published>2013-03-15T19:47:28Z</published>
    <updated>2013-03-30T10:48:09Z</updated>

    <summary> Earlier this morning, North Korea accused the United States of conducting a cyber attack that disrupted their Internet connectivity. While the details remain unknown, we can confirm that, in the last two days, North Korea&apos;s sole Internet provider has...</summary>
    <author>
        <name>Doug Madory</name>
        <uri>http://www.renesys.com</uri>
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://www.renesys.com/blog/">
        <![CDATA[<table><tr><td style="vertical-align:top" >
<br>
<p>
Earlier this morning, 
<a href="http://www.foxnews.com/world/2013/03/15/north-korea-accuses-us-south-korea-causing-internet-outage-in-cyber-attack/">North Korea accused the United States</a> of conducting a cyber attack that disrupted their Internet connectivity. 
While the details remain unknown, 
we can confirm that, in the last two days, 
North Korea's sole Internet provider has had ongoing problems staying connected to the global Internet. 
We'll summarize some of our evidence in this blog entry.
</p>
</td><td>
<img src="http://www.renesys.com/blog/assets_c/2013/03/800px-Flag_of_North_Korea-thumb-300x150-917.png" width="300" height="150" alt="800px-Flag_of_North_Korea.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px  20px;" /></td></tr></table>
<br><br>
]]>
        <![CDATA[<p>
<strong>Internet in North Korea</strong>
</p>

<p>
North Korea has an <a href="https://twitter.com/renesys/status/289463913383358464">extremely small Internet</a> for a country of 24 million people. Not counting the network involved in the <a href="http://www.timeslive.co.za/scitech/2013/03/06/north-korea-move-by-pirate-bay-a-hoax">recent Pirate Bay hoax</a>, the four networks of North Korea are routed by a single Internet service provider, Star JV (AS&nbsp;131279), which has two international Internet service providers: <a href="http://eng.chinaunicom.com">China Unicom</a> (AS&nbsp;4837) and <a href="http://en.wikipedia.org/wiki/Intelsat">Intelsat</a> (AS&nbsp;22351). Star began service on 18&nbsp;November 2010 and gained Intelsat as a provider on 8&nbsp;April 2012.
</p>

<a href="http://www.renesys.com/blog/assets_c/2013/03/131279_KP-901.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/03/131279_KP-901.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/03/131279_KP-thumb-300x257-901.png" width="300" height="257" alt="131279_KP.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></a>

<p><strong>Recent Disruptions</strong></p>

<p>
We observed disruptions in North Korean Internet connectivity beginning at 00:59:30 UTC on 13&nbsp;March 2013.  At this time, North Korea's four networks were very briefly removed from the global routing table (chart lower left). 

When the routes were restored, one of the four networks was routed over Intelsat,
while the other three were routed over China Unicom. 
After a few hours, all networks were once again routed over China Unicom. 
For about two hours starting at 22:40 UTC on 13&nbsp;March, 
all four networks disappeared for a second time from the global routing table. 
Later on 14&nbsp;March, 
we saw Intelsat again appear as a provider for one of the networks for several hours.
</p>
<p>
Despite such routing instabilities,
North Korean networks were generally available in the global routing table. 
However, when we look at our active measurements (i.e., traceroutes) into North Korea during this time, 
we see a significant drop-off in successful responses,
 suggesting a loss of connectivity not visible in routing data alone (chart lower right).
</p>

<table><tr><td>
<a href="http://www.renesys.com/blog/assets_c/2013/03/pirt_routing_KP-904.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/03/pirt_routing_KP-904.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/03/pirt_routing_KP-thumb-300x257-904.png" width="300" height="257" alt="pirt_routing_KP.png" class="mt-image-center" style="text-align: center; display: block; margin: 20px 20px 20px;" /></a>
</td><td>
<a href="http://www.renesys.com/blog/assets_c/2013/03/KP.March2013.traces3.ASedges.upstreamsof131279-907.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/03/KP.March2013.traces3.ASedges.upstreamsof131279-907.shtml','popup','width=840,height=719,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/03/KP.March2013.traces3.ASedges.upstreamsof131279-thumb-300x256-907.png" width="300" height="256" alt="KP.March2013.traces3.ASedges.upstreamsof131279.png" class="mt-image-center" style="text-align: center; display: block; margin: 20px 20px 20px;" /></a>
</td></tr></table>

<br>
<p>
The following graphic presents another view of latencies into North Korea,
constructed from recent measurements using all of our worldwide servers. 
This perspective helps illustrate the disruption of connectivity. 
Traceroutes through Intelsat appear for some North Korean hosts as they failover to satellite service.
</p>
<br>
<a href="http://www.renesys.com/blog/assets_c/2013/03/latencies_KPoutage_AllSources_b_s-913.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/03/latencies_KPoutage_AllSources_b_s-913.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/03/latencies_KPoutage_AllSources_b_s-thumb-400x342-913.png" width="400" height="342" alt="latencies_KPoutage_AllSources_b_s.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></a>

<p>
Rest easy everyone. The Pirate Bay was unharmed in this incident.
</p>]]>
    </content>
</entry>

<entry>
    <title>Faraway Fallout from Black Sea Cut</title>
    <link rel="alternate" type="text/html" href="http://www.renesys.com/blog/2013/02/faraway-fallout-from-black-sea.shtml" />
    <id>tag:www.renesys.com,2013:/blog//1.237</id>

    <published>2013-02-14T15:19:00Z</published>
    <updated>2013-03-16T09:49:50Z</updated>

    <summary> Last month, Wired.com&apos;s fascinating geological sciences blog, Eruptions, cast doubt on the purported cause of the December 23, 2012 failure of the Georgia-Russia submarine cable. That is, the author of the Eruptions blog post thought it unlikely to have...</summary>
    <author>
        <name>Doug Madory</name>
        <uri>http://www.renesys.com</uri>
    </author>
    
        <category term="Caucasus" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Middle East" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Natural Disaster" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Submarine Cables" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="georgia" label="Georgia" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="omantel" label="OmanTel" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="armenia" label="armenia" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="armentel" label="armentel" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="delta" label="delta" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="epeg" label="epeg" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="iran" label="iran" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="oman" label="oman" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="russia" label="russia" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="submarinecable" label="submarine cable" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://www.renesys.com/blog/">
        <![CDATA[<table><tr><td style="vertical-align:top" >
<p>
Last month,
<a href="http://www.wired.com/">Wired.com</a>'s fascinating geological sciences blog, <a href="http://www.wired.com/wiredscience/eruptions/">Eruptions</a>, cast <a href="http://www.wired.com/wiredscience/2013/01/submarine-eruption-in-the-black-sea-off-georgia-not-likely/">doubt</a> on the <a href="http://en.trend.az/regions/scaucasus/georgia/2105346.html">purported cause</a> of the December 23, 2012  failure of the <a href="http://www.georgia-russia.dk/">Georgia-Russia submarine cable</a>. 
That is, the author of the Eruptions blog post thought it unlikely to have been due to an undersea volcanic eruption. 
Without weighing in on the likelihood of active volcanoes in the Black Sea, 
we <a href="https://twitter.com/renesys/status/289824935612932096">tweeted</a> about some of the Internet impacts of this incident, 
although in 140 characters, we could only scratch the surface.
We'll take a more in-depth look in this blog, 
noting shifts in traffic as far away as Oman, more than 3,000 kilometers distant!
</p>
</td>

<td>
<a href="http://www.renesys.com/blog/assets_c/2013/02/blacksea_cables-874.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/02/blacksea_cables-874.shtml','popup','width=994,height=675,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/02/blacksea_cables-thumb-300x203-874.png" width="300" height="203" alt="blacksea_cables.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></a>
</td></tr></table>]]>
        <![CDATA[
<p><strong>Fiber Cuts in the Caucasus</strong></p>

<table><tr><td style="vertical-align:top" >
<p>
But first, let's consider some recent history.
The last time a fiber optic cable cut in the Caucasus grabbed international attention was almost two years ago (March 28, 2011) when a 75 year old Georgian woman <a href="http://www.dailymail.co.uk/news/article-1374027/Georgian-pensioner-facing-jail-cutting-Armenia-s-internet-snipping-cable.html">reportedly severed</a> the major terrestrial fiber optic cable serving the region while collecting scrap metal.
</p>

<p>
After her arrest, 
she told the press she had never heard of "the Internet" and that <a href="http://www.dailytelegraph.com.au/technology/pensioner-devastated-after-being-arrested-for-cutting-off-internet-to-armenia/story-fn7bsi21-1226037252829">she did <strong>not</strong> break the cable</a>,
which knocked out <strong><u>western</u> </strong>Internet transit for providers in Georgia and Armenia at exactly 13:00 UTC. 
I emphasize <strong>western</strong> because Russian incumbent, <a href="http://www.rostelecom.ru/">Rostelecom</a>, 
was still serving the region from <a href="http://en.wikipedia.org/wiki/Baku">Baku, Azerbaijan</a> during the fiber outage. 
<a href="http://www.bbc.co.uk/news/world-europe-12985082">Headlines</a> suggesting Armenia was completely offline were incorrect, 
the cut just shifted the remaining Georgian and Armenian traffic through Rostelecom until the fiber was fixed less than 8 hours later at 20:32 UTC.
</p>
</td><td>
<a href="http://www.renesys.com/blog/assets_c/2013/02/258446-hayastan-shakarian-895.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/02/258446-hayastan-shakarian-895.shtml','popup','width=316,height=237,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/02/258446-hayastan-shakarian-thumb-300x225-895.jpg" width="300" height="225" alt="258446-hayastan-shakarian.jpg" class="mt-image-center" style="text-align: center; display: block; margin: 10px 10px 10px;" /></a>
</td></tr></table>

<p>
Although Armenian incumbent <a href="http://en.wikipedia.org/wiki/Armenia_Telephone_Company">Armentel</a> was entirely dependent on the severed cable, 
other Internet providers in Armenia such as <a href="http://www.fibernet.am/en/index.html">Fibernet</a>,
which had Russian transit,
were able to survive the incident relatively unscathed. 
In the graphics below, 
we observe traceroute measurements into both Armentel (AS 12297) and Fibernet (AS 41965) on March 28, 2011. 
</p>

<br><br>
<table><tr><td>
<a href="http://www.renesys.com/blog/assets_c/2013/02/12297.mar2011.traces.ASedges.upstreamsof12297-868.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/02/12297.mar2011.traces.ASedges.upstreamsof12297-868.shtml','popup','width=840,height=719,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/02/12297.mar2011.traces.ASedges.upstreamsof12297-thumb-300x256-868.png" width="300" height="256" alt="12297.mar2011.traces.ASedges.upstreamsof12297.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" /></a>
</td><td>
<a href="http://www.renesys.com/blog/assets_c/2013/02/41965.mar2011.traces.ASedges.upstreamsof41965-871.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/02/41965.mar2011.traces.ASedges.upstreamsof41965-871.shtml','popup','width=840,height=719,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/02/41965.mar2011.traces.ASedges.upstreamsof41965-thumb-300x256-871.png" width="300" height="256" alt="41965.mar2011.traces.ASedges.upstreamsof41965.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></a>
</td></tr></table>

<p>
In upper left, 
Armentel's service from global provider <a href="http://www.teliasonera.com/">TeliaSonera</a> and Armentel's parent company, Russian provider <a href="http://www.vimpelcom.com/index.wbp">Vimpelcom</a>, 
were lost during the incident. 
In the upper right, 
Fibernet lost <a href="http://www.level3.com/">Level 3</a> service from the West, 
but not Internet transit from Rostelecom.
</p>

<p>
As a result of this incident, we saw an uptick in western and Russian transit diversity in the region as <a href="http://www.renesys.com/tech/presentations/pdf/ENOG.pdf">presented</a> by my colleague Jim Cowie in June 2011 at the <a href="http://www.enog.org/">Eurasia Network Operators Group </a>conference in Moscow.
</p>

<br><br>
<p><strong>Impacts of the Georgia-Russia cable cut</strong></p>

<p>
After this fiber cut and repair in 2011, 
Internet access to the region was relatively stable until recently.
As we <a href="https://twitter.com/renesys/status/289824935612932096">tweeted</a> last month, 
service into Georgia from Azeri provider <a href="http://www.delta-telecom.net">Delta</a> and service in Armenia via Armentel were impacted by the
Black Sea submarine fiber cut. 
Armentel lost its service from parent company, Vimpelcom, 
initially replacing it with transit through <a href="http://www.co.ge/">Caucasus Online</a> and later TeliaSonera. 
Delta lost its primary transit provider for Georgia, 
Russian provider <a href="http://www.ttk.ru/eng/business/">TransTelecom</a> (TTK) (AS 20485), 
and made up for the loss with additional transit from  
<a href="http://www.tatacommunications.com/">Tata</a> (AS 6453) and Level 3 (AS 3356) to the west and Rostelecom to the east.
</p>

<br><br>
<table><tr><td>
<a href="http://www.renesys.com/blog/assets_c/2013/02/12297_AM_blacksea-880.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/02/12297_AM_blacksea-880.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/02/12297_AM_blacksea-thumb-300x257-880.png" width="300" height="257" alt="12297_AM_blacksea.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" /></a>
</td><td>
<a href="http://www.renesys.com/blog/assets_c/2013/02/29049_GE_blacksea-883.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/02/29049_GE_blacksea-883.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/02/29049_GE_blacksea-thumb-300x257-883.png" width="300" height="257" alt="29049_GE_blacksea.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></a>
</td></tr></table>

<p>
On Tuesday of this week, 
<a href="http://www.panarmenian.net/eng/news/145367/">headlines</a> in Armenia carried the news that Armentel had just days prior expanded their international bandwidth capacity by again acquiring service from TeliaSonera. 
Prior to the headlines, 
users of Renesys's 
<a href="http://www.renesys.com/products_services/market_intel/">Market Intelligence</a> had spotted the change in service in its news feed.
</p>
<br><br>

<a href="http://www.renesys.com/blog/assets_c/2013/02/armentel_news-877.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/02/armentel_news-877.shtml','popup','width=764,height=245,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/02/armentel_news-thumb-300x96-877.png" width="300" height="96" alt="armentel_news.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></a>

<p><strong>Impacts on Iranian Transit</strong></p>

<p>Providers in Georgia and Armenia were not the only ones to lose Russian transit when the Georgia-Russia cable failed. Iran also uses Russian transit to access the Internet, some of which was dependent on that cable. On January 7, Iranian news carried a <a href="http://www.ictna.ir/id/052590/">story</a> <a href="http://translate.google.com/translate?hl=en&sl=fa&u=http://www.ictna.ir/id/052590/&prev=/search%3Fq%3Dhttp://www.ictna.ir/id/052590/%26hl%3Den%26client%3Dfirefox-a%26hs%3Dsk7%26tbo%3Dd%26rls%3Dorg.mozilla:en-US:official&sa=X&ei=_SAcUcjLBYXV0gGshoGQDw&ved=0CDcQ7gEwAA">(cached English translation)</a> with the headline "Internet slow over the last week due to an earthquake reported in Georgia". </p>

<p>
Iranian incumbent <a href="http://tci.ir/default.aspx?lang=En">TIC</a>, 
previously known as DCI, 
uses two ASNs for its International gateways, 
AS 12880 and since last year, AS 48159. 
As can be seen from the transit shift graphics below, 
the fiber break had no impact on upstreams of AS 12880. 
However, AS 48159 lost its service from Rostelecom when the cable was cut. 
What is more interesting is that the loss of Rostelecom for AS 48159 appears to have immediately triggered the activation of a dormant backup transit link from Omantel. 
This is the first time we have seen Omantel providing Internet service in Iran (although we did observe Omantel and TIC testing this connection from November 3 to 7, 2012).
For good measure, TIC also added Delta as a provider in early January for both of its ASNs 
&mdash; representing another completely new business relationship. Of course, all of these changes were also identified in <a href="http://www.renesys.com/products_services/market_intel/">Market Intelligence</a>.
</p>

<table>
<tr><td>
<a href="http://www.renesys.com/blog/assets_c/2013/02/12880_IR_blacksea-886.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/02/12880_IR_blacksea-886.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/02/12880_IR_blacksea-thumb-300x257-886.png" width="300" height="257" alt="12880_IR_blacksea.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" /></a>
</td><td>
<a href="http://www.renesys.com/blog/assets_c/2013/02/48159_IR_blacksea-889.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/02/48159_IR_blacksea-889.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/02/48159_IR_blacksea-thumb-300x257-889.png" width="300" height="257" alt="48159_IR_blacksea.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" /></a>
</td></tr></table>


<table><tr><td>
<p>The activation of this connection could be evidence that the final leg of the <a href="http://www.epegcable.com/">Europe-Persia Express Gateway (EPEG)</a> fiber optic cable connecting Iran to Oman has been completed. 
It was this segment of the cable system that was blamed for the <a href="http://www.telegeography.com/products/commsupdate/articles/2012/08/07/epeg-launch-delayed/">delay of the launch</a> of EPEG last year. 
Two weeks ago, 
Azeri press announced <a href="http://abc.az/eng/news/71307.html">EPEG would be activated</a> this month. 
If activated, 
EPEG could serve as a vital terrestrial alternative to the dozen or so <a href="http://www.submarinecablemap.com/">submarine fiber optic cables</a> through the Suez canal which connect Europe and Asia &mdash; thereby mitigating this potential single point of failure for global communications.
</p></td><td>
<a href="http://www.renesys.com/blog/assets_c/2013/02/epeg-898.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/02/epeg-898.shtml','popup','width=900,height=630,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/02/epeg-thumb-200x140-898.png" width="200" height="140" alt="epeg.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></a>
</td></tr></table>

<p><strong>So was it an undersea Volcano?</strong></p>

<table><tr><td style="vertical-align:top">
<p>
The most likely cause of the cable break in the Black Sea was the 
<a href="http://earthquake.usgs.gov/earthquakes/pager/events/us/c000ef8l/index.html">magnitude 5.7 earthquake</a>,
which struck a little more than an hour before traffic stopped flowing and appears to have
occurred under the path of the cable.
Regardless of the cause, 
it is fascinating to see how an earthquake in the Black Sea can immediately impact Internet pathways as far away as Oman.
The Black Sea and the Caucasus are the Internet crossroads where Russian, Turkish, Gulf State, and Central Asian traffic mingle on their way to the datacenters of Western Europe and the Americas.  Small impacts to particular cables can have large impacts on the flow of traffic regionally. Such is the Internet and our increasingly interconnected world. If you want to learn more from the operators involved, come join us at <a href="http://www.menog.org/meetings/menog-12/">MENOG 12 </a>(March 6, Dubai) and <a href="http://www.enog.org/meetings/enog-5/">ENOG 5</a> (May 27-28, St Petersburg).
</p>
</td><td>
<a href="http://www.renesys.com/blog/assets_c/2013/02/exposure-892.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/02/exposure-892.shtml','popup','width=540,height=558,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/02/exposure-thumb-300x310-892.png" width="200" height="205" alt="exposure.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></a>
</td></tr></table>]]>
    </content>
</entry>

<entry>
    <title>Bangladesh Connects via India</title>
    <link rel="alternate" type="text/html" href="http://www.renesys.com/blog/2013/01/bangladesh-connects-via-india.shtml" />
    <id>tag:www.renesys.com,2013:/blog//1.235</id>

    <published>2013-01-29T14:02:31Z</published>
    <updated>2013-03-16T09:44:16Z</updated>

    <summary> The Internet of Bangladesh has been connected to the world by a single submarine cable, Sea-Me-We 4 (SMW4), since this 18,800 kilometer-long optical-fiber system made its landing at Cox&apos;s Bazar in 2006. However, in the nearly seven years since...</summary>
    <author>
        <name>Doug Madory</name>
        <uri>http://www.renesys.com</uri>
    </author>
    
        <category term="Internet" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Latency" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="South Asia" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Submarine Cables" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.renesys.com/blog/">
        <![CDATA[<table><tr><td style="vertical-align:top" >

<p>
The Internet of Bangladesh has been connected to the world by a <em>single</em> submarine cable, <a href="http://en.wikipedia.org/wiki/SEA-ME-WE_4">Sea-Me-We 4 (SMW4)</a>,
since this 18,800 kilometer-long optical-fiber system made its landing at 
<a href="http://en.wikipedia.org/wiki/Cox%27s_Bazar">Cox's Bazar</a> 
in <a href="http://www.thedailystar.net/2006/05/22/d6052201033.htm">2006</a>.
However, in the nearly seven years since SMW4's activation, 
national Internet outages have plagued Bangladesh with some regularity. 
When their portion of this system is
<a href="http://www.thedailystar.net/newDesign/news-details.php?nid=11573">sabotaged</a>, 
suffers a
<a http://www.renesys.com/blog/2012/06/smw4-break-on-south-asia.shtml">failure</a> 
or is down for <a href="http://www.thedailystar.net/newDesign/latest_news.php?nid=31352">maintenance</a>, 
virtually all Internet bandwidth for the 
<a href="http://en.wikipedia.org/wiki/Demographics_of_Bangladesh">7th most populous country</a> in the world disappears,
forcing local providers to fall back to slow and expensive satellite services or to simply wait for restoration.
</p>

<p>
However, recent national outages due to planned SMW4 maintenance have revealed that some Bangladeshi providers have now activated a long-awaited second connection to the Internet via a <em>terrestrial link to India</em>.
We'll examine this new development here and highlight those providers who
can now offer fault-tolerant Internet service for the first time in Bangladesh.
</p>

</td><td>
<img src="http://www.renesys.com/blog/assets_c/2013/01/India-Bangladesh-thumb-300x240-848.jpg" width="280" height="225" alt="India-Bangladesh.jpg" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" />
</td></tr></table>
]]>
        <![CDATA[<p></p>
<p><strong>The Need for a Backup Link</strong></p>

<p>As far back as 2007, 
only one year after activating the nation's sole submarine cable connection, 
the telecommunications community in Bangladesh began
<a href="http://www.thedailystar.net/newDesign/news-details.php?nid=12837"> advocating for the construction of a secondary physical connection</a> 
to the Internet. 
However, despite years of <a href="http://www.thedailystar.net/newDesign/news-details.php?nid=112313">plans</a> and <a href="http://www.thedailystar.net/newDesign/news-details.php?nid=142877">proposals</a>, 
a second operational submarine cable hookup still seems to be <a href="http://www.thedailystar.net/newDesign/news-details.php?nid=265370">years away</a>.
</p>

<p>
In the meantime, 
major disruptions of Bangladesh's Internet service continue to occur. 
A recent example is the SMW4 fault from last summer,
which we examined <a href="http://www.renesys.com/blog/2012/06/smw4-break-on-south-asia.shtml">here</a>,
a failure that underscored how <a href="http://www.telegeography.com/products/commsupdate/articles/2012/06/11/internet-cut-highlights-need-for-cable-redundancy/">uniquely vulnerable Bangladesh's connectivity</a>
really is.
Such events have prompted the <a href="http://www.btrc.gov.bd/">Bangladesh Telecommunications Regulatory Commission (BTRC)</a> to act. 
In January 2012, 
the <a href="http://www.telecomasia.net/content/six-firms-secure-itc-licenses-bangladesh">BTRC issued licenses</a> 
to six companies to connect to India via the International Terrestrial Cable (ITC).
The six are:
<ul>
  <li><a href="http://www.novocom-bd.com/">Novocom Limited</a>,</li>
  <li><a href="http://www.1asiacom.com/">1Asia</a>,</li>
  <li><a href="http://bdlink.com.bd/">BD Link Communication Ltd.</a>,</li>
  <li><a href="http://www.mango.com.bd">Mango Teleservices Ltd.</a>,</li>
  <li><a href="http://www.summitcommunications.net/scl/">Summit Communications Ltd.</a>, and</li>
  <li><a href="http://www.fiberathome.net/">Fibre@Home Limited</a>.</li>
</ul>
</p>

<p></p>
<strong><p>First evidence of Terrestrial Link to India</p></strong>

<p>
In November, 
we <a href="https://twitter.com/renesys/status/269469896566521857/photo/1"> tweeted</a> the first hard evidence of the ITC in use. 
When Bangladesh's connection to SMW4 was once again taken down for maintenance, Fiber@Home was able to stay online via India, 
while the incumbent BTCL and others were either disconnected or had to rely on satellite back-ups. 
Using our latency measurements into Bangladesh during the outage, 
we were able to identify the impact of SMW4's unavailability on each provider. 
Of the four providers illustrated below, 
only Fiber@Home stayed online (through India) and they even managed to attract additional traffic from dual-homed customers who then had to rely solely on them to maintain connectivity.
</p>

<p>
<a href="http://www.renesys.com/blog/assets_c/2013/01/bd_4charts_nov2012-861.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/01/bd_4charts_nov2012-861.shtml','popup','width=1479,height=1160,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/01/bd_4charts_nov2012-thumb-300x235-861.png" width="300" height="235" alt="bd_4charts_nov2012.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></a>
</p>

<p>The two SMW4 planned outages for Bangladesh on the 19th and 23rd of this month have helped to reveal additional providers which are now receiving Internet transit from <a href="http://www.tatacommunications.com/">India-based Tata</a> via the ITC and no longer solely dependent on SMW4 for Internet access. The graphics below show traceroutes going into providers in Bangladesh during the SMW4 outage from 20:14 to 21:53 UTC on 23 January, 2013. While incumbent BTCL and Mango are completely offline during the downtime, 1Asia, Aamra Technologies, NovoCom and Fiber@Home experienced increases in their traffic as customers automatically shift traffic to the surviving connection. <em>It should be noted that the increase in latencies to Aamra is due to Tata <a href="http://www.renesys.com/blog/2011/10/pinning-down-latency-in-the-mi.shtml">hairpinning</a> traffic to Aamra via Los Angeles, not because it is providing satellite service.</em></p>

<a href="http://www.renesys.com/blog/assets_c/2013/01/bd_6charts_jan2013-864.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/01/bd_6charts_jan2013-864.shtml','popup','width=1469,height=1665,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/01/bd_6charts_jan2013-thumb-300x340-864.png" width="300" height="340" alt="bd_6charts_jan2013.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></a>

<p><strong>Greater Terrestrial Connectivity in Asia</strong></p>

<p><a href="http://lirneasia.net/about/profiles/abu-saeed-khan/">Abu Saeed Khan</a>, the Senior Policy Fellow of <a href="http://lirneasia.net/">LIRNEasia</a>, helped persuade the government of Bangladesh to join the SMW4 consortium in 2002 and has been working ever since to increase Internet inter-connectivity all across South and Southeast Asia. For several years now, he has been advocating his concept called the <a href="http://www.totaltele.com/view.aspx?ID=465754">Longest International Open-access Network</a> (LION) which seeks to have Asian countries migrate from the submarine cables which currently connect them together to terrestrial links, leveraging the extensive international highway system already in existence. The Bangladesh-India link may be a first step towards that reality.</p>

<p>For Bangladesh, the recent establishment of an operational terrestrial connection to India to serve as an alternative to SMW4 is a tremendous accomplishment. As this service becomes more widespread in the country, the recurring national Internet outages should become a thing of the past. 
</p>]]>
    </content>
</entry>

<entry>
    <title>Cuban Fiber: Completo?</title>
    <link rel="alternate" type="text/html" href="http://www.renesys.com/blog/2013/01/cuban-fiber-completo.shtml" />
    <id>tag:www.renesys.com,2013:/blog//1.236</id>

    <published>2013-01-22T19:00:01Z</published>
    <updated>2013-01-29T19:45:54Z</updated>

    <summary>For more latest information, please follow us on Twitter: @Renesys Cuban Internet connectivity continues to evolve by the hour, with a new, faster mode of operation in evidence as of this morning. Our measurements from around the world suggest that...</summary>
    <author>
        <name>Doug Madory</name>
        <uri>http://www.renesys.com</uri>
    </author>
    
    <category term="cuba" label="Cuba" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="telefonica" label="Telefonica" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="venezuela" label="Venezuela" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="submarinecable" label="submarine cable" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://www.renesys.com/blog/">
        <![CDATA[<em><p>For more latest information, please follow us on Twitter: <a href="https://twitter.com/renesys">@Renesys</a> <p></em>

<table><tr><td>
<p>Cuban Internet connectivity continues to evolve by the hour, with a new, faster mode of operation in evidence as of this morning.   Our measurements from around the world suggest that Cuban technicians may have completed the work they began a week ago, creating the first bidirectional Internet paths that are free of satellite connectivity.  </p>
</td><td>

<a href="http://www.renesys.com/blog/assets_c/2013/01/viva-cuba-fiber-858.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/01/viva-cuba-fiber-858.shtml','popup','width=445,height=156,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/01/viva-cuba-fiber-thumb-300x105-858.jpg" width="300" height="105" alt="viva-cuba-fiber.jpg" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></a>

</td></tr></table>
]]>
        <![CDATA[
<p>In our <a href="http://www.renesys.com/blog/2013/01/cuban-mystery-cable-activated.shtml">previous blog</a>, we described how we first detected the signs of change in Cuba's Internet connectivity on Monday, 14 January 2013.    Before that date, everything sent to Cuba experienced a delay of at least half a second, because of the speed of light: every packet sent and received had to travel around 70,000 km (44,000 miles) through space, bouncing off of geostationary satellites and returning to Earth.</p>

<p>On January 14th, we began to see routed paths for data flowing inbound to Cuba through a new service provider, <a href="http://http://www.telefonica.com/en/home/jsp/home.jsp">Telefonica</a>.  At the same time, we saw a second "mode" of latency for Internet traffic emerge, with reduced delays in the 400ms range.  That's fast enough that at least half the path must be terrestrial; we inferred that we were seeing signs of the activation of <a href="http://globalvoicesonline.org/2013/01/10/what-happened-to-the-cable-cubans-discuss-internet-access/">ALBA-1</a> from Venezuela.  </p>

<p>For the next week, however, nothing changed.  People on the ground in Havana reported no changes in Internet performance.   When we wrote our blog on Sunday, it wasn't clear whether this curious one-way connectivity was intentional, or the result of misconfiguration. </p>

<p><a href="http://www.renesys.com/blog/assets_c/2013/01/cuba-annotated-852.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/01/cuba-annotated-852.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/01/cuba-annotated-thumb-300x257-852.png" width="300" height="257" alt="cuba-annotated.png" class="mt-image-right" style="float: right; margin: 0 0 20px 20px;" /></a></p>

<p><strong>Today, that all changed. </strong> At exactly 14:01 UTC Tuesday (09:01 local time), we saw yet another mode emerge in the latency diagrams.   In this plot, you can see the original pure-satellite mode (A), the new asymmetric satellite mode (B), and a third, lower mode (C) that excludes the possibility of geosynchronous satellite service altogether.   At 180-220ms, these paths suggest a pure terrestrial solution, based on subsea and overland cables &mdash; the traditional Internet that nearly everyone else on earth enjoys.   Almost immediately, we started getting reports from Havana that delays for Internet traffic were dropping perceptibly, as the new routing policy kicked in. </p>

<p>What happened here?     We speculate that Cuban network operators changed their routing policy to make the ALBA-1 cable the default path for all outbound traffic from certain Cuban networks.   That would align with what we see in the data:  some satellite providers, like Intelsat, move from mode A to faster mode B (becoming asymmetric: cable outbound, satellite inbound), while some prefixes move from mode B to still faster mode C (becoming symmetric terrestrial: cable outbound, cable inbound).  </p>

<p>We'd like to hear confirmation from the Cuban network operators themselves, and we hope they'll comment below. </p>

]]>
    </content>
</entry>

<entry>
    <title>Mystery Cable Activated in Cuba</title>
    <link rel="alternate" type="text/html" href="http://www.renesys.com/blog/2013/01/cuban-mystery-cable-activated.shtml" />
    <id>tag:www.renesys.com,2013:/blog//1.234</id>

    <published>2013-01-20T14:00:03Z</published>
    <updated>2013-01-29T19:45:11Z</updated>

    <summary>Recent developments captured in a new blog here. (January 22, 2013) In February 2011, the first submarine cable connecting the island nation of Cuba to the global internet (by way of Venezuela) landed on Siboney beach, Santiago de Cuba. In...</summary>
    <author>
        <name>Doug Madory</name>
        <uri>http://www.renesys.com</uri>
    </author>
    
        <category term="Caribbean" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Internet" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Latency" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Submarine Cables" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="cuba" label="Cuba" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="telefonica" label="Telefonica" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="venezuela" label="Venezuela" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="submarinecable" label="submarine cable" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://www.renesys.com/blog/">
        <![CDATA[<p style="font-size:medium;"><em>Recent developments captured in a new blog <a href="http://www.renesys.com/blog/2013/01/cuban-fiber-completo.shtml">here</a>. (January 22, 2013)</em></p>

<table>
<tr><td style="vertical-align:center" ><p>In February 2011, 
the first submarine cable connecting the island nation of Cuba to the global internet 
(by way of Venezuela) 
<a href="http://www.cubadebate.cu/noticias/2011/02/09/el-cable-de-fibra-optica-ya-esta-en-santiago-de-cuba/">landed on Siboney beach, Santiago de Cuba</a>. 
In the two years since, the fate of the cable has been a 
<a href="http://latino.foxnews.com/latino/news/2012/05/21/cuba-mystery-over-undersea-internet-cable/">mystery</a> for <a href="http://laredcubana.blogspot.com/2012/05/what-happened-to-alba-1-undersea-cable.html">Cuba</a> <a href="http://globalvoicesonline.org/2013/01/10/what-happened-to-the-cable-cubans-discuss-internet-access/">observers</a>. 
In the past week, 
our global monitoring system has picked up indications that this cable has finally been activated,
although in a rather curious way, as we explain below.
</p>
</td><td>
<a href="http://www.renesys.com/blog/assets_c/2013/01/alba_cable-836.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/01/alba_cable-836.shtml','popup','width=825,height=679,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/01/alba_cable-thumb-300x246-836.png" width="300" height="246" alt="alba_cable.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" /></a>
</td></tr></table>
]]>
        <![CDATA[<p>
<strong>Connecting Cuba to the Internet</strong>
</p>
<p>
In 2007, state-owned telecommunications companies from <a href="http://www.telegeography.com/products/commsupdate/articles/2007/10/01/venezuela-cuba-cable-set-for-2009/">Cuba and Venezuela joined forces</a> to build a submarine cable between the two Caribbean nations,
linking Cuba directly to the global Internet and allowing it to end its reliance on satellite-based Internet services. 
At least that was the hope.
The cable was named the "<a href="http://www.cubadebate.cu/noticias/2010/01/07/aumenta-la-capacidad-de-conexion-de-la-internet-cubana/">Alternativa Bolivariana para los Pueblos de nuestra América</a>" or ALBA-1 for short. 
</p>

<p>Originally planned to be completed in 2009, 
the project hit <a href="http://www.telegeography.com/products/commsupdate/articles/2010/10/15/havana-laugh-cuba-venezuela-cable-delayed-until-july-at-the-earliest/">delay</a> after <a href="http://www.telegeography.com/products/commsupdate/articles/2011/02/11/close-but-no-cigar-cuban-cable-lands-launch-not-until-july/">delay</a>, 
until <a href="http://www.cubadebate.cu/noticias/2011/01/18/llega-a-venezuela-buque-con-fibra-optica-para-cuba/">construction was finally completed</a> in early 2011. However, despite the announcement of its completion, 
Cuba's Internet has still limped along on high-latency satellite service via three different Internet service providers. 
<em>That is, until last Monday when we noticed that Spanish telecom giant <a href="http://www.telefonica.com/en/home/jsp/home.jsp">Telefonica</a>
began service to 
<a href="http://www.etecsa.cu/">Empresa de Telecomunicaciones de Cuba S.A. (ETECSA)</a>, 
the state telecom of Cuba.
</em></p>

<p>
To underscore the significance of this development, 
we look back at how ETECSA obtained Internet service over the past 6 years.
During this period, 
we see the same three satellite providers,
although the routes carried over each has varied considerably over the years (below left). 
However, zooming in on the last couple of months, 
we see the entrance of Telefonica in our routing data as of last week (below right).

<p>
<table><tr><td>
<a href="http://www.renesys.com/blog/assets_c/2013/01/11960_CU_2007_2013-839.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/01/11960_CU_2007_2013-839.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/01/11960_CU_2007_2013-thumb-300x257-839.png" width="300" height="257" alt="11960_CU_2007_2013.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" /></a>
</td><td>
<a href="http://www.renesys.com/blog/assets_c/2013/01/11960_CU_since_01sep12-842.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/01/11960_CU_since_01sep12-842.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/01/11960_CU_since_01sep12-thumb-300x257-842.png" width="300" height="257" alt="11960_CU_since_01sep12.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" /></a>
</td></tr></table>
</p>

<p>
<table><tr><td style="vertical-align:top">
<p>In addition to our routing data, 
we observe traceroutes into Cuba following a new path via Telefonica and recording significantly lower latencies. 
Latency measurements from four cities are illustrated in the graphic on the right.</p>
<p>
We must emphasize <em>lower </em>latencies because, despite the drop, these aren't exactly <em>low</em> latencies. 
Our measured latencies to Cuba are still quite high, albeit improved. 
The fact that the latencies to Cuba from many locations around the world have dropped below 480ms means that the new Telefonica service cannot be entirely via satellite. 
However, if it were solely via submarine cables, 
we would expect latencies from many nearby countries to be less than 50ms.
<em> (Note: Round trip latencies for crossing the Atlantic and Pacific oceans are approximately 60ms and 110ms, respectively.)</em>
</p>
</td><td>
<a href="http://www.renesys.com/blog/assets_c/2013/01/latencies_to_cuba-845.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/01/latencies_to_cuba-845.shtml','popup','width=1477,height=1277,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/01/latencies_to_cuba-thumb-300x259-845.png" width="300" height="259" alt="latencies_to_cuba.png" class="mt-image-center" style="text-align: center; display: block; margin: 0 20px 20px;" /></a>

</td></tr></table>

<p>
<strong>Conclusions</strong>
</p>
<p>
We believe it is likely that Telefonica's service to ETECSA is, 
either by design or misconfiguration, 
using its new cable asymmetrically (i.e., for traffic in only one direction), 
similar to the situation we observed in <a href="http://www.renesys.com/blog/2011/11/lebanese-providers-drop-satell.shtml">Lebanon</a> in 2011. 
In such a configuration, 
ETECSA enjoys greater bandwidth and lower latencies (along the submarine cable) when receiving Internet traffic but continues to use satellite services for sending traffic.

While the activation of the ALBA-1 cable may be a good first step to providing ETECSA a better link to the Internet, 
the lack of <a href="http://www.havanatimes.org/?p=85719">widespread public access to Internet service</a> throughout the island will likely continue.
</p>

<p>
On the same day last week that we saw the first evidence of the ALBA-1 cable, 
Cuba <a href="http://www.latimes.com/news/world/worldnow/la-fg-wn-cuba-travel-reform-20130114,0,3264251.story">eliminated the requirement of an exit visa</a> for its people to travel outside the country. 
Could these two developments be part of a greater trend towards a freer and more open Cuba?
</p>]]>
    </content>
</entry>

<entry>
    <title>A Baker&apos;s Dozen, 2012 Edition</title>
    <link rel="alternate" type="text/html" href="http://www.renesys.com/blog/2013/01/a-bakers-dozen-2012-edition.shtml" />
    <id>tag:www.renesys.com,2013:/blog//1.233</id>

    <published>2013-01-17T17:58:43Z</published>
    <updated>2013-01-24T12:39:28Z</updated>

    <summary> It is an annual tradition at Renesys to provide a year-end review of how the Internet providers at the top of our Market Intelligence global rankings fared over the previous year. The Internet remains a huge blind spot for...</summary>
    <author>
        <name>Earl Zmijewski</name>
        <uri>http://www.renesys.com/blog/</uri>
    </author>
    
    <category term="nsp" label="NSP" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="rankings" label="Rankings" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="tier1" label="Tier-1" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://www.renesys.com/blog/">
        <![CDATA[<p>
It is an annual tradition at Renesys to provide a year-end review
of how the Internet providers at the top of our 
<a href="http://www.renesys.com/products_services/market_intel/index.shtml">Market Intelligence</a> global rankings fared over the previous year. 
The Internet remains a huge blind spot for many organizations that are buying Internet access.  
Market Intelligence provides the insight into who the leaders in the Internet transit marketplace are today and how they have changed over time.
Back in <a href="http://www.renesys.com/blog/2008/12/winners-and-losers-for-2008.shtml">2008</a>, 
we chose to look at the 13 providers that spent at least some time in the Top Ten that year, 
hence the name 
"<a href="http://dictionary.reference.com/browse/baker%27s+dozen">Baker's Dozen</a>". 
We looked at the top players again in 
<a href="http://www.renesys.com/blog/2009/12/a-bakers-dozen-in-2009.shtml">2009</a>,
<a href="http://www.renesys.com/blog/2011/01/a-bakers-dozen-2010-edition.shtml">2010</a>
and 
<a href="http://www.renesys.com/blog/2012/02/a-bakers-dozen-2011-edition.shtml">2011</a>.
A lot has changed over the years and for 2012,
we welcome two new members to this exclusive club,
PCCW and XO.
As predicted last year,
we also say good-bye to a declining AT&amp;T and Savvis.
While AT&amp;T's departure from the top of the global stage may be surprising
to some,
Savvis really hasn't left as it is now part of CenturyLink,
which also owns Qwest.
And while Qwest did leave our top global rankings in 2011,
they have now returned as part of a reinvigorated CenturyLink.
</p>

<p>
As you read this blog,
keep in mind that all of the rankings we discuss are relative to IPv4,
the Internet protocol carrying over 99% of all Internet traffic.
(For example,
compare <a href="https://www.ams-ix.net/statistics">total traffic</a> to 
<a href="https://www.ams-ix.net/technical/statistics/sflow-stats/ipv6-traffic">IPv6 traffic</a> at the very busy 
<a href="https://www.ams-ix.net/">Amsterdam Internet Exchange</a>.)
While we did also review IPv6 rankings last year, 
so little has changed that we'll just refer you to 
<a href="http://www.renesys.com/blog/2012/02/a-bakers-dozen-2011-edition.shtml">that blog</a> or, for more current information, our
<a href="http://www.renesys.com/products_services/market_intel/index.shtml">Market Intelligence</a> product offering which covers both IPv4 and IPv6 in detail.
So let's dive in and highlight a few of the trends and changes we observed in 2012.
</p>]]>
        <![CDATA[
<hr>
<br>
<p><strong>And the Winners are &#0133;</strong></p>

<p>
<a href="http://www.renesys.com/blog/assets_c/2013/01/2102-bakers-dozen-823.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/01/2102-bakers-dozen-823.shtml','popup','width=690,height=400,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/01/2102-bakers-dozen-thumb-690x400-823.jpg" width="690" height="400" alt="2102-bakers-dozen.jpg" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></a>
</p>

<p>
This graph shows our global scores for the Baker's Dozen over the past year.  
As always, the absolute scores are not meaningful in this context, so we omit the scale.
Five years ago, at the beginning of 2008, 
the top five in our rankings were Sprint, Level 3, Verizon, NTT and Global Crossing, 
in that order.
Sprint has been steadily declining ever since and, as 2013 begins, 
was just surpassed by Tata, 
leaving it at 7th globally.
Level 3 has acquired number-2 Global Crossing to become the undisputed number 1,
and NTT and TeliaSonera are in a tight race for number 2.
Verizon has dropped to 8th overall.
In other words, the deck has been thoroughly reshuffled in a few short years.
To make sense of the tangled graph above,
we'll divide up the players into three tiers and zoom in on each.
</p>

<hr>
<br>
<p><strong>On Top of the World &#0133;</strong></p>

<p>
<a href="http://www.renesys.com/blog/assets_c/2013/01/top-tier-826.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/01/top-tier-826.shtml','popup','width=690,height=400,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/01/top-tier-thumb-690x400-826.jpg" width="690" height="400" alt="top-tier.jpg" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></a>
</p>

<p>Level 3 (AS 3356) completed their
<a href="http://www.prnewswire.com/news-releases/level-3-completes-acquisition-of-global-crossing-131036448.html">acquisition of Global Crossing</a> (AS 3549) in 
October of 2011.  
We show them as separate entities here, 
since their networks have not yet been merged.
In previous acquisitions,
Level 3 has quickly absorbed the other organization.
Thus we expected to see the old Global Crossing AS fall off dramatically in 2012,
while the Level 3 AS soared.
That was not the case.
Instead, both entities declined steadily in the first half of the year before leveling out.
The decline is best explained by several small changes, rather than any one large customer loss.
Perhaps the market is adjusting to the merger by buying other transit in an attempt to preserve diversity?
A wide range of customers reduced the number of networks that they had previously routed via Level 3,
such as North America's nLayer (AS 25973, and recently acquired by Global Telecom &amp; Technology, Inc. (GTT)), Japan's Softbank (AS 4725), Britain's Easynet Global Services (AS 4589) and Brazil's Embratel (AS 4230).  
But one of the more significant reductions was due to a drop-off by Cable and Wireless Worldwide (AS 1273), 
starting in the spring of 2012.
</p>

<p>
Despite these losses,
the combined North American-based Level 3/Global Crossing score is still more than twice that of its nearest competitors, 
East Asian carrier NTT (AS 2914) and Eurasian carrier TeliaSonera (AS 1299),
both of which have vied for the number-2 spot throughout the year.
But with Level 3 declining or at best stagnating,
the competition is gaining ground as the Internet continues to expand.
When we 
<a href="http://www.renesys.com/blog/2011/04/level-crossing.shtml">first reported</a>
on the proposed Level 3/Global Crossing merger in April of 2011,
we stated that the next five global providers would have to combine to rival the score of 
new mega-Level 3.
Now, "only" the next three would have to do so, namely, NTT, TeliaSonera and Inteliquent.
It will be interesting to see if this trend continues in 2013.
</p>

<p>
But absent dramatic consolidation, 
it's safe to say the global race is now for the number-2 position.
While TeliaSonera was briefly ahead of NTT at the end of the summer,
NTT has more recently reasserted itself and appears to be gaining on its 
nearest competitor.
NTT saw increases in transit from Japan's KDDI (AS 2516),
South Korea's LG DACOM (AS 3786) and a surging China Mobile (AS 58453) to name just a few.
TeliaSonera saw dramatic increases in transit from SingTel (AS 7473).
Clearly Asia, with most of the world's population and still relatively 
<a href="http://www.internetworldstats.com/stats.htm">low Internet penetration</a>, 
will remain a key battleground for years to come.
This is a region of the world where we rank Level 3 second as AS 3356 and fifth as AS 3549.
</p>

<hr>
<br>
<p><strong>Closest Thing to Heaven &#0133;</strong></p>

<p>
<a href="http://www.renesys.com/blog/assets_c/2013/01/middle-tier-829.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/01/middle-tier-829.shtml','popup','width=690,height=400,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/01/middle-tier-thumb-690x400-829.jpg" width="690" height="400" alt="middle-tier.jpg" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></a>
</p>

<p>
After leaving the rarefied air of the top three providers,
we encounter our next group of five very strong global carriers.
Here we see Inteliquent (AS 3257),
formerly <a href="http://en.wikipedia.org/wiki/Inteliquent">Neutral Tandem and Tinet</a>,
Cogent (AS 174) and Tata (AS 6453) keeping up with the overall growth of the Internet.
Sprint (AS 1239), which was about to be passed by TeliaSonera at last year this time, 
has now just been passed by Tata.
If they continue on this trajectory, 
Sprint may end up in our third group by next year. 
Finally,
Verizon (AS 701) saw an interesting jump at the end of year to get within striking distance of Tata.
</p>

<p>
So where were the big wins?  In Asia, of course.
The main contributor to Inteliquent's rise was a substantial increase in transit from the 16th-ranked Asian carrier, Flag (AS 15412).
Cogent's largest gains came from Korea Telecom (AS 4766),
while Tata's came from Russia's Vimpelcom (AS 3216), Vietnam's VNPT Corporation (AS 45898), Bharti Airtel (AS 9498) and a number of smaller players.
Even Verizon got into the act with a year-end surge largely due to increased transit from China Telecom (AS 4134).
Now China Telecom roughly equally splits its transit needs between Verizon and Sprint.
Without this single enormous customer,
these two US-based carriers would tumble into our third group, 
shown next.
</p>

<hr>
<br>
<p><strong>The Rest of the Best &#0133;</strong></p>

<p>
<a href="http://www.renesys.com/blog/assets_c/2013/01/bottom-tier-832.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2013/01/bottom-tier-832.shtml','popup','width=690,height=400,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2013/01/bottom-tier-thumb-690x400-832.jpg" width="690" height="400" alt="bottom-tier.jpg" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></a>
</p>

<p>
This brings us to the final five of our Baker's Dozen, namely,
Telecom Italia Sparkle (AS 6762), PCCW (AS 3491), China Telecom (AS 4134), XO (AS 2828) and CenturyLink (AS 209).  
CenturyLink acquired both
<a href="http://www.renesys.com/blog/2011/04/qwavvis-the-battle-for-second.shtml"> Qwest and Savvis</a> in 2011.
PCCW entered our Baker's Dozen for the first time this year after solid and consistent gains throughout 2011 and 2012.
XO, after a strong 2011, 
ended up treading water in 2012, but still made the cut for the first time,
thanks to the departure of AT&amp;T and Savvis.
Both Sparkle and CenturyLink stumbled a bit later in the year, 
which kept CenturyLink from passing XO and put PCCW within striking distance of Sparkle.
</p>

<p>
Again, we are seeing the influence of Asia within movement in this third group.
Sparkle's biggest increases came from India's Bharti Airtel and Russia's Vimpelcom.
The decreases later in the year are predominantly due to losing transit from Russia's  Rostelecom (AS 12389) and losing Russia's MegaFon (AS 31133) as a customer entirely.
Meanwhile, PCCW gained significantly from China Mobile's increased transit.
The one exception to Asian influence in our rankings concerns CenturyLink, whose rise was dominated by increased transit from GTT/nLayer.
</p>

<hr>
<br>
<p><strong>Conclusions</strong></p>

<p>
Westerners view the Internet as a commodity and ubiquitous access is taken for granted.  
Unsurprisingly, we continue to see a wave of consolidation in these markets as companies can only "grow" by acquisition.
Organic growth can now only come in underserved markets,
and today we see the battle for global Internet dominance playing out in Asia.
Tomorrow, as its physical infrastructure improves, 
we may see more attention shift to Africa.
Although Asia continues to be the growth engine for many of the Baker's Dozen NSPs, we are starting to see commoditization and market consolidation on its western edge. During the year a number of Russian NSPs successfully integrated their 2011 acquisitions and are now looking for a compelling competitive advantage in a tight IP transit market.
</p>

<p>
But, nearly everywhere you look, 
enterprises have a lot more good choices for Internet transit than they have in years past.
That means that they are becoming more sophisticated consumers of Internet transit, which is why we find ourselves spending more time in 2013 studying Internet
<a href="http://www.renesys.com/tech/presentations/pdf/ENOG3-cowie.pdf">path performance</a>, in addition to the providers' relative market share.
Enterprises are starting to managing the Internet as part of their overall networking strategy and demanding explanations for poor performance from their providers.  
Any provider who can serve an increasingly interconnected world, 
and do so reliably with low latencies in 
<a href="http://www.renesys.com/blog/2011/10/pinning-down-latency-in-the-mi.shtml">good times</a> and 
<a href="http://www.renesys.com/blog/2012/11/sandys-global-impacts.shtml">bad</a>,
will undoubtedly gain customers and grow in our rankings. 
Stay tuned.
</p>]]>
    </content>
</entry>

<entry>
    <title>Restoration in Syria</title>
    <link rel="alternate" type="text/html" href="http://www.renesys.com/blog/2012/12/restoration-in-syria-1.shtml" />
    <id>tag:www.renesys.com,2012:/blog//1.232</id>

    <published>2012-12-01T16:24:57Z</published>
    <updated>2013-01-14T00:08:19Z</updated>

    <summary> Renesys confirms a largely complete restoration of the Syrian Internet this morning, starting at 14:32:10 UTC (16:32 local time in Damascus). Transit providers for the full prefix set do not appear to be significantly changed, with Internet service being...</summary>
    <author>
        <name>James Cowie</name>
        
    </author>
    
        <category term="Middle East" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="syriainternetblackout" label="syria internet blackout" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://www.renesys.com/blog/">
        <![CDATA[<p>
Renesys <strong>confirms</strong> a largely complete restoration of the Syrian Internet this morning, starting at 14:32:10 UTC  (16:32 local time in Damascus). </p>
<p>  

Transit providers for the full prefix set do not appear to be significantly changed, with Internet service being provided post-restoration by Telecom Italia, Tata Communications, Turk Telecom, and PCCW.  
</p><p>
<table><tr><td width="50%">Here's a view of live Syrian prefix counts during the outage and restoration, from 29 November to 1 December:</td><td><a href="http://www.renesys.com/blog/assets_c/2012/12/SY_reachable_Nov29-Dec01-814.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2012/12/SY_reachable_Nov29-Dec01-814.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2012/12/SY_reachable_Nov29-Dec01-thumb-300x257-814.png" width="300" height="257" alt="SY_reachable_Nov29-Dec01.png" class="mt-image-right" style="float: right; margin: 0 0 20px 20px;" /></a>
</td></tr>
</table>
</p>]]>
        <![CDATA[<p>
<table>
<tr><td width="50%">And here's a zoom into the same data, during the period of the restoration:</td>
<td width="50%">
<a href="http://www.renesys.com/blog/assets_c/2012/12/SY_reachable-Dec01-817.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2012/12/SY_reachable-Dec01-817.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2012/12/SY_reachable-Dec01-thumb-300x257-817.png" width="300" height="257" alt="SY_reachable-Dec01.png" class="mt-image-right" style="float: right; margin: 0 0 20px 20px;" /></a></td></tr>
<tr><td>Syrian upstream providers post-restoration look much as they did before the outage;  Turk Telekom's restoration appears to have been delayed by an hour relative to the other providers.</td><td>
<a href="http://www.renesys.com/blog/assets_c/2012/12/syria.restoration.trace.upstreams-820.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2012/12/syria.restoration.trace.upstreams-820.shtml','popup','width=840,height=719,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2012/12/syria.restoration.trace.upstreams-thumb-300x256-820.png" width="300" height="256" alt="syria.restoration.trace.upstreams.png" class="mt-image-right" style="float: right; margin: 0 0 20px 20px;" /></a></td></tr></table>
<p>
</p>
<p>
The restoration was achieved just as quickly and neatly as the outage: like a switch being thrown.   Does that mean that we believe the government (or the opposition) threw the switch?  Frankly, the data available just don't support attribution at this point, despite all the speculation. </p><p>  The only way we're going to know for sure will be to wait for a resolution to the conflict, at which point we will hear from the people who know for sure: the network engineers in Syria.  We hope they're safe and we look forward to hearing their story firsthand.   
</p>]]>
    </content>
</entry>

<entry>
    <title>Could It Happen In Your Country?</title>
    <link rel="alternate" type="text/html" href="http://www.renesys.com/blog/2012/11/could-it-happen-in-your-countr.shtml" />
    <id>tag:www.renesys.com,2012:/blog//1.230</id>

    <published>2012-11-30T16:32:57Z</published>
    <updated>2013-01-14T14:20:14Z</updated>

    <summary><![CDATA[{Updated; see below for lists of countries for easier reference, and a special offer for WCIT attendees. &mdash;jim} How hard is it to disconnect a country from the Internet, really? That's the number one question we've received about our analysis...]]></summary>
    <author>
        <name>James Cowie</name>
        
    </author>
    
        <category term="Engineering" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Governance" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Internet" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="internetblackout" label="Internet blackout" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://www.renesys.com/blog/">
        <![CDATA[<p><strong><em><a href="#postscriptum">{Updated; see below for lists of countries for easier reference, and a special offer for WCIT attendees.  &mdash;jim}</a></em></strong></p><p></p>
<p>
How hard is it to disconnect a country from the Internet, really?
</p><p>
That's the number one question we've received about our analysis of the <a href="http://www.renesys.com/blog/2011/01/egypt-leaves-the-internet.shtml">Egyptian</a> and <a href="http://www.renesys.com/blog/2012/11/syria-off-the-air.shtml">Syrian</a> Internet blackouts, and it's a reasonable question.   If the Internet is so famously resilient, designed to survive wars and calamities, how can it fail so abruptly and completely at the national level?
</p><p>
The key to the Internet's survival is the Internet's decentralization &mdash; and it's not uniform across the world.   In some countries, international access to data and telecommunications services is heavily regulated.  There may be only one or two companies who hold official licenses to carry voice and Internet traffic to and from the outside world, and they are required by law to mediate access for everyone else.  
</p><p>
Under those circumstances, it's almost trivial for a government to issue an order that would take down the Internet.  Make a few phone calls, or turn off power in a couple of central facilities, and you've (legally) disconnected the domestic Internet from the global Internet.   Of course, this level of centralization also makes it much harder for the government to defend the nation's Internet infrastructure against a determined opponent, who knows they can do a lot of damage by hitting just a few targets.  
</p>]]>
        <![CDATA[<p>
With good reason, most countries have gradually moved towards more diversity in their Internet infrastructure over the last decade.    Sometimes that happens all by itself, as a side effect of economic growth and market forces, as many different companies move into the market and compete to provide the cheapest international Internet access to the citizenry.   
</p><p>
Even then, though, there's often a government regulator standing by, allowing (or better yet, encouraging) the formation of a diverse web of direct connections to international providers.   Here's the problem: increased diversity at the international frontier often spells less money for the national incumbent provider (typically the old telephone company, often owned by the government itself).  Without some strong legal prodding and guidance from the telecoms regulator, significant diversification in smaller markets with a strong incumbent can take a long, long time.
</p>

<p>
Here's a map of the world, with countries colored according to the Internet diversity at the international frontier.   We did a census, from our own view of the global Internet routing table, of all the domestic providers in each country who have direct connections (visible in routing) to foreign providers.   
</p>

<br>
<table>
<tr><td>
<p>
<a href="http://www.renesys.com/blog/assets_c/2012/11/renesys.risk.internet.disconnect-810.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2012/11/renesys.risk.internet.disconnect-810.shtml','popup','width=1542,height=1017,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2012/11/renesys.risk.internet.disconnect-thumb-600x395-810.png" width="600" height="395" align="center" alt="renesys.risk.internet.disconnect.png" class="mt-image-right" /></a>
</p>
</td></tr></table>
<br>

<p>
As a first cut at a diversity metric, this makes a lot of sense; it's easy to compute, and fairly objective (an NSP either has a foreign transit provider visible in the routing tables, or it doesn't).     You can think of this, to first approximation, as the number of phone calls (or legal writs, or infrastructure attacks) that would have to be performed in order to decouple the domestic Internet from the global Internet. 
</p>
<ul><li><p>
<strong>If you have only 1 or 2 companies at your international frontier</strong>, we classify your country as being at severe risk of Internet disconnection.   Those 61 countries include places like Syria, Tunisia, Turkmenistan, Libya, Ethiopia, Uzbekistan, Myanmar, and Yemen.  <br/>
</p></li><li><p>
<strong>If you have fewer than 10 service providers at your international frontier</strong>, your country is probably exposed to some significant risk of Internet disconnection.    Ten providers also seems to be the threshold below which one finds significant additional risks from infrastructure sharing &mdash; there may be a single cable, or a single physical-layer provider who actually owns most of the infrastructure on which the various providers offer their services.  In this category, we place 72 countries, including Oman, Benin, Botswana, Rwanda, Pakistan, Kyrgyzstan, Uganda, Armenia, and Iran.   Disconnection wouldn't be trivial, but it wouldn't be all that difficult.   Egypt falls into this category as well; it took the Mubarak government several days to hunt down and kill the last connections, but in the end, the blackout succeeded.<br/>
</p></li><li><p>
<strong>If you have at least 10 internationally-connected service providers, but no more than 40</strong>, your risk of disconnection is fairly low.  Given a determined effort, it's plausible that the Internet could be shut down over a period of days or weeks, but it would be hard to implement and even harder to maintain that state of blackout.     There are 58 countries in this situation, ranging from Bahrain (at the small end) to Mexico (at the largest end).   India, Israel, Ecuador, Chile, Vietnam, and (perhaps surprisingly) China are all in this category. </p><p> So is Afghanistan, reminding us that sometimes national Internet diversity is the product of regional fragmentation and severe technical challenges.  It's true; the government in Kabul is powerless to turn off the national Internet, because it's built out of diverse service from various satellite providers, as well as Uzbek, Iranian, and Pakistani terrestrial transit. 
</p></li><li><p>
<strong>Finally, if you have more than 40 providers at your frontier</strong>, your country is likely to be extremely resistant to Internet disconnection.   There are just too many paths into and out of the country, too many independent providers who would have to be coerced or damaged, to make a rapid countrywide shutdown plausible to execute.   A government might significantly impair Internet connectivity by shutting down large providers, but there would still be a deep pool of persistent paths to the global Internet.    In this category are the big Internet economies: Canada, the USA, the Netherlands, etc., about 32 countries in all.
</p></li>
</ul>

<p>
So, could what happened to Egypt and Syria happen in your country?   Hopefully not.   But it's an important question that companies ask Renesys about all the time, as they decide which countries might reasonably host their new data centers. 
</p><p> 
Governments that want to encourage direct foreign investment in ICT should have this in mind as they head to Dubai next week for the <a href="http://www.itu.int/en/wcit-12/Pages/default.aspx">World Conference on International Telecommunications</a>.   Next to Internet performance and stability, the political risks of Internet disconnection are starting to appear on due diligence checklists, as companies consider where to make their investments in global cloud infrastructure.  
</p>
<p>&nbsp;</p>
<hr/>
<p><a name="postscriptum">
<em><strong>Postscript (3 Dec 2012)</strong></em></a></p>
<p>
Wow, a lot of interest in this subject so far.   Thanks for the comments and questions.   Keep in mind that we're starting with a simple maturity model of foreign/domestic interconnection diversity &mdash; factoring in physical interconnection and the 'hidden entanglements' among the logical relationships is the next step.  It's interesting that most people who are suggesting modifications to this model believe that their country is <em>much more vulnerable</em> to disconnection.  Nobody has claimed that their country is <strong>more</strong> resilient than we give them credit for! </p>
<p>  I'm collecting a list of most-commented countries, and we'll revisit these in some more detail in a future post.</p><p>
Also, many have asked for a browsable list of the countries that appear in the map. Here's a table of the ISO country codes for each of the four categories.  If you'd like more detail on these countries, the relationships among autonomous system providers in them, the size of the incumbents, their international transit arrangements, and the like, I have to recommend that you check out our <a href="http://renesys.com/products_services/market_intelligence/index.shtml">Market Intelligence</a> service.   If you're trying to understand how the online world really fits together at the provider-customer level, region by region and market by market, <a href="http://renesys.com/products_services/market_intelligence/index.shtml">Market Intelligence</a> provides the best roadmap of who's connected to whom in the service provider industry, from San Francisco to Sao Paolo, from Benin to Vladivostok. </p><p><strong>If you're a registered attendee at the WCIT conference in Dubai this week,</strong> <a href="mailto:sales@renesys.com">send me your accreditation</a> and we'll set you up with a free evaluation account. </p>
<p>
<table width="100%">
<tr>
<td style="background-color:#22490a"><font color="#ffffff">Severe Risk</font></td>
<td style="background-color:#489c21"><font color="#ffffff">Significant Risk</font></td>
<td style="background-color:#78bf56">Low Risk</td>
<td style="background-color:#cff8b2">Resistant</td>
</tr>
<tr>
<td style="background-color:#22490a"><font color="#ffffff">
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#AD">AD</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#AI">AI</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#AN">AN</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#AW">AW</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#AX">AX</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#BB">BB</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#BQ">BQ</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#BT">BT</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#CF">CF</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#CI">CI</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#CK">CK</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#CU">CU</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#DJ">DJ</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#DM">DM</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#ET">ET</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#FO">FO</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#GD">GD</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#GF">GF</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#GL">GL</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#GM">GM</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#GN">GN</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#GP">GP</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#GY">GY</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#IO">IO</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#JE">JE</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#KM">KM</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#KN">KN</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#KP">KP</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#LS">LS</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#LY">LY</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#MC">MC</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#MF">MF</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#MH">MH</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#ML">ML</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#MM">MM</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#MR">MR</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#NF">NF</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#NR">NR</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#PF">PF</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#PM">PM</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#PW">PW</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#RE">RE</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#SB">SB</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#SO">SO</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#SR">SR</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#SS">SS</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#ST">ST</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#SX">SX</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#SY">SY</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#SZ">SZ</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#TC">TC</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#TD">TD</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#TK">TK</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#TL">TL</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#TM">TM</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#TN">TN</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#TO">TO</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#UZ">UZ</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#VA">VA</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#WF">WF</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#YE">YE</a> 
</font></td>
<td style="background-color:#489c21"><font color="#ffffff">
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#AE">AE</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#AG">AG</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#AM">AM</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#AZ">AZ</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#BF">BF</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#BI">BI</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#BJ">BJ</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#BM">BM</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#BN">BN</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#BO">BO</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#BS">BS</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#BW">BW</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#BY">BY</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#BZ">BZ</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#CD">CD</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#CG">CG</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#CM">CM</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#CW">CW</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#DO">DO</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#EG">EG</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#FJ">FJ</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#FM">FM</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#GA">GA</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#GE">GE</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#GG">GG</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#GI">GI</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#GQ">GQ</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#GU">GU</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#HT">HT</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#IM">IM</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#IR">IR</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#JM">JM</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#JO">JO</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#KG">KG</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#KY">KY</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#LA">LA</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#LK">LK</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#LR">LR</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#MA">MA</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#ME">ME</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#MG">MG</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#MN">MN</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#MO">MO</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#MQ">MQ</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#MT">MT</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#MU">MU</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#MV">MV</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#MW">MW</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#NA">NA</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#NC">NC</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#NE">NE</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#OM">OM</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#PG">PG</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#PK">PK</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#PY">PY</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#QA">QA</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#RW">RW</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#SA">SA</a> <a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#SC">SC</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#SD">SD</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#SL">SL</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#SM">SM</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#SV">SV</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#TG">TG</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#TJ">TJ</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#TT">TT</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#UG">UG</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#UY">UY</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#VG">VG</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#VI">VI</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#VU">VU</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#WS">WS</a></font></td>
<td style="background-color:#78bf56"><a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#AF">AF</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#AL">AL</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#AO">AO</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#BA">BA</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#BD">BD</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#BG">BG</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#BH">BH</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#CL">CL</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#CN">CN</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#CO">CO</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#CR">CR</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#CY">CY</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#DZ">DZ</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#EC">EC</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#EE">EE</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#GH">GH</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#GR">GR</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#GT">GT</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#HN">HN</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#HR">HR</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#HU">HU</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#IL">IL</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#IN">IN</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#IQ">IQ</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#IS">IS</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#KE">KE</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#KH">KH</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#KR">KR</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#KW">KW</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#KZ">KZ</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#LB">LB</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#LI">LI</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#LT">LT</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#LU">LU</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#LV">LV</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#MD">MD</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#MK">MK</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#MX">MX</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#MZ">MZ</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#NG">NG</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#NI">NI</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#NP">NP</a>
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#NZ">NZ</a>  
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#PA">PA</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#PE">PE</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#PR">PR</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#PS">PS</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#PT">PT</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#RS">RS</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#SI">SI</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#SK">SK</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#TH">TH</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#TR">TR</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#TW">TW</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#TZ">TZ</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#VE">VE</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#VN">VN</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#ZA">ZA</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#ZM">ZM</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#ZW">ZW</a> </td>
<td style="background-color:#cff8b2"><a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#AR">AR</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#AT">AT</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#AU">AU</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#BE">BE</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#BR">BR</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#CA">CA</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#CH">CH</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#CZ">CZ</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#DE">DE</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#DK">DK</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#ES">ES</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#FI">FI</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#FR">FR</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#GB">GB</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#HK">HK</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#ID">ID</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#IE">IE</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#IT">IT</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#JP">JP</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#MY">MY</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#NL">NL</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#NO">NO</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#PH">PH</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#PL">PL</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#RO">RO</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#RU">RU</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#SE">SE</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#SG">SG</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#UA">UA</a> 
<a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#US">US</a> 
</td>
</tr></table></p>]]>
    </content>
</entry>

<entry>
    <title>Syrian Internet Is Off The Air</title>
    <link rel="alternate" type="text/html" href="http://www.renesys.com/blog/2012/11/syria-off-the-air.shtml" />
    <id>tag:www.renesys.com,2012:/blog//1.229</id>

    <published>2012-11-29T13:31:09Z</published>
    <updated>2013-01-14T00:09:42Z</updated>

    <summary>Click for latest update: 01:00 GMT Friday. Starting at 10:26 UTC on Thursday, 29 November (12:26pm in Damascus), Syria&apos;s international Internet connectivity shut down. In the global routing table, all 84 of Syria&apos;s IP address blocks have become unreachable, effectively...</summary>
    <author>
        <name>James Cowie</name>
        
    </author>
    
        <category term="Internet" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Middle East" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="syria" label="Syria" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://www.renesys.com/blog/">
        <![CDATA[<p><a href="#latest"><em>Click for latest update: 01:00 GMT Friday.</em></a></P>

<p>Starting at 10:26 UTC on Thursday, 29 November (12:26pm in Damascus),  Syria's international Internet connectivity <a href="http://www.renesys.com/eventsbulletin/2012/11/SY-1354184790.html">shut down</a>.  In the global routing table, all 84 of Syria's IP address blocks have become unreachable, effectively removing the country from the Internet.</p>

<p>We are investigating the dynamics of the outage and will post updates as they become available.<br />
</p>]]>
        <![CDATA[<table><tr><td style="vertical-align:top"><p><em>Update (15:45 UTC)</em>
</p>
<p>Looking closely at the continuing Internet blackout in Syria, we can see that traceroutes into Syria are failing, exactly as one would expect for a major outage.   The primary autonomous system for Syria is the Syrian Telecommunications Establishment; all of their customer networks are currently unreachable.
</p><p>
Now, there <em>are</em> a few Syrian networks that are still connected to the Internet, still reachable by traceroutes, and indeed still hosting Syrian content.   These are five networks that use Syrian-registered IP space, but the originator of the routes is actually Tata Communications.   These are potentially offshore, rather than domestic, and perhaps not subject to whatever killswitch was thrown today within Syria.    
</p><p>
These five offshore survivors include the webservers that were <a href="https://www.eff.org/deeplinks/2012/05/fake-skype-encryption-tool-targeted-syrian-activists-promises-security-delivers">implicated in the delivery of malware targeting Syrian activists</a> in May of this year. 
</p></td><td>
<a href="http://www.renesys.com/blog/assets_c/2012/11/SY_outages_Nov12-795.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2012/11/SY_outages_Nov12-795.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2012/11/SY_outages_Nov12-thumb-300x257-795.png" width="300" height="257" alt="SY_outages_Nov12.png" class="mt-image-right" style="float: right; margin: 0 0 20px 20px;" /></a>
<a href="http://www.renesys.com/blog/assets_c/2012/11/ste.traces.outage-798.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2012/11/ste.traces.outage-798.shtml','popup','width=840,height=719,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2012/11/ste.traces.outage-thumb-300x256-798.png" width="300" height="256" alt="ste.traces.outage.png" class="mt-image-right" style="float: right; margin: 0 0 20px 20px;" /></a>
</td></tr>

<p><tr><td style="vertical-align:top"><p></p>

<p>It has been a crazy year for Syrian Internet transit arrangements, most recently with the loss of Deutsche Telekom as a transit provider earlier this month.   </p>

</p>
</td><td>
<a href="http://www.renesys.com/blog/assets_c/2012/11/November.2012.SY.transit-792.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2012/11/November.2012.SY.transit-792.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2012/11/November.2012.SY.transit-thumb-300x257-792.png" width="300" height="257" alt="November.2012.SY.transit.png" class="mt-image-right" style="float: right; margin: 0 0 20px 20px;" /></a>
</td></tr><tr><td style="vertical-align:top">
<p><em>Update (20:30 UTC):</em></p>

<p>Still no signs of life from the affected prefixes.   Looking back over the last week, you can see that the routing of the Syrian Internet has actually been pretty stable until today's wholesale shutdown. </p>

<p> There have been some brief up-and-down flickers affecting the reachability of a particular 12 networks, and there was one brief whole-country outage of less than ten minutes on 25 November.   By the time that one was confirmed, the outage was over.   It would be reaching to call that a "precursor event" or "practice run,"  but that's a possibility.</p>

<p>Also, some have asked about the submarine connectivity into Syria.  Here's a map showing the three principal routes.  There's also terrestrial connectivity into Turkey to the north, but those paths have not been reliable in recent months.  </p>
</td><td>
<a href="http://www.renesys.com/blog/assets_c/2012/11/SY_outages_1week_Nov2012-801.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2012/11/SY_outages_1week_Nov2012-801.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2012/11/SY_outages_1week_Nov2012-thumb-300x257-801.png" width="300" height="257" alt="SY_outages_1week_Nov2012.png" class="mt-image-right" style="float: right; margin: 0 0 20px 20px;" /></a>

<p><a href="http://www.renesys.com/blog/assets_c/2012/11/Syria_Submarine_cables2-804.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2012/11/Syria_Submarine_cables2-804.shtml','popup','width=1251,height=1250,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2012/11/Syria_Submarine_cables2-thumb-300x299-804.jpg" width="300" height="299" alt="Syria_Submarine_cables2.jpg" class="mt-image-right" style="float: right; margin: 0 0 20px 20px;" /></a><br />
</td></tr><br />
<tr><td><br />
<a id="latest"><br />
<em>Update (01:00 GMT, 30 Nov):</em></a><br />
<p>The last 5 networks belonging to Syria, a set of smaller netblocks previously advertised by Tata Communications, have been torn down and are no longer routed. These blocks survived today's Internet blackout in Syria, but 12 hours after the onset, they, too are off the air.   Traceroutes to these blocks now die on Tata's network in New Jersey, and websites hosted in these blocks are no longer responding.</p><br />
</td><td><br />
<a href="http://www.renesys.com/blog/assets_c/2012/11/last_5_Syrian_outages-807.shtml" onclick="window.open('http://www.renesys.com/blog/assets_c/2012/11/last_5_Syrian_outages-807.shtml','popup','width=700,height=600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.renesys.com/blog/assets_c/2012/11/last_5_Syrian_outages-thumb-300x257-807.png" width="300" height="257" alt="last_5_Syrian_outages.png" class="mt-image-right" style="float: right; margin: 0 0 20px 20px;" /></a><br />
</td></tr><br />
</table></p>]]>
    </content>
</entry>

</feed>
