[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
192.250.24.0/22 (as 23034) not reachable from Verizon, tinet, global crossing, XO
- Subject: 192.250.24.0/22 (as 23034) not reachable from Verizon, tinet, global crossing, XO
- From: tony at wicks.co.nz (Tony Wicks)
- Date: Fri, 19 Sep 2014 09:26:27 +1200
- In-reply-to: <[email protected]>
- References: <5D7E8D6713A8AA4AB53AF403632BE8260137743FE5@CPEXM01.corp.dsg.local> <[email protected]> <[email protected]>
-----Original Message-----
From: NANOG [mailto:nanog-bounces at nanog.org] On Behalf Of sthaug at nethelp.no
Sent: Friday, 19 September 2014 9:09 a.m.
To: BMassel at descartes.com; job at instituut.net
Cc: nanog at nanog.org
Subject: Re: 192.250.24.0/22 (as 23034) not reachable from Verizon, tinet,
global crossing, XO
> > 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.
Reachable from New Zealand -
192.250.24.0/24 *[BGP/170] 02:42:04, MED 0, localpref 90
AS path: 4826 174 812 23034 I, validation-state:
unverified
> to 175.45.102.9 via ae1.526
64 bytes from 192.250.24.1: icmp_seq=0 ttl=242 time=193.274 ms
64 bytes from 192.250.24.1: icmp_seq=1 ttl=242 time=196.312 ms
64 bytes from 192.250.24.1: icmp_seq=2 ttl=242 time=197.578 ms
- Prev by Date:
192.250.24.0/22 (as 23034) not reachable from Verizon, tinet, global crossing, XO
- Next by Date:
192.250.24.0/22 (as 23034) not reachable from Verizon, tinet, global crossing, XO
- Previous by thread:
192.250.24.0/22 (as 23034) not reachable from Verizon, tinet, global crossing, XO
- Next by thread:
192.250.24.0/22 (as 23034) not reachable from Verizon, tinet, global crossing, XO
- Index(es):