Working from ATT route server....

rviews@route-server.ip.att.net> ping 4.2.2.1
PING 4.2.2.1 (4.2.2.1): 56 data bytes
64 bytes from 4.2.2.1: icmp_seq=0 ttl=54 time=8.661 ms
64 bytes from 4.2.2.1: icmp_seq=1 ttl=54 time=9.291 ms
64 bytes from 4.2.2.1: icmp_seq=2 ttl=54 time=9.401 ms
^C
--- 4.2.2.1 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 8.661/9.118/9.401/0.326 ms

rviews@route-server.ip.att.net>
From: NANOG <nanog-bounces+scott.pennington=cinbell.com@nanog.org> on behalf of Mel Beckman <mel@beckman.org>
Sent: Sunday, January 12, 2025 7:24 PM
To: Jerry Cloe <jerry@jtcloe.net>
Cc: nanog@nanog.org <nanog@nanog.org>
Subject: Re: Level3 4.2.2.1 and 4.2.2.2 not responding to pings, DNS queries work
 
Still not pinging from Frontier, Lumen, AT&T, or Verizon networks


 -mel

On Jan 12, 2025, at 4:13 PM, Jerry Cloe <jerry@jtcloe.net> wrote:


O:\>ping 4.2.2.1
 
Pinging 4.2.2.1 with 32 bytes of data:
Reply from 4.2.2.1: bytes=32 time=36ms TTL=56
Reply from 4.2.2.1: bytes=32 time=44ms TTL=56
Reply from 4.2.2.1: bytes=32 time=36ms TTL=56
Reply from 4.2.2.1: bytes=32 time=38ms TTL=56
 
Ping statistics for 4.2.2.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 36ms, Maximum = 44ms, Average = 38ms
 
Same for 4.2.2.2


 

-----Original message-----
From: Mel Beckman <mel@beckman.org>
Sent: Sun 01-12-2025 06:07 pm
Subject: Level3 4.2.2.1 and 4.2.2.2 not responding to pings, DNS queries work
To: nanog@nanog.org;
I noticed that Level3 open DNS 4.2.2.1 and 4.2.2.2 stopped responding to ping today. They are responding to DNS queries however.

Does anyone know if this filtering is going to be permanent?

-mel beckman