[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: job at instituut.net (Job Snijders)
- Date: Thu, 18 Sep 2014 22:49:16 +0200
- In-reply-to: <5D7E8D6713A8AA4AB53AF403632BE8260137743FE5@CPEXM01.corp.dsg.local>
- References: <5D7E8D6713A8AA4AB53AF403632BE8260137743FE5@CPEXM01.corp.dsg.local>
On Thu, Sep 18, 2014 at 08:42:23PM +0000, 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 looking glass' report network not in table.
Which ones?
> Can someone lend a hand? What is the best way to improve this
> situation? How do we find where the problem is?
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.
Kind regards,
Job
- 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):