Hijack event today by Indosat

Posted by Andree Toonk - April 3, 2014 - Hijack, News and Updates - 1 Comment

Today we observed a large-scale ‘hijack’ event that affected many of the prefixes on the Internet. This blog post is to provide you with some additional information.

What happened?
Indosat, AS4761, one of Indonesia’s largest telecommunication networks normally originates about 300 prefixes. Starting at 18:26 UTC (April 2, 2014) AS4761 began to originate 417,038 new prefixes normally announced by other Autonomous Systems such as yours. The ‘mis-origination’ event by Indosat lasted for several hours affecting different prefixes at different times until approximately 21:15 UTC.

What caused this?
Given the large scale of this event we presume this is not malicious or intentional but rather the result of an operational issue. Other sources report this was the result of a maintenance window gone bad. Interestingly we documented a similar event involving Indosat in 2011, more details regarding that incident can be found here: http://www.bgpmon.net/hijack-by-as4761-indosat-a-quick-report/

Impact
The impact of this event was different per network, many of the hijacked routes were seen by several providers in Thailand. This means that it’s likely that communication between these providers in Thailand (as well as Indonesia) and your prefix may have been affected.
One of the heuristics we look at to determine the global impact of an event like this is the number of probes that detected the event. In this case, out of the 400k affected prefixes, 8,182 were detected by more than 10 different probes, which means that the scope and impact of this event was larger for these prefixes.
The screenshot below is an example of a Syrian prefix that was hijacked by Indosat where the ‘hijacked’ route was seen from Australia to the US and Canada.

Full alert detail

Full alert detail

What was the impact for my network?
By clicking on the alert details link in the alert email or portal you will see the number of probes that detected the hijacked route update. It also shows you where in the world these updates were seen so you’ll have an idea of the geographical scope of the event.
Users with a premium account also have access to all the individual BGP updates as well as the full AS path. This will tell you in detail what networks selected this bad route and the exact timestamps. Some of you also received a phone call to inform you of the events immediately after detection.

BGP probe and peering
A BGP probe in this case means one of our peering partners. You too can become a peering partner and get access to our PeerMon service, for more details see: https://portal.bgpmon.net/peermon.php

Questions and more information
I hope this provides you with some useful additional information regarding this event. Feel free to contact us should you have any follow up questions or would like to have more information for the purpose of further forensics.

One comment

  • Gabriel says:

    We receive a few alerts and sent emails to the who is contact of AS4761.
    BGP mon is a great tool!

    Thanks for keeping us posted!

    Regards,

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>