Has anyone else in the Atlanta, GA area seeing similar behavior where the pings ramp up then cease to respond? It's been ongoing for the past ~2 hours for me: Reply from 78.46.104.117: bytes=32 time=132ms TTL=43 Reply from 78.46.104.117: bytes=32 time=146ms TTL=43 Reply from 78.46.104.117: bytes=32 time=137ms TTL=43 Reply from 78.46.104.117: bytes=32 time=132ms TTL=43 Reply from 78.46.104.117: bytes=32 time=137ms TTL=43 Reply from 78.46.104.117: bytes=32 time=220ms TTL=43 Reply from 78.46.104.117: bytes=32 time=233ms TTL=43 Reply from 78.46.104.117: bytes=32 time=247ms TTL=43 Reply from 78.46.104.117: bytes=32 time=264ms TTL=43 Reply from 78.46.104.117: bytes=32 time=360ms TTL=43 Reply from 78.46.104.117: bytes=32 time=363ms TTL=43 Reply from 78.46.104.117: bytes=32 time=427ms TTL=43 Reply from 78.46.104.117: bytes=32 time=598ms TTL=43 Request timed out. Request timed out. Reply from 4.2.2.4: bytes=32 time=11ms TTL=54 Reply from 4.2.2.4: bytes=32 time=11ms TTL=54 Reply from 4.2.2.4: bytes=32 time=11ms TTL=54 Reply from 4.2.2.4: bytes=32 time=11ms TTL=54 Reply from 4.2.2.4: bytes=32 time=69ms TTL=54 Reply from 4.2.2.4: bytes=32 time=11ms TTL=54 Reply from 4.2.2.4: bytes=32 time=134ms TTL=54 Reply from 4.2.2.4: bytes=32 time=110ms TTL=54 Reply from 4.2.2.4: bytes=32 time=111ms TTL=54 Reply from 4.2.2.4: bytes=32 time=133ms TTL=54 Reply from 4.2.2.4: bytes=32 time=285ms TTL=54 Reply from 4.2.2.4: bytes=32 time=226ms TTL=54 Reply from 4.2.2.4: bytes=32 time=278ms TTL=54 Reply from 4.2.2.4: bytes=32 time=454ms TTL=54 Request timed out. Request timed out. -- W. Charles Goorsky Charles.Goorsky@gmail.com