Has anyone else had their server updated to R32?

Mine has not been which is strange given that as other GSP's state:

"All Battlefield 4 ranked game servers will be automatically updated immediately per DICE’s requirements, apologies to all the server owners with populated servers!"

I realise there is not much in R32, however with everything else that is going on, I am wondering why no server update also?

We are currently experiencing some problems with DICE getting the patch to us, we have them working on a solution and should have something up soon.

They are working on a solution to sending you a single file? I'm sure you felt embarrassed saying that ;)

I have read a few unhappy post (in other forums) in regards to R32 server patch maybe it is good that I don't have it yet but it would be nice to know why we have not got it yet or when you plan to roll it out so we are not upset when our servers empty out Oh wait servers are already empty because you can't stop people being kicked out of the servers over the last 8 days so nobody wants to play on our servers anyway :(

Glad to hear you have found a suitable alternative..

Been on R32 since it was available (auto deployed as per DICE requirements, naughty AusGamers!)....
Been pretty solid and stable since deployment. We had some issues on our Siege server, but that was box related and not patch related, the Vanilla server has been stable since deployment and not gone down once since.
Would be odd to not roll this out as in my opinion its a hell of a lot more stable than the last build was....
Interested to know why AusGamers have not deployed this :)
(dont think anyone is home to deploy it based on my past experience with AG and service...)

BF4Admin / Static: we don't use FTP for these transfers, and the issue was with a backbone link in the US. If you are going to be condescending, you'll want to be sure of your facts first.

Ahhh.. excuse me?

I thought we were the ones paying for a service here? Who gives a f**k if its FTP, email or snail mail, the point is that you are taking our money happily, yet not providing us with what we are paying for.

To clarify, what I pay for is:

1 - A server that works, reliably, 24/7
2 - Updates to be applied on time

While I am sure that talking about backbone links to the US sounds fancy and muddies the waters, the truth is that international internet traffic was working during the timeframe, and the traffic should have been re-routed.

I was not being condescending, I was serious - surely another form of transmission was possible. They call it business continuity ( <---- that is me being condescending).

Enough with the excuses, simply fix the problems or stop providing the service.

While I am sure that talking about backbone links to the US sounds fancy and muddies the waters, the truth is that international internet traffic was working during the timeframe, and the traffic should have been re-routed.

I was not being condescending, I was serious - surely another form of transmission was possible. They call it business continuity ( <---- that is me being condescending

Another form of transmission was not possible. R32 was not a client compatibility patch, so extraordinary measures were not contemplated. DICE were aware of the situation and were not alarmed - we were in communication with them about the issue at all times.

Neither we nor DICE have any control over transit in the US. The only way we would be able to alter the routing is to alter the endpoints. DICE were not able or willing to do so - they have a specific system for delivering patches to us that is not up for debate. That left us to alter the physical location of our repository. This is not trivial; we needed to build a new system to their specifications in a different datacentre. We do have access to a few options here (through our very good friends at Mammoth Networks and Binary Lane, but before we had a chance to build a repository the transit issue was resolved by the US company and we received the R33 patch in time to deploy it.

As for business continuity - that is an issue that is balanced against security and necessity. If it was the R33 patch that was unable to be sent (a client compatibility patch that is mandatory for people to join servers) we would have had staff working after hours to build the alternative repository or DICE would have sent the patch from an alternative location. They have done this in the past for other client compatibility patches - one of the great people at DICE pretty much pulled an all-nighter a few months ago for exactly this reason. The decision was made that R32 didn't warrant this level of time expenditure. DICE know what is in the patches, so it is their call.