test content
  • Games
  • Social
  • Arc News
  • Support
  • Zen
What is the Arc Client?
Install Arc
Forums > Home› Support› PC, Network, and Other Technical Issues› Windows and General: PC, Network, and Other Technical Issues

Rubber banding randomly

gvblackmoon1gvblackmoon1 Member Posts: 0 Arc User
edited September 2014 in Windows and General: PC, Network, and Other Technical Issues
Did following
ipconfig /release
ipconfig /renew
ipconfig /flushdns

Service provider Click network for network (Tacoma has it's own cable providere Click controls the cable) Advancestream for ISP.

Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 12 ms 11 ms 8 ms 10.101.0.1
3 13 ms 12 ms 14 ms click_dtn_core_10g2/2.click-network.com [131.191
.0.22]
4 9 ms 8 ms 11 ms click-cndtn7606b_10g2/4.click-network.com [131.1
91.0.92]
5 11 ms 11 ms 10 ms cr1-tacn-t4-3.bb.spectrumnet.us [216.243.28.65]

6 18 ms 13 ms 19 ms te3-5.ccr01.pdx01.atlas.cogentco.com [38.104.105
.73]
7 13 ms 13 ms 15 ms 154.54.89.58
8 22 ms 24 ms 23 ms te7-3.ccr01.boi01.atlas.cogentco.com [154.54.40.
102]
9 35 ms 31 ms 31 ms te0-7-0-8.ccr21.slc01.atlas.cogentco.com [154.54
.40.93]
10 42 ms 44 ms 45 ms be2126.ccr21.den01.atlas.cogentco.com [154.54.25
.65]
11 55 ms 54 ms 55 ms be2128.ccr21.mci01.atlas.cogentco.com [154.54.25
.174]
12 68 ms 66 ms 65 ms be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.
86]
13 90 ms 90 ms 89 ms be2137.ccr21.bos01.atlas.cogentco.com [154.54.43
.194]
14 90 ms 90 ms 89 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
15 92 ms 93 ms 91 ms 38.111.40.114
16 88 ms 91 ms 99 ms patchserver2.crypticstudios.com [208.95.185.41]


Trace complete.

C:\Windows\system32>


contacting nettest server..
Local IP: 131.191.55.159
Ping: 90.9 msec
Port: 80: 136 KB/sec 8 KB/sec 150 KB/sec 500
Port: 80: 266 KB/sec 10 KB/sec 286 KB/sec 500
Port: 443: 333 KB/sec 9 KB/sec 356 KB/sec 500
Port: 443: 311 KB/sec 12 KB/sec 334 KB/sec 500
Port: 7255: 255 KB/sec 10 KB/sec 275 KB/sec 500
Port: 7255: 256 KB/sec 9 KB/sec 276 KB/sec 500
Port: 7003: 272 KB/sec 10 KB/sec 293 KB/sec 500
Port: 7003: 257 KB/sec 9 KB/sec 279 KB/sec 500
Port: 7202: 280 KB/sec 11 KB/sec 299 KB/sec 500
Port: 7202: 279 KB/sec 10 KB/sec 300 KB/sec 500
Port: 7499: 265 KB/sec 9 KB/sec 287 KB/sec 500
Port: 7499: 335 KB/sec 12 KB/sec 359 KB/sec 500
Port: 80: 274 KB/sec 10 KB/sec 295 KB/sec 500
Idle NIC bandwidth Send: 1 KB/sec Recv: 7 KB/sec
hit return to exit
Post edited by gvblackmoon1 on

Comments

  • dllmmodllmmo Member Posts: 233 Arc User
    edited August 2014
    As it is event and give away week you might suffer a little rubberbanding at peak hours. Everybody are loggin on to claim and it will take some power off your connection.
  • gvblackmoon1gvblackmoon1 Member Posts: 0 Arc User
    edited August 2014
    Actually I'm seeing the same level as I would during the week without the special events that are running right now.
  • grouchyotakugrouchyotaku Member Posts: 0 Arc User
    edited August 2014
    gvblackmoon1 wrote: »
    Did following
    ipconfig /release
    ipconfig /renew
    ipconfig /flushdns

    Service provider Click network for network (Tacoma has it's own cable providere Click controls the cable) Advancestream for ISP.

    ...
    contacting nettest server..
    Local IP: 131.191.55.159
    Ping: 90.9 msec
    Port: 80: 136 KB/sec 8 KB/sec 150 KB/sec 500
    Port: 80: 266 KB/sec 10 KB/sec 286 KB/sec 500
    Port: 443: 333 KB/sec 9 KB/sec 356 KB/sec 500
    Port: 443: 311 KB/sec 12 KB/sec 334 KB/sec 500
    Port: 7255: 255 KB/sec 10 KB/sec 275 KB/sec 500
    Port: 7255: 256 KB/sec 9 KB/sec 276 KB/sec 500
    Port: 7003: 272 KB/sec 10 KB/sec 293 KB/sec 500
    Port: 7003: 257 KB/sec 9 KB/sec 279 KB/sec 500
    Port: 7202: 280 KB/sec 11 KB/sec 299 KB/sec 500
    Port: 7202: 279 KB/sec 10 KB/sec 300 KB/sec 500
    Port: 7499: 265 KB/sec 9 KB/sec 287 KB/sec 500
    Port: 7499: 335 KB/sec 12 KB/sec 359 KB/sec 500
    Port: 80: 274 KB/sec 10 KB/sec 295 KB/sec 500
    Idle NIC bandwidth Send: 1 KB/sec Recv: 7 KB/sec
    hit return to exit

    The 'Trace Route' results show nothing out of the ordinary, so its not a network latency issue...

    The 'Net Test' with its inconsistent throughput results is indicating a connection quality issue of some kind, that could be causing your rubber-banding issue...

    So now we need the 'Path Ping' results to pinpoint where the connection quality issue is located...
  • gvblackmoon1gvblackmoon1 Member Posts: 0 Arc User
    edited September 2014
    Pathping from today

    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
    over a maximum of 30 hops:
    0 Odin [192.168.1.8]
    1 192.168.1.1
    2 10.101.0.1
    3 click_dtn_core_10g2/2.click-network.com [131.191.0.22]
    4 click-cndtn7606b_10g2/4.click-network.com [131.191.0.92]
    5 cr1-tacn-t4-3.bb.spectrumnet.us [216.243.28.65]
    6 te3-5.ccr01.pdx01.atlas.cogentco.com [38.104.105.73]
    7 154.54.89.58
    8 te7-3.ccr01.boi01.atlas.cogentco.com [154.54.40.102]
    9 te0-7-0-8.ccr21.slc01.atlas.cogentco.com [154.54.40.93]
    10 be2126.ccr21.den01.atlas.cogentco.com [154.54.25.65]
    11 be2128.ccr21.mci01.atlas.cogentco.com [154.54.25.174]
    12 be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.86]
    13 be2137.ccr21.bos01.atlas.cogentco.com [154.54.43.194]
    14 te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
    15 38.111.40.114
    16 patchserver2.crypticstudios.com [208.95.185.41]

    Computing statistics for 400 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 Odin [192.168.1.8]
    0/ 100 = 0% |
    1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
    0/ 100 = 0% |
    2 112ms 0/ 100 = 0% 0/ 100 = 0% 10.101.0.1
    0/ 100 = 0% |
    3 109ms 0/ 100 = 0% 0/ 100 = 0% click_dtn_core_10g2/2.click-networ
    k.com [131.191.0.22]
    0/ 100 = 0% |
    4 117ms 0/ 100 = 0% 0/ 100 = 0% click-cndtn7606b_10g2/4.click-netw
    ork.com [131.191.0.92]
    0/ 100 = 0% |
    5 93ms 1/ 100 = 1% 1/ 100 = 1% cr1-tacn-t4-3.bb.spectrumnet.us [2
    16.243.28.65]
    0/ 100 = 0% |
    6 116ms 1/ 100 = 1% 1/ 100 = 1% te3-5.ccr01.pdx01.atlas.cogentco.c
    om [38.104.105.73]
    0/ 100 = 0% |
    7 119ms 1/ 100 = 1% 1/ 100 = 1% 154.54.89.58
    0/ 100 = 0% |
    8 183ms 0/ 100 = 0% 0/ 100 = 0% te7-3.ccr01.boi01.atlas.cogentco.c
    om [154.54.40.102]
    0/ 100 = 0% |
    9 134ms 0/ 100 = 0% 0/ 100 = 0% te0-7-0-8.ccr21.slc01.atlas.cogent
    co.com [154.54.40.93]
    0/ 100 = 0% |
    10 127ms 0/ 100 = 0% 0/ 100 = 0% be2126.ccr21.den01.atlas.cogentco.
    com [154.54.25.65]
    0/ 100 = 0% |
    11 163ms 0/ 100 = 0% 0/ 100 = 0% be2128.ccr21.mci01.atlas.cogentco.
    com [154.54.25.174]
    0/ 100 = 0% |
    12 167ms 0/ 100 = 0% 0/ 100 = 0% be2156.ccr41.ord01.atlas.cogentco.
    com [154.54.6.86]
    1/ 100 = 1% |
    13 153ms 1/ 100 = 1% 0/ 100 = 0% be2137.ccr21.bos01.atlas.cogentco.
    com [154.54.43.194]
    0/ 100 = 0% |
    14 185ms 1/ 100 = 1% 0/ 100 = 0% te4-4.ccr01.bos06.atlas.cogentco.c
    om [66.28.4.42]
    0/ 100 = 0% |
    15 156ms 1/ 100 = 1% 0/ 100 = 0% 38.111.40.114
    0/ 100 = 0% |
    16 136ms 1/ 100 = 1% 0/ 100 = 0% patchserver2.crypticstudios.com [2
    08.95.185.41]

    Trace complete.
  • grouchyotakugrouchyotaku Member Posts: 0 Arc User
    edited September 2014
    gvblackmoon1 wrote: »
    Pathping from today

    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
    over a maximum of 30 hops:
    0 Odin [192.168.1.8]
    1 192.168.1.1
    2 10.101.0.1
    3 click_dtn_core_10g2/2.click-network.com [131.191.0.22]
    4 click-cndtn7606b_10g2/4.click-network.com [131.191.0.92]
    5 cr1-tacn-t4-3.bb.spectrumnet.us [216.243.28.65]
    6 te3-5.ccr01.pdx01.atlas.cogentco.com [38.104.105.73]
    7 154.54.89.58
    8 te7-3.ccr01.boi01.atlas.cogentco.com [154.54.40.102]
    9 te0-7-0-8.ccr21.slc01.atlas.cogentco.com [154.54.40.93]
    10 be2126.ccr21.den01.atlas.cogentco.com [154.54.25.65]
    11 be2128.ccr21.mci01.atlas.cogentco.com [154.54.25.174]
    12 be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.86]
    13 be2137.ccr21.bos01.atlas.cogentco.com [154.54.43.194]
    14 te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
    15 38.111.40.114
    16 patchserver2.crypticstudios.com [208.95.185.41]

    Computing statistics for 400 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 Odin [192.168.1.8]
    0/ 100 = 0% |
    1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
    0/ 100 = 0% |
    2 112ms 0/ 100 = 0% 0/ 100 = 0% 10.101.0.1
    0/ 100 = 0% |
    3 109ms 0/ 100 = 0% 0/ 100 = 0% click_dtn_core_10g2/2.click-networ
    k.com [131.191.0.22]
    0/ 100 = 0% |
    4 117ms 0/ 100 = 0% 0/ 100 = 0% click-cndtn7606b_10g2/4.click-netw
    ork.com [131.191.0.92]
    0/ 100 = 0% |
    5 93ms 1/ 100 = 1% 1/ 100 = 1% cr1-tacn-t4-3.bb.spectrumnet.us [2
    16.243.28.65]
    0/ 100 = 0% |
    6 116ms 1/ 100 = 1% 1/ 100 = 1% te3-5.ccr01.pdx01.atlas.cogentco.c
    om [38.104.105.73]
    0/ 100 = 0% |
    7 119ms 1/ 100 = 1% 1/ 100 = 1% 154.54.89.58
    0/ 100 = 0% |
    8 183ms 0/ 100 = 0% 0/ 100 = 0% te7-3.ccr01.boi01.atlas.cogentco.c
    om [154.54.40.102]
    0/ 100 = 0% |
    9 134ms 0/ 100 = 0% 0/ 100 = 0% te0-7-0-8.ccr21.slc01.atlas.cogent
    co.com [154.54.40.93]
    0/ 100 = 0% |
    10 127ms 0/ 100 = 0% 0/ 100 = 0% be2126.ccr21.den01.atlas.cogentco.
    com [154.54.25.65]
    0/ 100 = 0% |
    11 163ms 0/ 100 = 0% 0/ 100 = 0% be2128.ccr21.mci01.atlas.cogentco.
    com [154.54.25.174]
    0/ 100 = 0% |
    12 167ms 0/ 100 = 0% 0/ 100 = 0% be2156.ccr41.ord01.atlas.cogentco.
    com [154.54.6.86]
    1/ 100 = 1% |
    13 153ms 1/ 100 = 1% 0/ 100 = 0% be2137.ccr21.bos01.atlas.cogentco.
    com [154.54.43.194]
    0/ 100 = 0% |
    14 185ms 1/ 100 = 1% 0/ 100 = 0% te4-4.ccr01.bos06.atlas.cogentco.c
    om [66.28.4.42]
    0/ 100 = 0% |
    15 156ms 1/ 100 = 1% 0/ 100 = 0% 38.111.40.114
    0/ 100 = 0% |
    16 136ms 1/ 100 = 1% 0/ 100 = 0% patchserver2.crypticstudios.com [2
    08.95.185.41]

    Trace complete.

    'Path Ping' results show dropped packets around the Cogent Boston Hub, as well as your ISP gateway to the Cogent Backbone...

    You should open up a ticket with Cryptic/PWE about the Cogent Boston Hub congestion, as well as your ISP Tech support to see if they can fix the problem with their gateway hub...
Sign In or Register to comment.