CF is pinging at 150-250ms for me now, with a lot of dropped packets. My ping was something like 25-50 before. I noticed a number of people on dio's are having the same problem.

Is there anything that can be done (by me or by any of you) to alleviate this? I wanna play. :(

I've been running extensive pings and things looking pretty normal to me now. Is anyone still seeing the lag spikes we were having previously?

dsfvadv

Sometimes I get random spikes of lag. They usually last only about 6 to 10 seconds, but it's enough to screw up a PK if the timing is bad. On occasion I get completely disconnected. During these lag spikes, I am still able to connect to other sites smoothly.

Next time you have a spike try a traceroute, and try connecting to other sites that are definitely hosted in the U.S.

Traceroute seems to imply the problem is the US end.

But when I played from Canada recently, it was fine (mostly).

Nt

Made constant attempts. Finally, I tried a few hours ago and it worked. I'm from the west coast, U.S.

It is 10 o'clock PM, Day of the Sun
20th of the Month of the Heat in the year 1766.
It is currently nighttime.
The moon is currently full.

The Carrion Fields started up at Fri Dec 23 22:07:22 2011 (CST)
The system time is Sun Dec 25 02:15:47 2011 (CST)
You have been logged in for 1 hour and 13 minutes.


Conecting from Sweden.

Hope that helps. My two group mates laged out as well in this time. No idea where they're from though.

For a few days after the 18th, my ping and traceroutes looked the same as before, with lots of dropped packets and an average of 350.

Yesterday and today, however, I see a REALLY solid average of 114, with only one spike, pasted below. I'm pretty happy, all told.






C:\Users\>ping 66.85.154.235 -n 100

Pinging 66.85.154.235 with 32 bytes of data:
Reply from 66.85.154.235: bytes=32 time=112ms TTL=49
**snip***
Reply from 66.85.154.235: bytes=32 time=114ms TTL=49
Reply from 66.85.154.235: bytes=32 time=112ms TTL=49
Reply from 66.85.154.235: bytes=32 time=139ms TTL=49
Reply from 66.85.154.235: bytes=32 time=186ms TTL=49
Reply from 66.85.154.235: bytes=32 time=299ms TTL=49
Reply from 66.85.154.235: bytes=32 time=110ms TTL=49
***snip***
Ping statistics for 66.85.154.235:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 110ms, Maximum = 299ms, Average = 114ms

ntnt

I have to refresh the site multiple times in order to be able to connect to www.carrionfields.com and the forums (I have to refresh for both separately). The forums generally work after I get through.

They've been getting emails from other folks as well and are aware of the short lag out periods that have occured over the past few weeks.


The issue appears to be large traffic spikes affecting different areas of the network. Our provider has been notified and they are aware and already in the process of network upgrades to resolve the issues. Over the next couple of weeks they will be replacing their routing network as well as the in-rack switches to improve network performance.


They also mentioned that when testing your ping not to use any tool like 'just-ping.com' as the firewalls are designed to block ping floods and other networking tools to prevent DoS attacks.

I've been seeing the same spikes as you just doing 'ping -n 10000 www.carrionfields.net' and when the spikes hit, I usually drop to about 50% packet loss.

If you see more instability, please email me the time (preferably the exact system time) and I will continue to pass it along to the support staff.

I still have yet to experience this. I wonder if it's only happening from certain geographies?

$ mtr -r -c 20 carrionfields.net
HOST: NOTTELLING                   Loss%   Snt   Last   Avg  Best  Wrst StDev
snip snip snip
  7. te0-2-0-1.ccr21.ord01.atlas.  0.0%    20   54.3  39.1  11.9 179.0  45.8
  8. te0-3-0-0.ccr21.mci01.atlas.  0.0%    20   24.9  44.2  24.2 170.4  41.9
  9. te0-3-0-1.ccr21.dfw01.atlas.  0.0%    20   34.8  52.1  34.6 180.8  41.0
 10. te0-1-0-1.ccr21.iah01.atlas.  0.0%    20   40.0  56.5  39.9 181.8  38.7
 11. te7-1.ccr01.sat01.atlas.coge  0.0%    20   67.7  91.5  67.2 189.6  43.0
 12. te7-2.ccr01.phx02.atlas.coge  0.0%    20   68.0  94.4  67.6 193.7  46.0
 13. vl3512.na41.b023003-0.phx02.  5.0%    20   71.3  91.7  68.9 165.0  35.2
 14. 38.104.116.186                0.0%    20   77.0  98.8  68.9 248.1  46.6
 15. bb2.cwie.10.2.phx0.cwie.net   0.0%    20   68.6 119.0  68.3 390.8  94.0
 16. ???                          100.0    20    0.0   0.0   0.0   0.0   0.0
 17. 66.85.154.234                 0.0%    20   69.4  93.5  68.7 311.0  60.8
 18. riverwind.thirdhosting.com   10.0%    20   68.9  84.3  68.8 253.1  45.4

Third Hosting is having problems. Wait it out, I guess.

HOST: local Loss% Snt Last Avg Best Wrst StDev
1. 192.168.1.1 0.0% 20 0.6 0.6 0.6 1.1 0.1
2. 98.222.132.1 0.0% 20 20.2 27.0 19.2 48.8 7.0
snip snip snip
4. te-0-7-0-6-ar01.elmhurst.il. 0.0% 20 22.0 22.3 20.0 32.5 2.5
5. pos-0-1-0-0-ar01.area4.il.ch 0.0% 20 21.9 22.7 20.2 41.8 4.5
6. pos-3-6-0-0-cr01.350ecermak. 0.0% 20 25.8 25.3 22.0 32.0 2.5
7. pos-0-3-0-0-cr01.chicago.il. 0.0% 20 21.2 23.0 21.1 32.3 2.3
8. pos-1-13-0-0-cr01.denver.co. 0.0% 20 49.2 48.6 47.3 50.1 0.8
9. pos-0-10-0-0-cr01.seattle.wa 0.0% 20 75.1 75.6 73.0 86.6 2.8
10. pos-0-2-0-0-pe01.seattle.wa. 0.0% 20 73.0 74.3 72.3 84.2 2.7
11. 75.149.231.130 20.0% 20 97.4 102.1 97.2 121.8 6.3
12. unknown.hwng.net 20.0% 20 149.4 127.8 120.8 149.4 7.5
13. e2-1.r1.ph.hwng.net 25.0% 20 133.3 136.9 131.2 162.5 7.9
14. cwie-1.ph.hwng.net 20.0% 20 133.2 132.9 131.5 135.1 0.9
15. bb2.cwie.10.2.phx0.cwie.net 25.0% 20 161.6 138.6 131.7 193.0 16.8
16. 172.28.0.2 85.0% 20 147.0 146.1 141.8 149.5 4.0
17. 66.85.154.234 95.0% 20 133.2 133.2 133.2 133.2 0.0
18. riverwind.thirdhosting.com 25.0% 20 133.0 133.7 131.9 143.7 2.8


Also, mtr is a really cool tool I didn't know about. Thanks for that. I wouldn't "wait it out" if I was Zulg though, I'd be contacting the hosting company about 25% packet loss. That's pretty unacceptable.

My packet loss is less bad tonight, but I'm in the 250-350ms range now.

I just did two ping tests, one from my work machine and one from another host where I have a shell account. Results:

100 packets transmitted, 100 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 39.834/40.445/41.396/0.303 ms

100 packets transmitted, 100 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 44.745/45.007/46.169/0.238 ms

   

Couldn't that be a clue? Like you are that side of a screwy relay?

I know nothing about these things though.

I did when it was in Texas. Now it seems to be in Tempe, AZ.

Guess they got it resolved.

I'm not sure how you still have such good pings when the machine moved to seattle and you were close to it when it was in texas... I thought. I'm jealous.

Just reran my test and am seeing 25% loss again. Would love to see if this is the case for others (essentially right now) as well.

Actually it is way worse now (as high as 60% packet loss)

F'ing ridiculous.

asdf

Anything you guys can do to fix this? Nudge them a bit?

A few times that I do want to play, I'm not going to play/risk playing because I can't do anything due to packetloss

>Anything you guys can do to fix this?

There is nothing I can do to fix it.

>Nudge them a bit?

I opened a support ticket, we'll see if anythign comes from it.

7 95 ms 96 ms 95 ms be-10-802-pe01.111eighthave.ny.ibone.comcast.net
<75.149.231.113>
8 99 ms 99 ms 98 ms pos-1-8-0-0-cr01.newyork.ny.ibone.comcast.net <6[br/>8.86.86.45]
9 102 ms 102 ms 102 ms pos-0-8-0-0-cr01.ashburn.va.ibone.comcast.net <6[br/>8.86.87.205]
10 114 ms 115 ms 115 ms pos-4-12-0-0-cr01.atlanta.ga.ibone.comcast.net
11 170 ms 170 ms 170 ms pos-1-8-0-0-cr01.dallas.tx.ibone.comcast.net <68[br/>.86.88.61]
12 171 ms 170 ms 171 ms pos-0-9-0-0-cr01.losangeles.ca.ibone.comcast.net
<68.86.87.253>
13 170 ms 170 ms 170 ms pos-2-10-0-0-cr01.sanjose.ca.ibone.comcast.net
14 171 ms 171 ms 171 ms pos-0-9-0-0-ar01.sfsutro.ca.sfba.comcast.net <68[br/>.86.90.234]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.

Wondering if my problems accessing this website (fail several times before eventually succeeding) might be related.