Has ping / tracert been blocked on 5g network?

Heads up boys & girls!!

Its back o on the way. After the post from castrionfanatic I tested and my Nokia gateway was 27 days and some odd hours uptime and ICMP not passing. I decided to reboot the gateway and try again. Boom! It works. So, a reboot for you may also improve matters. I am in East Tennessee so locations may be different but it is much improved here. 

itinkeralot-MBP ~ % ping google.com

PING google.com (173.194.219.138): 56 data bytes

64 bytes from 173.194.219.138: icmp_seq=0 ttl=104 time=41.858 ms

64 bytes from 173.194.219.138: icmp_seq=1 ttl=104 time=47.267 ms

64 bytes from 173.194.219.138: icmp_seq=2 ttl=104 time=43.141 ms

64 bytes from 173.194.219.138: icmp_seq=3 ttl=104 time=53.151 ms

64 bytes from 173.194.219.138: icmp_seq=4 ttl=104 time=44.556 ms

64 bytes from 173.194.219.138: icmp_seq=5 ttl=104 time=49.542 ms

64 bytes from 173.194.219.138: icmp_seq=6 ttl=104 time=56.210 ms

64 bytes from 173.194.219.138: icmp_seq=7 ttl=104 time=41.839 ms

64 bytes from 173.194.219.138: icmp_seq=8 ttl=104 time=46.823 ms

64 bytes from 173.194.219.138: icmp_seq=9 ttl=104 time=45.199 ms

64 bytes from 173.194.219.138: icmp_seq=10 ttl=104 time=42.422 ms

64 bytes from 173.194.219.138: icmp_seq=11 ttl=104 time=46.108 ms

64 bytes from 173.194.219.138: icmp_seq=12 ttl=104 time=49.083 ms

64 bytes from 173.194.219.138: icmp_seq=13 ttl=104 time=41.708 ms

64 bytes from 173.194.219.138: icmp_seq=14 ttl=104 time=44.228 ms

64 bytes from 173.194.219.138: icmp_seq=15 ttl=104 time=45.096 ms

64 bytes from 173.194.219.138: icmp_seq=16 ttl=104 time=45.386 ms

64 bytes from 173.194.219.138: icmp_seq=17 ttl=104 time=46.104 ms

64 bytes from 173.194.219.138: icmp_seq=18 ttl=104 time=41.739 ms

64 bytes from 173.194.219.138: icmp_seq=19 ttl=104 time=42.638 ms

^C

--- google.com ping statistics ---

20 packets transmitted, 20 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 41.708/45.705/56.210/3.797 ms