[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: sthaug at nethelp.no (sthaug at nethelp.no)
- Date: Thu, 18 Sep 2014 23:08:55 +0200 (CEST)
- In-reply-to: <[email protected]>
- References: <5D7E8D6713A8AA4AB53AF403632BE8260137743FE5@CPEXM01.corp.dsg.local> <[email protected]>
> > 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 from here (AS 2116, Norway).
> Do you have a pingable IP address in the range which is problematic?
> That would help others who are willing to debug your issue enormously.
192.250.24.1 and 192.250.24.2 (for example) are pingable from 2116.
Steinar Haug, Nethelp consulting, sthaug at nethelp.no
- Follow-Ups:
- 192.250.24.0/22 (as 23034) not reachable from Verizon, tinet, global crossing, XO
- From: hslabbert at stargate.ca (Hugo Slabbert)
- 192.250.24.0/22 (as 23034) not reachable from Verizon, tinet, global crossing, XO
- From: tony at wicks.co.nz (Tony Wicks)
- 192.250.24.0/22 (as 23034) not reachable from Verizon, tinet, global crossing, XO
- From: gary at baribault.net (Gary Baribault)
- 192.250.24.0/22 (as 23034) not reachable from Verizon, tinet, global crossing, XO
- From: gary at baribault.net (Gary Baribault)
- 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):