Pages in the ‘outage’ Category

The SuperTweet App has been suspended by Twitter

Jan 24, 2014 by supertweetnews

For the moment, perhaps permanently, the Supertweet Proxy has been suspended by Twitter.

We'll let you know when we have more details to provide.

DOS Attacks on SuperTweet API

Feb 12, 2013 by supertweetnews

Not absolutely sure if these are intentionally malicious or just a swarm of new users with lots of bugs in their code (I suspect it is intentional attacks on SuperTweet).

Either way, the end result is that the service has been affected and may continue to be. I really don't have time for this people. The SuperTweet API is a service that we run for the community OUT OF OUR POCKETS to help people. But if this keeps up, we will have to shut it down.

Twitter was down for about an hour today

Jun 21, 2012 by supertweetnews

It hasn't happened in a long time, an apparent total service outage of Twitter. These were a pretty common occurrence in the early days, circa 2007, but Twitter has been much more robust for quite a while, where outages are usually isolated to some sub-set of users/features and they don't take the whole service down.

I feel for the engineers and operations staff that have to deal with these problems. I've been there. It's not fun. Very few of us have ever had to deal with the volumes Twitter is dealing with. It's not the same as running your own little Apache PHP server, folks. Anyway, the service appears to be coming back on-line again now and the API right along with it.

One thing we discovered with this outage, is that SuperTweet is currently totally dependent on Twitter, even to provide outage information and status information on Twitter itself (including this Blog which is integrated with Twitter). Oh well, that's probably something we will just live with for now, unless these kinds of total Twitter outages become more frequent.

Approximate time of outage:

started around 9:15am Pacific time (16:15 GMT)

ended around 10:15am Pacific time (17:15 GMT) outage report

Sep 17, 2011 by supertweetnews

We had a partial outage of the API service and a full outage of the main site (for logging in and setting up new accounts).  The root cause of the outage was immediately resolved and the service restored as soon as we realized was down.

Unfortunately, our notification systems failed, and so none of our (all volunteer) admins were notified of the outage for several hours. We are looking into why all of the notification systems failed and we have added two additional notification systems as backups to hopefully prevent another issue of this type in the future.

We apologize for any inconvenience this outage may have caused. Induced Outage Post-mortem

Jul 20, 2010 by supertweetnews

When we get more details we will add, but here is a short report on what happened to today.

Some time earlier today, the all the DNS servers at went belly up.  This affected many domains, thousands, perhaps even millions around the net. is not the host for service, but was the DNS host for the domain.  That was a mistake and we apologize for not correcting this setup earlier. Generally, I move DNS service for any domains I care about to a more reliable infrastructure, where we have complete control. We hadn't got around to that for the domain and it was still running off the default but historically unreliable DNS at

While is still down as I write this, and countless domains registered through them are still down, we found a backdoor that allowed us tocorrect the the DNS, repointing it to our reliable DNS hosting - so such a failure can never impact again. domains have been down for hours, all over the net. I suspect this will have a huge fallout for - I know I've about had it with them and will look to move my many domains off to someone else. If anyone has suggestions for good registrars, let me know - I mean the main reason we still use is the "devil-you-know" and I don't want to move to some other provider that is even worse.

So in short, is back up and we're sorry for the outage that, while not the fault of the servers or network, it was a result of our failure to setup DNS for on a proper infrastructure.

Update: Actual outage appears to have been roughly 90 minutes - going offline for most people around 6:30am pacific time and coming back online (after moving DNS off at about 8am. It took a little while to figure out what was wrong and then a little while longer to find the backdoor that allowed us in to switch the DNS over.