On 9/18/2014 4:42 PM, Brock Massel wrote:
Hi folks,
I'm hoping someone can shed some light on the situation.
The 192.250.24 addresses have been reachable for several months in the current
configuration with no reported issues. Since the 16th we have been hearing
reports that destinations in
Hi folks,
I'm hoping someone can shed some light on the situation.
The 192.250.24 addresses have been reachable for several months in the current
configuration with no reported issues. Since the 16th we have been hearing
reports that destinations in that block are unavailable for some.
Several
On Thu, Sep 18, 2014 at 08:42:23PM +, Brock Massel wrote:
The 192.250.24 addresses have been reachable for several months in the
current configuration with no reported issues. Since the 16th we have
been hearing reports that destinations in that block are unavailable
for some.
Several
The 192.250.24 addresses have been reachable for several months in the
current configuration with no reported issues. Since the 16th we have
been hearing reports that destinations in that block are unavailable
for some.
Several looking glass' report network not in table.
Visible
On Thu 2014-Sep-18 23:08:55 +0200, sth...@nethelp.no sth...@nethelp.no wrote:
The 192.250.24 addresses have been reachable for several months in the
current configuration with no reported issues. Since the 16th we have
been hearing reports that destinations in that block are unavailable
for
-Original Message-
From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of sth...@nethelp.no
Sent: Friday, 19 September 2014 9:09 a.m.
To: bmas...@descartes.com; j...@instituut.net
Cc: nanog@nanog.org
Subject: Re: 192.250.24.0/22 (as 23034) not reachable from Verizon, tinet,
global
Pingable from Montreal area as well
Gary Baribault
Courriel: g...@baribault.net
GPG Key: 0x685430d1
Fingerprint: 9E4D 1B7C CB9F 9239 11D9 71C3 6C35 C6B7 6854 30D1
On 09/18/2014 05:08 PM, sth...@nethelp.no wrote:
The 192.250.24 addresses have been reachable for several months in the
current
Hum, Traceroute is not as nice
traceroute to 192.250.24.1 (192.250.24.1), 30 hops max, 60 byte packets
1 GW (192.168.0.2) 0.459 ms 0.435 ms 0.422 ms
2 * * *
3 10.170.182.81 (10.170.182.81) 18.417 ms 18.711 ms 18.702 ms
4 216.113.124.126 (216.113.124.126) 16.611 ms 17.774 ms
: Thursday, September 18, 2014 5:46 PM
To: Brock Massel
Cc: nanog@nanog.org
Subject: Re: 192.250.24.0/22 (as 23034) not reachable from Verizon, tinet,
global crossing, XO
Hi,
looks like you mainly use one transit provider (AS812) or your other transit
providers correctly filter that prefix.
According
Hi,
looks like you mainly use one transit provider (AS812) or your other
transit providers correctly filter that prefix.
According to
https://stat.ripe.net/data/prefix-routing-consistency/data.json?preferred_version=0.7resource=192.250.24.0%2F22
there is no route object for the 192.250.24.0/22.
, September 18, 2014 5:46 PM
To: Brock Massel
Cc: nanog@nanog.org
Subject: Re: 192.250.24.0/22 (as 23034) not reachable from Verizon, tinet,
global crossing, XO
Hi,
looks like you mainly use one transit provider (AS812) or your other transit
providers correctly filter that prefix.
According
11 matches
Mail list logo
