An amusing snip-it. On the day the banks are starting to appear before the economics committee, I noticed the APRA web site was down. Yes, the ADI regulator had disappeared! I wanted to grab some information for analysis I was running. Normal service was resumed just before 11:00 this morning.
Thinking it might be my end, I tried this. Nope, the site was down.
At 8:55am, local time it came back, then went again. At 9:34, we are getting an HTTP Error 503 from APRA. A quick lookup says of 503:
HTTP Error 503 – Service unavailable
Introduction
The Web server (running the Web site) is currently unable to handle the HTTP request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. Some servers in this state may also simply refuse the socket connection, in which case a different error may be generated because the socket creation timed out.
Fixing 503 errors
The Web server is effectively ‘closed for repair’. It is still functioning minimally because it can at least respond with a 503 status code, but full service is impossible i.e. the Web site is simply unavailable. There are a myriad possible reasons for this, but generally it is because of some human intervention by the operators of the Web server machine. You can usually expect that someone is working on the problem, and normal service will resume as soon as possible.
