What's new

Odd Loss/Choke

A Stable Carbocation

Staff member
Moderator
Well last time it was on my end, perhaps this was nfo's end? I don't know. It still is not acceptable, since it seems to be a commonly repeating occurrence.
 

mclovin

Well-Known Member
i always see a lag spike every few rounds on all servers. i think this is an issue on your end unless others complain about this consistently. i played for a good 2 hours today and saw nothing that made me rage rage and want to post on forums about.

but that is just me
 

IcEWoLF

Staff member
Founder
I went ahead and sent it to NFo, but the issue appears to be on Verizon's end again:

Code:
1   0.5 ms   0.4 ms   1.1 ms  border1.teng3-2.nuclearfallout-62.sje003.pnap.net [66.151.129.177]
2   4.0 ms   2.1 ms   1.9 ms  core1.t6-1-bbnet1.sje011.pnap.net [66.151.144.21]
3   2.0 ms   1.7 ms   1.9 ms  te0-0-2-3.208.nr11.b023785-1.sjc01.atlas.cogentco.com [38.104.134.69]
4   1.8 ms   1.7 ms   1.6 ms  te0-0-1-2.agr14.sjc01.atlas.cogentco.com [154.24.15.181]
5   1.6 ms   1.6 ms   1.7 ms  te0-4-0-0.ccr22.sjc01.atlas.cogentco.com [154.54.6.89]
6   2.5 ms   2.3 ms   2.3 ms  be2047.ccr21.sjc03.atlas.cogentco.com [154.54.5.114]
7   2.8 ms   2.6 ms   2.7 ms  verizon.sjc03.atlas.cogentco.com [154.54.12.170]
8   *       14.1 ms  15.9 ms  B200.LSANCA-LCR-21.verizon-gni.net [130.81.209.255]
9   *        *        *       Request timed out.
10  22.5 ms  22.1 ms  22.4 ms  pool-173-51-91-201.lsanca.fios.verizon.net [173.51.91.201]
 

A Stable Carbocation

Staff member
Moderator
Honestly, for the last 10+ years it's been great. We were one of the first areas to get FIOS and NEVER had the internet die, though a 2 routers did. Never had a single connection issue until a couple weeks ago.
 

IcEWoLF

Staff member
Founder
The problem is, Verizon is using one of the worst net providers ever...Cogent is probably the cheapest BW provider out there and they always have issues.
Its something VZ and CG have to fix on their end and optimize their routes. Keep submitting the reports as they happen, the only thing I can do is to submit it to NFo which gets forwarded to Internap and its up to them to get Verizon to switch the routes, but the problem is, its not a permanent fix since they keep changing things up once a node gets overloaded they are just slow at fixing the problem.
 

IcEWoLF

Staff member
Founder
Also doing a simple google search you can see bunch of people that use Netflix are having issues with Verizon and their packet loss.
This is the most recent interview: Netflix packets being dropped every day because Verizon wants more money | Ars Technica
It also sounds like Verizon has something to do with it...

Cogent Verizon peering congestion | NANOG | users
Verizon and Cogent packet loss | nsp | outages
Packet loss issue between Verizon & Cogent - Project 1999
People Complaining About Lag... READ - League of Legends Community
 

IcEWoLF

Staff member
Founder
Well in a way I'm glad it's not just me, that way they hear more complaints and hoepfully act sooner.
I think the main issue here is Verizon restricting bandwidth for Netflix and now fucking up routing for everyone that goes through their routes.
I can bet you anything that if they fixed the dispute between them and netflix we would not be having this issue.

This is something that has been going on for a while.
Corporates sticking it to the public, hopefully someone will come down hard on these fuckers someday.
 

A Stable Carbocation

Staff member
Moderator
New problem everyone!

Trace taken from computer.

Code:
C:\Users\Daniel>tracert 66.151.138.115

Tracing route to c-66-151-138-115.managed-vds.internap-sj.nfoservers.com [66.151
.138.115]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.0.0.1
  2     8 ms     8 ms     8 ms  98.255.224.1
  3     8 ms     7 ms     7 ms  te-7-2-sr01.davis.ca.ccal.comcast.net [68.87.201
.29]
  4     9 ms     9 ms     9 ms  te-0-3-0-5-ar03.sacramento.ca.sacra.comcast.net
[68.85.120.221]
  5    14 ms    15 ms    15 ms  he-3-6-0-0-10-cr01.sanjose.ca.ibone.comcast.net
[68.86.90.125]
  6    18 ms    19 ms    55 ms  pos-0-5-0-0-pe01.11greatoaks.ca.ibone.comcast.net [68.86.87.162]
  7    34 ms    34 ms    34 ms  xe-9-3-0.sjc10.ip4.tinet.net [213.200.80.165]
  8    22 ms    21 ms    21 ms  xe-4-3-0.sjc10.ip4.gtt.net [89.149.187.45]
  9    15 ms    15 ms    15 ms  internap-gw.ip4.gtt.net [77.67.70.26]
10    15 ms    32 ms    15 ms  border1.t4-1-bbnet2.sje003.pnap.net [66.151.144.90]
11    16 ms    14 ms    15 ms  c-66-151-138-115.managed-vds.internap-sj.nfoserv
ers.com [66.151.138.115]

Trace complete.
Trace from nfo tool in server control, I don't know if this is useful- so I will include it:

Code:
C:\>tr 98.255.224.143

NFO win32 trace tool v2.04, copyright (c)2005 Nuclearfallout Enterprises, Inc.

Tracing route to c-98-255-224-143.hsd1.ca.comcast.net [98.255.224.143]
with up to 30 hops:

1   0.5 ms   0.4 ms   0.4 ms  border1.teng3-2.nuclearfallout-62.sje003.pnap.net [66.151.129.177]
2   2.4 ms   1.1 ms   1.2 ms  core3.pc1-bbnet1.sje.pnap.net [66.151.144.3]
3   1.0 ms   1.0 ms   1.0 ms  xe-0-6-0-8.r01.snjsca04.us.bb.gin.ntt.net [128.241.219.129]
4   1.2 ms   1.1 ms   1.0 ms  ae-3.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.19]
5   3.4 ms   3.3 ms   3.3 ms  ae-0.comcast.snjsca04.us.bb.gin.ntt.net [129.250.66.34]
6   6.4 ms   6.2 ms   3.8 ms  he-3-15-0-0-cr01.sanjose.ca.ibone.comcast.net [68.86.85.241]
7   6.0 ms   6.0 ms   6.0 ms  68.86.90.18 [68.86.90.18]
8   7.8 ms   7.6 ms   7.6 ms  te-9-4-sr01.davis.ca.ccal.comcast.net [68.85.120.222]
9   7.4 ms   7.4 ms   7.3 ms  te-6-0-acr01.davis.ca.ccal.comcast.net [68.87.201.18]
10   *        *        *       Request timed out.
11  15.6 ms   *       15.1 ms  c-98-255-224-143.hsd1.ca.comcast.net [98.255.224.143]

Trace complete.
The Comcast guy came out today and said that the box was being overloaded, so he added a splitter. Unfortunately, that did not fix the main issue I am having. A stutter, that seems caused by connection issues, since I can run games fine, it's the online ones that don't work very well.
 
Top