Has anyone confirmed if this affects all ICMP, or just specific ICMP types (e.g. echoreq/echorep)?
If they're blocking all ICMP, someone at Cox needs to be fired immediately.
My Cox Rep confirmed that it indeed being blocked at 'several' of their peering points. I have not got a RFO as of yet, but they are initially blaming it on a "Peering Partner". My investigation concluded that it was COGENT (as174) that was the peering partner, yet I do not know who exactly was at fault, though it didn't sound like it was Cox from my rep. They had mentioned that their own monitoring systems were dark due to the outage. They had mentioned it was ALL icmp being affected. This affected traffic regardless of destination or source ip address. Ryan Werber Sr Network Engineer Epik Networks Irvine, California