But once again the CFA feed for the fire locations IS NOT WORKING. The DSE Site IS working, with the same information, but if you live in Epping, Victoria, why would you check the DSE site? - When the CFA is your fire brigade?
This is not the first time and I doubt will be the last. If it is a planned outage, then notice should be posted on the site, on the relevant page.
I was informed at 19.36hrs EST, that the website has currently been down for 20 hours. It is now 20.42hrs EST and there is no notice on the site, nor has the site come back up.
If this was to happen mid-summer, I'm sure there would be an uproar, but since it's winter and little threat is posed, who cares?
I hate to say it but I care - my reasons for caring are that a site that can't work properly in winter, what hope have we got in summer when the threat is real and not imagined?
The people who run the technical side of things for the CFA need to fix this urgently as I have been blogging about every outage that I am made aware of.
Here the major outages that I am aware of and have been able to prove.
Dec 2009 - Outage #1
Dec 2009 - Reason for Outage
Dec 2009 - Outage #2
Jan 2010 - Outage #3
Jan 2010 - Outage #4
Jan 2010 - Outage #5
Feb 2010 - Outage #6
At the risk of repeating myself:-
"We must make our voices heard over the politics, over the government protectionism of public liability, we need multiple sources of information and not information that is hidden from all except a few who understand how these things work.
“Emergency Services Minister Bob Cameron says people should never rely only on the CFA website."
So tell me Mr Cameron – what do we rely on? Or do we leave our house, our business or animals to the hand of God?
Victorians have a right to know - not be kept in the dark like mushrooms. We have a right to defend if capable/able"
**It is now 7.23hrs EST 31.05.10 and the CFA website is still down, making a total of 32 hours that the CFA has been down for so far. This is not acceptable
** The site finally came back up again at 10.05hrs EST 31.05.10 - making a total of 35 hours down time