Maybe it's due to the firewall problem that caused the "emergency maintenance". The pidgeons in the host's datacentre must have eaten the hamsters' food.

http://fm.en.kupaisky.com/Community/Forum/View.aspx?num=7738&searchtype=0&pagecount=0&searchvalue=&sort=5&category=Z01&page1=1

Last three routes are returning 30-40% packet loss.
Using Ping Plotter STD Edition
Trace to 211.43.149.201
Avergae report time 14:00 to 16:00 AEST 10th March 2012

12 hops no packet loss.
13 134.159.62.198  I3-peer.eqnx02.pr.reach.com  = 0% packet loss
14.  4.53.208.10       PANTHER-EXP.edge1.sanjose3.level3.net = 12% packet loss
15   174.35.18.82     = 30% packet Loss
16   174.35.13.242   = 30% packet Loss
17   211.43.149.201 = 30% packet Loss

The LAST 4 hops are lossing packets
There used to be a hop between 16-17 that had a 30% loss but this has been removed.

So....
Recap..
Change of Switch port on Servers
"new" or "refurbished" hardware
Firewall Changes
Removal of 1 hop.
Firewall changes mk2
Firewall change emergency fix 1

Result: Same hosting company and Same laggy crap.
            Same BGP routing issues.

Next attempted to fix is..?

Absolutely unplayable, great time to have an event when you didnt even fix the issue.

How is it even possible to be so incompetent.