Archive

Archive for February, 2010

Unexpected downtime Feb. 28th

February 28th, 2010 No comments

The host this service is running on hasn’t been reachable since around 4pm today. The hoster has been informed and we hope it will be available again soon. Thanks again for your patience.

Update: The machine is back up. The service wasn’t reachable for around two hours. According to our hoster it was caused by a power outage.

Categories: Downtimes

Hello Spectrum

February 22nd, 2010 No comments

For some time now Spectrum made itself a name for being a fast and reliable transport between XMPP and “legacy networks”. After moving from ejabberd to Prosody XMPP-wise, switching away from the python based transport has been a task on our to-do list for far too long.

The most visible differences for end-users will be another domain being used and more choice in regard to supported protocols. Namely aim gg icq irc msn qq simple xmpp and yahoo. The current transports located at “im.thiessen.it” will be available under “thiessen.im” along with the new ones in the future. The necessary changes in your roster are being done automatically and should not result in more than a short disconnect.

Update: The migration has been completed successfully. In some cases users may ended up with the wrong encoding for their country. If you should experience problems please contact us in support@rooms.thiessen.im (webchat).

Update 2: We currently experience a problem where the transport suddenly stops reacting. Spectrum’s development team has been informed and we expect a fix by the end of the week. If you notice connection problems, please use the chatroom mentioned above to let us know.

Categories: Features, Transports

Unexpected downtime Feb. 19th at 3am

February 19th, 2010 No comments

Last night we experienced an unexpected crash of Prosody. The service wasn’t available for about two hours from 3am. Unfortunately the Prosody team couldn’t find the cause yet which is why we are going to restart the deamon in debug mode tonight. That will hopefully give us more information in case it happens again. The expected downtime is less than a minute.

Update: The issue has been identified and a fix is being worked on.

Categories: Downtimes