SAA CEO responds to FlySAA downtime

Hours?

We're a small company and even we monitor our websites constantly - and automatically - with notifications via email and SMS when they go down.

I bet a member of the public had to notify them...

Joke.
 
Se voet...

If nobody in their IT dept knew that flysaa.com was expiring then they should all be fired for being useless and incompetent.

Network Solutions would have notified them that the domain was up for renewal AGES ago... some useless twit in SAA's IT dept probably just deleted the email.
 
Se voet...

If nobody in their IT dept knew that flysaa.com was expiring then they should all be fired for being useless and incompetent.

Network Solutions would have notified them that the domain was up for renewal AGES ago... some useless twit in SAA's IT dept probably just deleted the email.

Or flagged it as spam and forget about it :D
 
I would hardly call Network Solutions an incompetent service provider....

They have some "shady" business practices, yes, but they're not incompetent in the slightest.
 
“The problem was a direct result of service providers not meeting their obligations and SAA will be taking further action in this regard.” commented Smyth via the now functional FlySAA website.

BUT

“Unfortunately SAA did not receive any pre-warning of the pending issue but within hours of the problem being identified, the SAA IT personnel were able to address the problem ensuring minimal disruptions to our customers.” he continued.

Wait, what? :confused:

Your own IT personnel was able to rectify the issue? Then why didn't any of your IT personnel pick up the expiration warning then?

@TB - it all depends on whether their IT department also managed the domain registration etc.
 
Se voet...

If nobody in their IT dept knew that flysaa.com was expiring then they should all be fired for being useless and incompetent.

Network Solutions would have notified them that the domain was up for renewal AGES ago... some useless twit in SAA's IT dept probably just deleted the email.

and also SAA should fire their outsourced IT provider for not alerting them or paying it themselves, which makes sense as they manage the domain for the client, and invoicing them... WHOIS.
 
Yep!:rolleyes: teh interwebs works in mysterious ways...

Yes, it does. Like for instance, how DNS servers at different ISP's cache results for name lookups for a period of time after they request them from the authoritative servers. Which means that, if the DNS changes at 00:00, and the TimeToLive is specified at 12 hours, and the DNS is then restored at 04:00, a user at an ISP who queried the site at 03:59 would still be seeing cached results at 15:59, while another user of a different ISP who queried the site at 04:01 would already see the restored site.

Yes, the intarwebs DO work in mysterious ways . . .
 
Since it was name server changing it explains why the downtime was so long. DNS servers in South Africa takes ages to propegate compared to google public DNS which only take a few seconds.
 
Me thinks accounting sat on the bill :D I've yet to see an IT department not willing to spend money to kep things running.
 
CEO playing the blame game on the service provider. Hope we will get a reply from the service provider...
 
Chances are some underpaid , overworked IT admin dude received the email 6 months ago...unfortunately he left the company and no one noticed.
 
Top
Sign up to the MyBroadband newsletter
X