It was the year 2000 we heard of Y2K bug. Now, this time it’s a another bug called “Twitpocalypse”, that going to crash some third-party Twitter services on 13 Jun 2009 at 09:46:42 AM GMT.


According to Twitpocalypse:

The Twitpocalypse is similar to the Y2K bug. Very soon the unique identifier associated to each tweet will exceed 2,147,483,647
For some of your favorite third-party Twitter services not designed to handle such a case, the sequence will suddenly turn into negative numbers. At this point, they are very likely to malfunction or crash.

So, the Twitpocalypse is a serious issue or hype? that we can’t figure it out right now being Twitter user. When I read the article, “The Twitpocalypse Is Coming! Is Twitterland Doomed?!?” at Mashable I got bit confused. But, the statement by Ben Parr of  Mashable,

we’re pretty sure that Twitter would have made some mention by now. Even if there was an issue, Twitter could probably fix it on their end.

clears the Twitpocalypse issue as hype! to some extent!

Lets see, what happens on 13 Jun 2009 at 09:46:42 AM GMT.