I don't really get it... You want me to ping 95.130.9.210 ?
If so, ping & traceroute works great from both my exits
Le mercredi 18 octobre 2017 à 23:48 +, Paul Templeton a écrit :
> Has anyone come across a scenario where a carrier blocks IP traffic?
>
> atlas.cogentco.com is the point
On Thu, Oct 19, 2017 at 01:19:21AM +, Paul Templeton wrote:
Whoever runs that node will need to talk to their ISP support team to
get it unblocked.
Thanks Andy - the reason I asked because its not with the Service Provider it's
there upstream carrier - I have lodged a ticket with the
> Whoever runs that node will need to talk to their ISP support team to
get it unblocked.
Thanks Andy - the reason I asked because its not with the Service Provider it's
there upstream carrier - I have lodged a ticket with the carrier and waiting to
here back. The ISP doesn't know anything. I
On Wed, Oct 18, 2017 at 11:48:33PM +, Paul Templeton wrote:
Has anyone come across a scenario where a carrier blocks IP traffic?
atlas.cogentco.com is the point which drops any packet to 95.130.9.210
From where I sit it looks like .210 is null-routed. All of my ISPs drop
the packets as
