Home Your Tech Mobility ANZ goMoney users get no money
ANZ goMoney users get no money Featured

ANZ customers using the bank's iOS and Android apps were left in the lurch today after a system-wide error rendedered the app useless.

Various reports have confirmed that on both the iOS and Android ANZ goMoney apps some customers received a message saying “service has been interrupted”, meaning they couldn't access their funds at all.

Meanwhile when other users attempted to enter their PIN, a message would read “Incorrect passcode. Last try”.

Website Aussie Outages, which tracks Aussie outages through social media reports, detected hundreds of reports on Wednesday morning from about 5am.

ANZ took to Facebook to let users know it was aware of the issue.

“Morning, we’re aware that some customers are currently experiencing issues with our goMoney app,” the bank wrote on its Facebook page.

“Our tech team is looking into this and we’ll update as soon as we know more . . . Very sorry for any inconvenience.”

ANZ said this month that its goMoney app had 1.1 million active users and had handled $78 billion in transactions since it launched in August 2010.

ANZ had advised customers to use Internet Banking or www.anz.com/mobilelanding on their mobile during the outage, however, some customers then posted that Internet banking didn't work either.

In other bank news today, St. George is trialling Google Glass compatibility. Google Glass finally became available to the public today.

UPDATE: The bank posted an update at around 2pm, writing "UPDATE: goMoney is starting to come back up now. It may be a bit slow at the start and if you’re still having issues in about an hour, please Private Message us with your mobile number. Appreciate your patience and sorry again for the inconvenience."

WEBINAR 7th May 11am - WOW 802.11

Learn how Ruckus Redefines High-Speed, High Capacity Wi-Fi with Industry’s First 802.11ac Wave 2 Access Point

THIS IS ONE NOT TO MISS SO REGISTER NOW

DON'T MISS OUT - REGISTER NOW!

FREE WHITEPAPER - RISKS OF MOVING DATABASES TO VMWARE

VMware changed the rules about the server resources required to keep a database responding

It's now more difficult for DBAs to see interaction between the database and server resources

This whitepaper highlights the key differences between performance management between physical and virtual servers, and maps out the five most common trouble spots when moving production databases to VMware

1. Innacurate metrics
2. Dynamic resource allocation
3. No control over Host Resources
4. Limited DBA visibility
5. Mutual ignorance

Don't move your database to VMware before learning about these potential risks, download this FREE Whitepaper now!

DOWNLOAD!

David Swan

David Swan is a tech journalist from Melbourne and is iTWire's Associate Editor. Having started off as a games reviewer at the age of 14, he now has a degree in Journalism from RMIT (with Honours) and owns basically every gadget under the sun.

Connect