Filtering After Recent Chinese "BGP Hijack" Does not Affect RIPE Region

Robert Kisteleki — Apr 09, 2010 10:25 AM
Filed under:
Related to a thread on the NANOG mailing list about "BGP hijack from 23724 -> 4134 China?", we checked if any of those prefixes originated in the RIPE NCC service region.

Yesterday a new thread was started on the NANOG mailing list with the title "BGP hijack from 23724 -> 4134 China?" -- see .

We did not (yet?) look into all the gory details of exactly what happened and why, but we did notice that several prefix lists have been generated by different people, listing the IPv4 prefixes that could be blocked. I ran a quick scan through one of the recent ones (available at ), to see if it contains any prefixes related to the RIPE region.

It seems that none   of these prefixes belong to the RIPE NCC service region, as far as we can tell, therefore there's no apparent "collateral damage" to our members.



Add comment

You can add a comment by filling out the form below. Only plain text is possible. Web and email addresses will be transformed into clickable links. Comments are moderated so they won't appear immediately.

Related Items
Visualising Bandwidth Capacity and Network Activity in RIPEstat Using M-Lab Data

As a result of the cooperation between the RIPE NCC and Measurement Lab (M-Lab), you can now ...

IPv6 Darknet Experiment

Similar to an experiment done for IPv4 address space, Merit is now performing a darknet experiment ...

Visualizing the Egyptian Disconnection

In the routing graphs produced by the RIPE REX tool, we can get a different visualization of ...

The Shape of a BGP Update

What happens to BGP traffic when an announcement or withdrawal of an address prefix propagates ...

Traffic in Network and

This study, done by Geoff Huston and George Michaelson from the APNIC is looking at the level of ...