It is most certainly Cogentco that's responsible for the connection problems guaranted.
After two months now, I can say without a doubt it is their backend causing the problems.
With that said, I don't see a resolution to this mess unless SE move their DataCenter somewhere else because I have to imagine SE know by now it is them and have known for a while and there is still no resolution.
Cogentco can't handle the load, It is clearly their backend. During peak times, more will notice the issues and experience them.
Over the past two months, I have been working with Comcast (HQ in PA) to determine if it is their (Comcast's) network with their maint/escalation department since I raised the question of whether or not they are throtteling it as P2P and their engineer (read: not Tier 1, not Tier 2) and we have found nothing wrong with the routing between myself and at least them.
With that in hand, I have gathered tracerts from more than a few handful of people, spread across the U.S. who connect to the U.S. Data center (in Montreal) and they all exhibit the exact same behaviour. Time outs, or extrodinarily high latency once they reach Cogentco's backend.
The reason some don't experience issues, or less issues is most certainly the time of day and Cogentco's ability to spread the load to so many connections. Unless Cogentco address the problem, SE will continue to see these issues occur and I suspect, that's why after 140 pages of blaming our ISP's (the hundreds of them) it means, they either have not bothered to contact our ISP's (the hundreds of them) to remediate the issue or they know that it isn't our ISP's and know Cogentco can't handle the load and saying as much would be very damaging to the success of the game.
Wouldn't it be ironic if the throtelling were P2P directly out the backend from Ormuco. I mean, maybe THEY are not provisioned for the correct loads.
Not likely I'm sure, since I would bet that's where they started looking.