Thread: Post 2.1 Lag spike (Still not resolved)

Problem still exists, still making anything post T1 pretty much impossible.

Anyone have any preferences between pingzapper, wtfast and battleping?

bump bump bumpity

| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|te0-17-0-3.ccr41.ham01.atlas.cogentco.com - 0 | 2701 | 2701 | 47 | 50 | 84 | 51 |
| be2188.mpd21.ams03.atlas.cogentco.com - 0 | 2701 | 2701 | 52 | 56 | 79 | 55 |
| be2182.ccr21.lpl01.atlas.cogentco.com - 0 | 2701 | 2701 | 60 | 64 | 92 | 64 |
| be2384.ccr21.ymq02.atlas.cogentco.com - 0 | 2701 | 2701 | 131 | 136 | 163 | 135 |
| 38.122.42.34 - 0 | 2701 | 2701 | 131 | 134 | 165 | 131 |
| 192.34.76.10 - 6 | 2196 | 2069 | 133 | 146 | 208 | 145 |
| 199.91.189.242 - 7 | 2176 | 2044 | 135 | 146 | 680 | 143 |
| 199.91.189.47 - 7 | 2153 | 2015 | 135 | 145 | 163 | 138 |

Another good day where square's ISP fails to communicate with cogentco

lol.... just lol.

I quit my sub after 2 months because of this issue, and I keep checking back on the forums every month to see if it is resolved. Hard to believe these issues have not been addressed yet.

The decision to throw all NA/EU servers into the same data center in Montreal was a huge mistake. Why it is not possible for SE to put up servers in other locations is just beyond me. Its almost as if they want a smaller user base so its easier for them to manage.

I m so sorry about that.. this monte sub has gone without playin do to this lag prob... My connection works at all But a part 2 hours on friday night i cannot play, at least an answer from SE would be Well accepted..

Originally Posted by Lurkios

Problem still exists, still making anything post T1 pretty much impossible.

Anyone have any preferences between pingzapper, wtfast and battleping?

I like WTFast for their tunnel to tunnel protocols.

Originally Posted by ntall1

lol.... just lol.

I quit my sub after 2 months because of this issue, and I keep checking back on the forums every month to see if it is resolved. Hard to believe these issues have not been addressed yet.

The decision to throw all NA/EU servers into the same data center in Montreal was a huge mistake. Why it is not possible for SE to put up servers in other locations is just beyond me. Its almost as if they want a smaller user base so its easier for them to manage.

Money.

Data Centers cost tens of millions of dollars. If the ROI isn't there or the investor board isn't keen on hiring people, buying equipment (ever look at how much commercial grade blades cost?), Securing deals with ISP's, running interconnect lines, negotiating rent locations/buying buildings, setting up the servers (including cooling, maintenance, locking down OEM lines of support and hardware acquisition), hiring IT admins to monitor and patch, having another physical location for HQ to watch and measure for performance. All for a game that's less than a year old, that they had to remake because the first did so bad essentially doubling/tripling the cost of production. No one would sign off on that. Not the CFO, CEO, Accounting, Directors, hell I doubt Yoshi would let that go if he had the power to make it happen.

Square JUST turned a profit. They won't risk loss. They can't afford to. Their majority sharholders won't allow them to.

They COULD rent racks (I'm glad they don't. Shows they actually care enough to manage their own servers) but that comes with a whole other set of challenges.

Also keep in mind that the NA data center in Montreal is manned by three people. THREE. It's not a department it's 2 IT Admins and a lead. That they are able to run patches like they are and fielding new issues is pretty impressive for essentially 2 guys and lead.

Still having same bad problem problem :/
here some test in the issue hour:

http://imgur.com/TZCBwNH,eGKsjbG#0
http://imgur.com/TZCBwNH,eGKsjbG#1

so here is a long tracet from my Verizon fios ISP at my house all the way to Hyperion data center. IF you look you can see at level3 in New York and at level3 in Montreal there is consistent packet loss. The unexpected packet loss is also happening directly at the SE server for Hyperion. This is unacceptable