I can only speculate as to what the issue is as I don't have root access to Tata racks and Ormucos fiber.
I have no doubt that the Square is aware of the issue and that the servers going down for maintenance is, in part, to alleviate the latency spikes. Though the client is owned by Square, their servers and their fiber nodes are run by another company. The bonus to this is that Square doesn't have to field or staff techs to monitor and maintain servers. Square also doesn't have to buy servers so they save money. The drawback is when something goes wrong, they are helpless to actually correct the issue. All they can do is field master tickets on Tata and Ormuco CRM databases.
The maintenance scheduled for 9/11/13 is quite long. This actually tells us that there is going to be hardware changes and upgrades. 2-3 hour maintenance are more software (client) side. 8-12 hours signifies that hardware on the MPLS and servers are being modified.
If the fix today doesn't correct the issues users are seeing, there are a couple of things to try:
1.) If using wifi, attempt to hardline the connection. Does the congestion clear up?
2.) Be sure to open and forward the ports Square has detailed in a stickied thread in the tech support Forums.
3.) You may clear the issue using a third party program such as PingZapper or the like. I prefer to not use this method. Using a third party program leaves you at the mercy of the program and the company who services it. This is a band aid for the root problem. You would essentially be treating the symptom, not curing the disease.
4.) VPN's have been reported to help clear the issue. This is a gamble as VPN's work just like Tata does. Multiple users and the connection slows down and lags. The VPN may be able to re route you on a different route path essentially avoiding the high traffic data centers and ports.
I had a few questions about your data. Are these polls before or after PingZapper? The reason I ask is that you have an extra hop through a data center that I haven't seen on any trace routes I've found on the Forums:
13 61 ms 62 ms 109 ms te8-3.dr10.mtl.iweb.com [67.205.127.238]
This data center is run by iweb:
http://iweb.com/about/vision
I haven't seen this hop on either my own, or others trace routes. I've also noticed that your ping times are relatively low and are pretty close together (60-120ms). I wonder if this is because of the scrubber, or if you're routing through another data center that Square may have picked up.
Verizon, though meaning well, is inaccurate in stating the issue is with the Game Provider. Looking over your parsing data, I see that you have low ping times. I don't see a whole lot of fluctuation. What I do see is the glaring time out requests. Your connection to the server port (Tata) is either congested or is dropping due to load. Yours is an excellent example of how the server you're connecting to behaves when congested or not specd to handle the amount of volume it's seeing.
Your issue unfortunately cannot be corrected by any via client side means. This is an issue with the actual server load and shows that the racks are congested and cannot negotiate with the amount of users it sees at this time. Until the server provider expands the servers (partition/addition) and redistributes the port assignments, the issue will persist.
Apologies for the long post!