Re: help with diagnosing traffic blackhole to / from select akamai ranges?

2020-01-09 Thread Niels Bakker
* wimcl...@gmail.com (William McLendon) [Thu 09 Jan 2020, 20:18 CET]: thank you all for the rapid feedback and suggestions! since many have asked for more detail, the specific prefix in question is 168.8.214.0/24. The previous owner is still announcing 168.8.0.0/14. If you're shooting holes

Re: help with diagnosing traffic blackhole to / from select akamai ranges?

2020-01-09 Thread William McLendon
thank you all for the rapid feedback and suggestions! since many have asked for more detail, the specific prefix in question is 168.8.214.0/24. it is currently being advertised; the customer just is not currently using it until we can resolve this reachability issue. As a note, our RADB irr d

Re: help with diagnosing traffic blackhole to / from select akamai ranges?

2020-01-09 Thread Warren Kumari
On Thu, Jan 9, 2020 at 1:56 PM William McLendon wrote: > > Good afternoon, > > we have a downstream customer originating a more specific /24 prefix, and > when they do so, traffic sourced from that /24 prefix to at least a subset of > akamai ranges (at minimum the 184.27.24.0/22 block at this ti

Re: help with diagnosing traffic blackhole to / from select akamai ranges?

2020-01-09 Thread Hugo Slabbert
It would likely be helpful if you indicate which /24 and which supernet you're talking about so people can perhaps comment if it's something around IRR, ROAs, what their views are of the block(s), etc. -- Hugo Slabbert | email, xmpp/jabber: h...@slabnet.com pgp key: B178313E | also on Sig

help with diagnosing traffic blackhole to / from select akamai ranges?

2020-01-09 Thread William McLendon
Good afternoon, we have a downstream customer originating a more specific /24 prefix, and when they do so, traffic sourced from that /24 prefix to at least a subset of akamai ranges (at minimum the 184.27.24.0/22 block at this time) are getting blackholed somewhere along the path either to or f