<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </head> <body bgcolor="#ffffff" text="#000000"> Dear Colleagues, together with some other LIR's we've discovered there are several issues with allocations/assignments made within the 178.0.0.0/8 range. Seemingly there are some server/router administrators/companies out there which don't regular update their IANA Allocation list. We've observed that a lot of networks are unreachable if we use IPs out of the 178.0.0.0/8 range. The same observation also made other LIR's we know. After contacting these networks (from MD, RO, RU, DE, and other counties), we figured out that they all reported they had firewall/filter rules using a IANA allocation list, and their list reported 178/8 to be "iana-reserved" or "iana-unallocated". The network 178.0.0.0/8 were allocated on January 2009 to the RIPE NCC, hence these operators haven't updated their lists for more than 1 year. I guess the filter was set up once without taking into account that currently unallocated networks might get allocated later on. This problem concerns everyone at the moment, especially people with allocations from 178.0.0.0/8. I ask every one of you to check if you use an iana filter list or if possible, notify your clients, data centers and so on to check and if necessary update their lists. Are other members in this discussion list maybe observing the same problem as we did and our LIR colleagues? Cheers! -- Sven Wiese General Director I.C.S. "Trabia-Network" S.R.L. [t] +373 (22) 844-844 [e] <a href="mailto:s.wiese@trabia.net">s.wiese@trabia.net</a> [i] <a href="http://www.trabia.net">www.trabia.net</a> <div style="width: 500px; text-align: justify;"> Privileged/Confidential Information may be contained in this message. If you are not in the addresses indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such a case, you should destroy this message and kindly notify the sender by reply e-mail.</div> </body> </html>