Name of ISP: Verizon FiOS
Character name: Yuengling Light
Country of Residence: Fairfax County, Northern Virginia, United States

Same issue. Constant 5 second freezes.

I've isolated the issue down to one of these hops:

3 28 ms 14 ms 10 ms G0-9-2-6.WASHDC-LCR-21.verizon-gni.net [130.81.97.106]
4 9 ms 8 ms 8 ms ae1-0.RES-BB-RTR1.verizon-gni.net [130.81.209.206]
5 11 ms 12 ms 11 ms 0.ae5.XL1.IAD8.ALTER.NET [152.63.8.121]
6 9 ms 8 ms 8 ms 0.xe-10-0-1.GW9.IAD8.ALTER.NET [152.63.33.161]
7 * 14 ms 14 ms tinet-gw.customer.alter.net [152.179.50.30]
8 41 ms 39 ms 37 ms xe-1-0-0.mtl10.ip4.tinet.net [89.149.185.41]
9 41 ms 37 ms 40 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
10 47 ms 41 ms * 192.34.76.2
11 47 ms 41 ms 42 ms 199.91.189.234
12 37 ms 39 ms 38 ms 199.91.189.74

Reply from 216.221.156.110: bytes=64 time=39ms TTL=250
Reply from 216.221.156.110: bytes=64 time=37ms TTL=250
Request timed out.
Request timed out.
Reply from 216.221.156.110: bytes=64 time=40ms TTL=250
Reply from 216.221.156.110: bytes=64 time=34ms TTL=250
Reply from 216.221.156.110: bytes=64 time=33ms TTL=250
Reply from 216.221.156.110: bytes=64 time=38ms TTL=250
Reply from 216.221.156.110: bytes=64 time=32ms TTL=250
Request timed out.
Reply from 216.221.156.110: bytes=64 time=38ms TTL=250
Request timed out.
Reply from 216.221.156.110: bytes=64 time=38ms TTL=250
Reply from 216.221.156.110: bytes=64 time=38ms TTL=250
Reply from 216.221.156.110: bytes=64 time=39ms TTL=250
Reply from 216.221.156.110: bytes=64 time=35ms TTL=250
Request timed out.
Reply from 216.221.156.110: bytes=64 time=38ms TTL=250
Reply from 216.221.156.110: bytes=64 time=42ms TTL=250


I tried getting Verizon to look into it, but they are blaming the "game provider". (0)