So, Frogster has refused to centralize efforts into a single thread and has, instead, opted to troll other threads that were critical from the beginning in hopes of getting good support from the community. As such, I am starting this thread as a suggestion forum to provide a central place for feedback and support.
As per Roeksha:
Wewill not shutdown Siege Wars for several reasons. We are as of yet not sure what the problem is, we can try fixes, but when Siege War is offline there is noway to verify if this fixed the actual problem. Our QA team is unable to reproduce a 'stresstest' of approx. 3000 players in Siege War. You are not our testdummies, but we do need your help to gain information if the changes we made helped at all.
This problem with the stress test that you are having an issue recreating on your own can be solved. Enlist the player base for a second round of siege in the mornings until the solution is found. A tertiary siege midday might even be possible. The full population that is represented at evening siege times might not even be necessary for a useful test. We have asked for a chance to become involved via a test server for other issues many times before. Perhaps it is time to listen to us.
Additionally, I'll add my own observations on the issue. The lag looks suspiciously like bandwidth throttling on the part of the owners of the server bank you switched to. The fact that it occurs midway through siege makes it look like an automatic response to an increased server load.
ISP's have also been known to throttle certain types of traffic and we ARE talking about Miami here. I'm not sure what kind of WAN access is used by the server bank but it is worth looking into.