Not sure if its possible but i think there getting worse lol
My trades tonight from WA went straight through, no problem. At the same time I was soaking up my available bandwidth with three separate data streams (MT4, Reuters and IB TWS), downloading a swag of large applications and data, and simultaneously conducting file transfers whilst VoIP chatting with another trader in Qld whose Go Market trades were also "spot on".
Do you ever have the feeling, if you're the only one having problems (or one of the few) the problem might be at your end?
Have you checked everything which can be checked and eliminated these as possible causes before blaming the broker? Are the delays at your computer processing the "order" instruction, the connection sending the instruction, the broker receiving the instruction, or the broker acting on the instruction, or you receiving receipt of confirmation of the action being completed? How can you prove this? How are you measuring the delay? Do you keep a forensic-accurate record of mouse clicks/keyboard activity versus trade execution times which can be analysed to try and identify possible causes? Look for some less-than-obvious causes; anti-virus interference, software conducting an auto-update, downloading/streaming videos/audio at the time of placing a trade, email clients searching for new email etc. Who is your ISP and what traffic do they have at these times when you experience these delays? (Remember: certain people do most of their big downloads at off-peak times, these vary with ISP and clientele.) There are many, many possible causes.
Although modern-day computing is as common as sliced bread, it is still a highly technical and complicated field of endeavour. Discovering the cause(s) of problems often takes more effort than writing the application in the first place, especially when the "problem" application is run with other hardware, programs and operating system services (not all of these play nicely with each other either!) Add networking and telecommunications to the issue and the problem complexity increases exponentially. You might even discover "blame" for the error is distributed i.e. no single entity is entirely responsible for the problem (then the fun really starts!)
Like most things, the problems closest to home are the problems most easily rectified so try looking there first before looking further afield.
wabbit