[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

Subject: help with diagnosing traffic blackhole to / from select akamai ranges?
From: niels=nanog at bakker.net (Niels Bakker)
Date: Thu, 9 Jan 2020 21:15:57 +0100
In-reply-to: <[email protected]>
References: <[email protected]> <CAHw9_i+wkLkJfOSY6feghT5-ViOtZebHsSdbUJvktMEaSOwZOw@mail.gmail.com> <[email protected]>

* wimclend at 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 in netblocks like this you can expect routing issues.


	-- Niels.

References:
- help with diagnosing traffic blackhole to / from select akamai ranges?
  - From: wimclend at gmail.com (William McLendon)
- help with diagnosing traffic blackhole to / from select akamai ranges?
  - From: warren at kumari.net (Warren Kumari)
- help with diagnosing traffic blackhole to / from select akamai ranges?
  - From: wimclend at gmail.com (William McLendon)

Prev by Date: "Using Cloud Resources to Dramatically Improve Internet Routing"
Next by Date: "Using Cloud Resources to Dramatically Improve Internet Routing"
Previous by thread: help with diagnosing traffic blackhole to / from select akamai ranges?
Next by thread: Career @ Micron21 - Working in Australia / Melbourne - Data Centre Experienced Network Engineer
Index(es):
- Date
- Thread