swas blog

Twitter Developer is now down and while we have not heard back from Twitter yet, we are hoping that the fact that it abruptly went down is a sign they are now aware of the problem that has been affecting our ability to send out weather alerts. The problem is we were currently working there on the conversion so we have to wait till they boot it back up to continue. We are seriously hoping it is not a random unrelated outage. But we will update you as soon as we have them back up or we directly from Twitter Corporate offices.

Update 8:23 pm Twitter has just confirmed on Twitter status blog that Developer is down for maintenance. We would like to yell YIPPIE! right now, but as we have not heard back from them yet, we will restrain ourselves.

Update 11: 58 pm Ten obs feeds were fired and as of right now, none have posted on the correct account. They have however posted on one account:

Mt__Washington

If Twitter was fixing a problem with Developer, it wasn’t the problem we are experiencing. We have paused all feeds again, and will await word from Twitter.

• …Hermine expected to produce heavy rainfall over Southern Plains…
  Hermine is expected to produce total rainfall accumulations of 4 to 8 inches, with possible isolated maximum amounts of 10 inches from the middle Texas coast northward through central Texas and over central and eastern Oklahoma. These rains are expected to spread across southeastern Kansas, northwestern Arkansas, and Missouri during the next few days and could cause life-threatening flash floods.

As of 11:30 pm Monday night we have paused all feed testing. We opened up the other half of the eastern seaboard and it appears as though every single feed was blasted into the Boston Account. Twitter has been notified already of the earlier problems and we have just updated them regarding the Boston feed party that just occurred. We will update you as soon as we hear back from Twitter.

We have already started rolling about half of the observations from the eastern seaboard and have already been able to confirm that the missing feeds as well as the feeds being sent to the wrong accounts are not as a result of our servers malfunctioning. We have notified Twitter of the additional information and will post anything here when we hear back from them. We are still on track to complete the OAUTH conversion inside of the 2 week period we initially provided as an estimate, but until Twitter has a fix on their end for these issues we cannot really estimate how much longer it will take to restore all feeds. In fact additional time may be required because of the heavy monitoring we must do to assure that any new issues do not pop out at us.

As we mentioned 2 days ago we are working from the east back the west, trying to provide coverage in case the east has to deal with any additional hurricanes. We are moving as fast as humanly possible, but now, we are not just relying on our own team, we are relying on Twitter’s team too and we are quite sure they have many pressing issues inn addition to the ones we have reported. As we mentioned earlier today, please do not rely on the feeds until we post an all clear on this blog. Thanks for your support and patience.