Those users with the ability to send messages via the API directly to a users screen name are currently receiving a 500 error back from the IMified API. We have identified a fix for this issue and it will be deployed later this evening. Will update this post when this issue is resolved.
Update 2/18 8:40am: Last night’s update has been moved to this AM
Update 2/18 8:50am: This issue should now be resolved
We’re currently investigating a problem resulting in a number of bot being offline. We should have this issue resolved shortly. SMS and twitter bots are working without issue.
We’ll be performing maintenance on our core IM servers tonight at midnight EST. IM bots will be offline briefly while we install updates to the IMified software.
We’re investigating an issue where some IM bots are responding slowly, failing to respond, or not appearing as online to all users. We’re currently working on the problem and may need to restart IM bots in order to recover. An update will be provided when we know more.
We’re making some configuration changes to our core IM servers tonight at midnight EST that require a restart. You will see your IM bots disconnnect and then reconnect when the IM servers are restarted.
Update: This has been postponed to Jan 22, Midnight EST.
The maintenance has been completed.
Beginning with Twitters 90 minute outage this morning, Twitter’s API has been returning a large number of errors and unexpected data. This means that Twitter bots are not responding to many requests as we are unable to consistently post to Twitter.
We’re working on two significant issues at the moment.
Messages to large numbers of bots are failing to reach developer endpoints, resulting in non-responses to incoming messages.
The second issue is communications problems with Google Talk. This is resulting in the inability to have a gmail address act as a bot and is preventing S2S connections from users using Google Talk addresses to speak to bots with a bot.im address.
We’ll provide an update when these issues are resolved.
Update: Twitter and SMS are both working normally. Only Instant Messaging bots are affected.
Update 11:30PST: IM bots are beginning to recover. You may notice your bot appears offline for a brief period as all the bots come back around.
Update 12:15 PST: All bots are now fully recovered.
We’re currently experiencing an issue with IM screen names appearing offline. We should have this issue resolved shortly. SMS and twitter bots are working without issue.
Right now we’re experiencing a significantly elevated rate of errors on the platform. Some users are reporting they are unable to add or remove bots, and some bot connections on some networks are appearing offline or not responding to messages.
We’re aware of the issue and are working on a fix.
Update 10:20am EST
Bots are currently coming back online. It may take up to 30 minutes for all bots to appear online.
Update 10:45am EST
All bots are currently online
We noticed some issues in creating new bots, followed by some server errors on our end. The process of solving the issue caused all bots to drop offline. They are reconnecting now. If you created a new bot or added a new network in the last hour and it is not coming online, please delete it and recreate it.
Status
