- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tracing route to WIN-TGPS0LQCFCC [94.23.145.197]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 6 ms 4 ms 4 ms L100.TAMPFL-VFTTP-144.verizon-gni.net [96.254.17
9.1]
3 7 ms 12 ms 12 ms G0-9-3-7.TAMPFL-LCR-22.verizon-gni.net [130.81.1
40.80]
4 * * * Request timed out.
5 13 ms 14 ms 14 ms 0.ae12.GW1.MIA19.ALTER.NET [140.222.225.79]
6 310 ms 307 ms 312 ms teliasonera-gw.customer.alter.net [152.179.236.2
2]
7 338 ms 339 ms 337 ms ash-bb3-link.telia.net [62.115.141.117]
8 * 339 ms 339 ms nyk-bb1-link.telia.net [62.115.136.202]
9 342 ms 342 ms * nyk-b2-link.telia.net [62.115.112.107]
10 338 ms 342 ms 344 ms nwk-1-a9.nj.us [178.32.135.212]
11 413 ms 409 ms 414 ms ldn-1-a9.uk.eu [178.32.135.79]
12 414 ms 414 ms 412 ms rbx-g1-a9.fr.eu [91.121.128.86]
13 412 ms 417 ms 412 ms rbx1-3a-a9.fr.eu [37.187.231.100]
14 415 ms 414 ms 414 ms WIN-TGPS0LQCFCC [94.23.145.197]
15 413 ms 416 ms 414 ms WIN-TGPS0LQCFCC [94.23.145.197]
Trace complete.
this is unacceptable
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Problem is fixed! (At least on my end). Contacted support and they escalated the issue and I'm back down to normal pings. It's not as good as it used to be (135-140ms to this one particular server, up from 105-110ms), but infinitely better than 350-450ms. I suppose the 25-30ms increase is due to an extra hop going from Tampa to Miami, then to atlanta, instead of from Tampa, to Atlanta
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It was fixed on my end as well after multiple calls and complaints. I was out of town for a while, but I am back to normal levels for that certain hop.
I want to give a shout-out to everyone on here, and especially Verizon's Tech Support. It took me escalating the issue and asking to talk to a supervisor a couple times, but I finally got in touch with someone who knew what they were talking about, and could understand the problem.
Thanks to everyone else who took the time to post on the forums, as I was able to use "Well there are other Verizon users on the forums having the same problem" line and they finally understood that it wasn't a problem with my router or the gamer server.
Happy Gaming!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same issue has happened yet again.
Tracing route to WIN-TGPS0LQCFCC [94.23.145.197]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms FIOS_Quantum_Gateway.fios-router.home [192.168.1
.1]
2 3 ms 4 ms 4 ms L100.TAMPFL-VFTTP-144.verizon-gni.net [96.254.17
9.1]
3 7 ms 6 ms 7 ms G101-0-0-5.TAMPFL-LCR-22.verizon-gni.net [100.41
.221.62]
4 * * * Request timed out.
5 13 ms 14 ms 14 ms 0.ae12.GW1.MIA19.ALTER.NET [140.222.225.79]
6 302 ms 304 ms 302 ms teliasonera-gw.customer.alter.net [152.179.236.2
2]
7 310 ms 321 ms 327 ms ash-bb3-link.telia.net [62.115.141.117]
8 322 ms 319 ms 329 ms nyk-bb1-link.telia.net [62.115.136.202]
9 302 ms 304 ms 322 ms nyk-b2-link.telia.net [62.115.112.107]
10 308 ms 296 ms 304 ms nwk-1-a9.nj.us [178.32.135.212]
11 380 ms 369 ms 389 ms ldn-1-a9.uk.eu [178.32.135.79]
12 385 ms 372 ms 379 ms rbx-g1-a9.fr.eu [91.121.128.86]
13 400 ms 384 ms 379 ms rbx1-3a-a9.fr.eu [37.187.231.64]
14 402 ms 379 ms 371 ms WIN-TGPS0LQCFCC [94.23.145.197]
15 394 ms 374 ms 374 ms WIN-TGPS0LQCFCC [94.23.145.197]
Trace complete.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Indeed it has begun again. I was not on gaming yesterday nor this morning, so i had not noticed. I hope Verizon will fix it agian this time or I may have to make the transition to another ISP.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yea, here we go again...
NOT "solved"
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
C:\Users\XXXXX>ping 94.23.145.197
Pinging 94.23.145.197 with 32 bytes of data:
Reply from 94.23.145.197: bytes=32 time=377ms TTL=116
Reply from 94.23.145.197: bytes=32 time=365ms TTL=116
Reply from 94.23.145.197: bytes=32 time=366ms TTL=116
Reply from 94.23.145.197: bytes=32 time=362ms TTL=116
Ping statistics for 94.23.145.197:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 362ms, Maximum = 377ms, Average = 367ms
Tracing route to WIN-TGPS0LQCFCC [94.23.145.197]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms FIOS_Quantum_Gateway.fios-router.home [192.168.1
.1]
2 4 ms 4 ms 4 ms L100.TAMPFL-VFTTP-144.verizon-gni.net [96.254.17
9.1]
3 6 ms 7 ms 9 ms G101-0-0-5.TAMPFL-LCR-22.verizon-gni.net [100.41
.221.62]
4 * * * Request timed out.
5 11 ms 12 ms 12 ms 0.ae12.GW1.MIA19.ALTER.NET [140.222.225.79]
6 197 ms 194 ms 191 ms teliasonera-gw.customer.alter.net [152.179.236.2
2]
7 218 ms 214 ms 216 ms ash-bb3-link.telia.net [62.115.141.117]
8 230 ms 231 ms 234 ms nyk-bb1-link.telia.net [62.115.138.24]
9 221 ms 221 ms 226 ms nyk-b2-link.telia.net [213.155.130.28]
10 221 ms 221 ms 219 ms nwk-1-a9.nj.us [178.32.135.212]
11 286 ms 289 ms 294 ms ldn-1-a9.uk.eu [178.32.135.79]
12 303 ms 296 ms 299 ms rbx-g1-a9.fr.eu [91.121.128.86]
13 305 ms 314 ms 314 ms rbx1-3a-a9.fr.eu [37.187.231.64]
14 311 ms 316 ms 311 ms WIN-TGPS0LQCFCC [94.23.145.197]
15 303 ms 304 ms 311 ms WIN-TGPS0LQCFCC [94.23.145.197]
Fix it or we switch to bright house
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
YOU ARE POSTING IN A PEER TO PEER FORUM.
You will need to contact Verizon directly if you want any chance of getting them to look at this problem.
ps: Curious as why you guys use a ip number address rather than a name?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
because this is a server rented in france, not a website. i have contacted verizon multiple times over this issue and they are of no help. {edited for privacy}
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Verizon (and most or ISPs) won't guarantee performance past their network.
And they can't always control which gateway traffic goes out (depends on where they get routing info).
Are you certain poor performance is within Verizon network?