For what it's worth, here's the explanation they gave me regarding the problems today and yesterday (I had stuck orders/positions during the problem timeframes both days):
"Normally the Globex B channel sends identical data as the A channel and can be used during high volume periods to make sure all ticks are captured. Monday, Globex's B channel sent huge microbursts of data that were inconsistent with the A channel data. The continued data bursts caused delayed or denied responses for orders and modifications. Once the issue was discovered, the B channel was deactivated restoring normal trading conditions. The B channel will remain inactive until some hardware and network modifications are made that will prevent exchange data issues from impeding order flow. How is this being resolved to prevent it from happening again? When this first occurred last week, Zen-Fire engineers were the ones to notify the exchange about it. They (Zen-Fire) put in place hardware and network modifications to anticipate these types of issues. Yesterday, Zen-Fire engineers caught this even faster due to the new modifications, but it wasnât until yesterday afternoon that the exchange made changes on their end to prevent it from happening in the future."
As I understand it, the B channel is what gives the higher data rates that supplies unfiltered data to ZF, unlike to other platforms (thus the reason why other platforms didn't have the difficulties).
In my opinion, they were not lying in describing the source of the problem.
I guess it goes to show nobody is perfect. It seems that every freaking broker is having some issues in futures these days.