On Tue, Jan 2, 2018 at 9:51 PM, James Milko wrote:
> The output I dumped was from route-views.routeviews.org. On affected
> prefes you get 7843->6453->nothing unaffected prefixes get
> 7843->6453->15169. Unaffected prefixes don't have more specifics from
> 10512. My sample size is only 8 thoug
The output I dumped was from route-views.routeviews.org. On affected
prefes you get 7843->6453->nothing unaffected prefixes get
7843->6453->15169. Unaffected prefixes don't have more specifics from
10512. My sample size is only 8 though with a mix of affected and
unaffected users.
JM
On Tue, J
it looks like 203040 is a pure transit as (no originated prefixes) and 1103
- surfnet could squish what is your view anyway.
On Tue, Jan 2, 2018 at 9:29 PM, Christopher Morrow
wrote:
>
>
> On Tue, Jan 2, 2018 at 8:50 PM, James Milko wrote:
>
>> Not sure if anyone from Spectrum is looking here a
On Tue, Jan 2, 2018 at 8:50 PM, James Milko wrote:
> Not sure if anyone from Spectrum is looking here at this hour, but someone
> is hijacking a few of your prefixes. It's causing problems in my area (NC)
> with reaching Google services. I'm sure there are other impacts, but
> that's what peopl
Not sure if anyone from Spectrum is looking here at this hour, but someone
is hijacking a few of your prefixes. It's causing problems in my area (NC)
with reaching Google services. I'm sure there are other impacts, but
that's what people are noticing.
Sorry if this hits the list twice, I sent it
5 matches
Mail list logo
