Does anyone else notice any issues?

 

[[email protected] mhammett]# tcptraceroute 63.175.151.3 5060

Selected device eth0, address 205.218.65.34, port 51739 for outgoing packets

Tracing the path to 63.175.151.3 on TCP port 5060, 30 hops max

 1  205.138.198.193  2.686 ms  0.404 ms  1.042 ms

 2  ge5-1.br03.chc01.pccwbtn.net (63.218.5.97)  0.444 ms  0.504 ms  0.411 ms

 3  * * *

 4  ge0-2-0-1000M.ar1.CHI2.gblx.net (67.17.107.193)  0.885 ms  0.531 ms  0.464 ms

 5  sprint-1.ar1.CHI2.gblx.net (64.212.107.82)  26.533 ms  9.346 ms  54.376 ms

 6  sl-bb22-chi-5-0.sprintlink.net (144.232.20.90)  112.045 ms  209.869 ms  202.905 ms

 7  sl-bb20-roa-8-0-0.sprintlink.net (144.232.18.37)  15.198 ms  13.906 ms  32.054 ms

 8  sl-gw20-roa-10-0.sprintlink.net (144.232.17.190)  104.213 ms  36.510 ms  34.817 ms

 9  sl-essex-6-0.sprintlink.net (144.223.151.22)  53.096 ms  75.561 ms  51.180 ms

10  * * *

11  voip.essex1.com (63.175.151.3) [closed]  35.588 ms  69.591 ms *

 

This is normally a < 5 ms traceroute.