Jump to content

Recommended Posts

Posted

Thank you both Sir's

 

Anyone still encountering issues with lag please let us know and post the information the Lt. Col. requested as well. For those not familiar with running a trace route it is fairly simple and you don't need admin access to your PC.

 

Windows: Open command prompt [Win+R "cmd" hit enter]

 

type "tracert 208.167.243.207" and hit enter.

 

Post results here.

 

Mac: Open Terminal [hit search icon at top taskbar; type terminal]

 

type "traceroute 208.167.243.207"

 

Post results here.

Posted (edited)

I got on tonight at 8pm PST and the server was really laggy and rubber banding, and everyone was complaining about the rubber banding. I wounded a few teammates unintentionally due to the rubberbanding. Server became a ghost town after 15mins.

 

A single traceroute didn't give the full picture so I took a PingPlotter trace over 3 mins and isolated it down to the hop that was dropping packets and ping was spiking. A major contributor is the first hop before the server's IP (vl105-as1.pnj1.choopa.net 108.61.79.86).

 

Hope this info helps and this gets resolved quickly.

 

Tracing route to 208.167.243.207.choopa.net [208.167.243.207]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     3 ms     5 ms     9 ms  static-50-53-152-1.bvtn.or.frontiernet.net [50.53.152.1]
  3     3 ms     4 ms     4 ms  50-39-211-13.bvtn.or.frontiernet.net [50.39.211.13]
  4    40 ms    44 ms    46 ms  ae2---0.cor02.bvtn.or.frontiernet.net [74.40.1.181]
  5    47 ms    44 ms    41 ms  ae3---0.cor01.plal.ca.frontiernet.net [74.40.1.225]
  6    20 ms    19 ms    19 ms  ae0---0.cbr01.plal.ca.frontiernet.net [74.40.3.150]
  7    20 ms    21 ms    19 ms  xe-0.paix.plalca01.us.bb.gin.ntt.net [198.32.176.14]
  8   121 ms   119 ms   121 ms  ae-15.r01.snjsca04.us.bb.gin.ntt.net [129.250.5.33]
  9    45 ms    44 ms    45 ms  ae-1.r22.snjsca04.us.bb.gin.ntt.net [129.250.3.26]
 10    64 ms    66 ms    67 ms  ae-8.r21.chcgil09.us.bb.gin.ntt.net [129.250.5.16]
 11    68 ms   157 ms    75 ms  ae-4.r20.chcgil09.us.bb.gin.ntt.net [129.250.2.162]
 12    86 ms    87 ms    87 ms  ae-0.r25.nycmny01.us.bb.gin.ntt.net [129.250.2.167]
 13   114 ms   112 ms   114 ms  ae-2.r07.nycmny01.us.bb.gin.ntt.net [129.250.3.98]
 14   115 ms   114 ms   112 ms  ae-0.choopa.nycmny01.us.bb.gin.ntt.net [128.241.2.202]
 15   113 ms   114 ms   114 ms  vl39-br1.pnj1.choopa.net [66.55.144.149]
 16   113 ms   115 ms   114 ms  vl105-as1.pnj1.choopa.net [108.61.79.86]
 17   110 ms   112 ms   114 ms  208.167.243.207.choopa.net [208.167.243.207]

Trace complete.

 

2016_11_03_PingPlotter_1stMarineRaiders_lag.PNG

Edited by Blue Saber BAR
remove photobucket link
Posted

Marsden asked for a fat packet ping to the hop in question. Here is my ping result with a 1400 MTU size:

 

C:\>ping -t -f -l 1400 108.61.79.86

Pinging 108.61.79.86 with 1400 bytes of data:
Reply from 108.61.79.86: bytes=1400 time=125ms TTL=48
Reply from 108.61.79.86: bytes=1400 time=119ms TTL=48
Reply from 108.61.79.86: bytes=1400 time=359ms TTL=48
Reply from 108.61.79.86: bytes=1400 time=128ms TTL=48
Reply from 108.61.79.86: bytes=1400 time=118ms TTL=48
Reply from 108.61.79.86: bytes=1400 time=175ms TTL=48
Reply from 108.61.79.86: bytes=1400 time=514ms TTL=48
Reply from 108.61.79.86: bytes=1400 time=128ms TTL=48
Reply from 108.61.79.86: bytes=1400 time=125ms TTL=48
Reply from 108.61.79.86: bytes=1400 time=357ms TTL=48
Reply from 108.61.79.86: bytes=1400 time=119ms TTL=48
Reply from 108.61.79.86: bytes=1400 time=119ms TTL=48
Reply from 108.61.79.86: bytes=1400 time=166ms TTL=48
Reply from 108.61.79.86: bytes=1400 time=517ms TTL=48
Reply from 108.61.79.86: bytes=1400 time=124ms TTL=48
Reply from 108.61.79.86: bytes=1400 time=126ms TTL=48
Reply from 108.61.79.86: bytes=1400 time=357ms TTL=48
Reply from 108.61.79.86: bytes=1400 time=119ms TTL=48
Reply from 108.61.79.86: bytes=1400 time=125ms TTL=48
Reply from 108.61.79.86: bytes=1400 time=167ms TTL=48
Reply from 108.61.79.86: bytes=1400 time=511ms TTL=48
Reply from 108.61.79.86: bytes=1400 time=118ms TTL=48
Reply from 108.61.79.86: bytes=1400 time=120ms TTL=48
Reply from 108.61.79.86: bytes=1400 time=327ms TTL=48
Reply from 108.61.79.86: bytes=1400 time=119ms TTL=48
Reply from 108.61.79.86: bytes=1400 time=121ms TTL=48
Reply from 108.61.79.86: bytes=1400 time=180ms TTL=48
Reply from 108.61.79.86: bytes=1400 time=502ms TTL=48
Reply from 108.61.79.86: bytes=1400 time=119ms TTL=48
Reply from 108.61.79.86: bytes=1400 time=118ms TTL=48

Ping statistics for 108.61.79.86:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 118ms, Maximum = 517ms, Average = 210ms
C:\>

Posted

Love you Blue. Additional traces from my side appear to confirm the problem is with the hosts second server/hub in line from us as that is where the spikes are starting


My Snapshot also shows a massive spike across all of the servers tested on the last 6 steps of the trace, no related ping increase reported to my client while the spike occurred. I wish I could have gotten more images across the .ibone. routes to determine if it is just an issue with the Comcast Backbone at this time and not the svc host. I have new tests running currently and will allow them to run for a half hour, I am no longer in the server.

Posted (edited)

After Marsden reset the server, the server was still rubber-banding and spiking with the 1st hop. Note the max ping of the 108.61.79.86 hop. Those happen exactly when the rubber-banding in the server happens.

 

Here is a 10 minute trace.

 

2016_11_03_PingPlotter_1stMarineRaiders_lag_post_server_reset.PNG

Edited by Blue Saber BAR

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Recent Posts

    • 2nd Platoon Weekly Attendance   Week of 13APR2025   P = Present | E = Excused | A = Absent   Platoon Staff CWO. A. Pitteway - Present 1stSgt. J. Candy -  Excused GySgt. A Yoder -  Present GySgt. R. Fielding - Excused   1st Squad Squad leader:  Cpl. M. Noel - Excused Cpl. B. Grande -  Present Cpl. R. Smith -  Present Cpl. C. Keebler - Excused Pfc. D. Moffat -  Present     2nd Squad Squad leader:  SSgt. S. Holquist - Excused Cpl. T. Scary - Present Cpl. C. Marsh - Present Cpl. W. Swift - -Present Pfc. M. Oake - Excused Pvt. R. Zera - Absent    
    • Name: Ieatalottafood   Steam I.D: STEAM_0:1:513301312   Duration of Ban: Permanent   Reasons for the Ban: tking and dropping N word in server   Demo Provided?: N   Comments: pubber made complaint via discord I witnessed the actions and banned
    • Name: Avid Eater   Steam I.D: STEAM_0:1:190401750   Duration of Ban: Permanent   Reasons for the Ban: Aimbot   Demo Provided?: Y   Comments:   avideater.dem
    • Name: jswagmoney69   Steam I.D: [U:1:211178173]   Duration of Ban: Permanent   Reasons for the Ban: inappropriate comments: "Heil Hitler, n word" couple of times    Demo Provided?: No   Comments: goose was present at the time.
    • Name: ariana grenade   Steam I.D: STEAM_0:0:830419473   Duration of Ban: Permanent   Reasons for the Ban: Team Killing and Wounding   Demo Provided?: Y/N   Comments: 7th ban in 4 months, and this one is outta here.
×
×
  • Create New...