Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

Why does sourceop hate australians? ;.;
#1

It seems every move or change makes the ping that much worse...

The question here being has is recently moved?

I didn't notice any news updates but my ping has gotten from 280 (barely playable) to 410 (completely unbearable)..Seems every move gets further and further away...i anticipate in a few months you'll be hosting from the moon at this rate. O.o

Anyway the point of the post is my ping has gone up and if there hasn't been a recent move (of what looks to be a few of the servers, namely no mods no bs 24/7 2fort) then has anyone got any ideas, i've killed my router/connection, pc, etc.
Reply
#2

it's either valve's fault or the (terrible) server provider

[Image: hell-met.jpg]
Reply
#3

Source doesn't hate you phate, it's just that nomods server has been terrible with the lag lately. Play on the server for more then five minutes and it's all anyone complains about(Other than hell-met and his abuse of pipebombs and admin power)
Reply
#4

There haven't been any recent moves. The servers are still in Texas. If you want to be helpful, post tracert results.
Reply
#5

I did the trace on the server end. It seems to be a fault with ntt.

Code:
traceroute to 123.243.34.237 (123.243.34.237), 30 hops max, 40 byte packets
1  mpdedicated.com (174.37.110.65)  197.616 ms  197.714 ms  197.795 ms
2  po105.dar01.sr01.dal01.networklayer.com (66.228.118.220)  0.357 ms  0.469 ms                                 0.516 ms
3  ae6.bbr01.eq01.dal03.networklayer.com (173.192.18.210)  0.252 ms  0.259 ms                                 0.260 ms
4  ae-6.r07.dllstx09.us.bb.gin.ntt.net (157.238.224.225)  0.403 ms  0.638 ms  0                               .747 ms
5  ae-6.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.66)  0.457 ms  0.451 ms  0.45                               4 ms
6  ae-0.r21.dllstx09.us.bb.gin.ntt.net (129.250.2.59)  0.455 ms  0.481 ms  0.47                               8 ms
7  ae-4.r21.chcgil09.us.bb.gin.ntt.net (129.250.2.201)  34.574 ms  35.256 ms  3                               5.206 ms
8  ae-0.r20.chcgil09.us.bb.gin.ntt.net (129.250.3.97)  31.000 ms  35.380 ms  26                               .590 ms
9  as-1.r23.nycmny01.us.bb.gin.ntt.net (129.250.6.14)  44.551 ms  54.197 ms  50                               .851 ms
10  ae-0.r22.nycmny01.us.bb.gin.ntt.net (129.250.3.72)  54.890 ms  55.744 ms  45                               .665 ms
11  as-1.r22.londen03.uk.bb.gin.ntt.net (129.250.3.255)  117.264 ms  126.809 ms                                 112.239 ms
12  ae-0.r23.londen03.uk.bb.gin.ntt.net (129.250.4.86)  125.655 ms  129.017 ms                                 118.385 ms
13  as-3.r22.amstnl02.nl.bb.gin.ntt.net (129.250.4.19)  120.376 ms  133.779 ms                                 137.029 ms
14  as-2.r23.amstnl02.nl.bb.gin.ntt.net (129.250.2.119)  129.101 ms  139.852 ms                                 124.735 ms
15  po-2.r00.amstnl02.nl.bb.gin.ntt.net (129.250.2.231)  123.077 ms  123.688 ms                                 129.077 ms
16  Vlan585.icore1.AD1-Amsterdam.as6453.net (195.219.150.77)  131.833 ms  129.35                               9 ms  145.008 ms
17  if-3-3205.tcore1.AV2-Amsterdam.as6453.net (195.219.150.94)  129.748 ms  126.                               266 ms  137.230 ms
18  if-7-2.tcore2.NJY-Newark.as6453.net (195.219.194.1)  179.868 ms  175.818 ms                                 175.111 ms
19  if-1-3.tcore2.LVW-LosAngeles.as6453.net (64.86.252.57)  183.728 ms  183.489                                ms  186.616 ms
20  if-2-2.tcore1.LVW-LosAngeles.as6453.net (66.110.59.1)  190.450 ms  217.873 m                               s  217.861 ms
21  * if-2-2.tcore2.LVW-LosAngeles.as6453.net (66.110.59.2)  190.884 ms  188.379                                ms
22  if-14-0-0-1984.mcore5.LAA-LosAngeles.as6453.net (64.86.252.22)  187.928 ms                                 189.402 ms  193.802 ms
23  if-1-0-0.core4.SQN-SanJose.as6453.net (209.58.33.86)  335.264 ms  335.356 ms                                 335.358 ms
24  Vlan1282.icore1.SQN-SanJose.as6453.net (216.6.30.74)  204.863 ms * Vlan1282.                               icore1.SQN-SanJose.as6453.net (216.6.30.74)  203.877 ms
25  Vlan516.icore1.SQN-SanJose.as6453.net (66.198.97.34)  413.068 ms  404.584 ms                                 417.365 ms
26  syd-pow-cla-csw2-po-1.tpgi.com.au (202.7.162.10)  375.289 ms  373.610 ms  38                               4.777 ms
27  syd-pow-cla-bras7-port-channel-2.tpgi.com.au (202.7.166.71)  372.752 ms  376                               .329 ms  373.021 ms

The packets are seriously going from Dallas, to Chicago, New York, Amsterdam (where it seems to switch provider), back to New Jersey, then to LA, then to San Jose, and then make its way to Australia. Fucking nuts.

These sorts of things typically resolve themselves, but post back again if not. How long has it been an issue?
Reply
#6

Well, the ping increase has been as of the date of the thread (yesturday), i first done isolation tests to see if it was myself then posted.
Reply
#7

Yeah, been around 5 days so far and no sign of change looks like i'm stuck with it Cry
Reply
#8

well, some1 needs to make a call / mail to ntt to make 'm aware...
Reply
#9

I imagine df has mentioned it.

I was a commando you know.
Reply
#10

I'm not seeing it anymore on the server end. Pings in the mid 200s. Do a trace on your end to confirm.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)