We'd like to keep Spreaker up 100% of the time. When that doesn't happen, we write about it here.
|Website||So far so good|
|Api||So far so good|
|Streaming||So far so good|
|Mobile apps||So far so good|
Spreaker website and API have been unreachable for 40 minutes, from 22:19 UTC to 22:58 UTC, due to networking issues in Amazon EU-west-1 datacenter where we currently run most of our servers.
As soon as the issue occurred, we immediately started to migrate all affected servers to new ones, in order to quickly recover the service.
At the time of writing, Amazon is still investigating the issue (see screenshot below), but all remaining Spreaker servers currently look unaffected.
We’re really sorry for the trouble.
Spreaker web site and API are now online. We’re still checking all services, then we’ll start investigate the issue and will post more details.
The failure affected more servers then initially detected. We’re working to bring everything back asap.
We’ve detected an issue on one of our primary databases and Spreaker is currently unavailable. We’re working to bring it back asap.
Tonight we had an issue on our Tube server tube.us-east.spreaker.com - due to an high load the server exhausted all the memory and the Tube service in us-east region failed intermittently. We’ve worked to bring it back as soon as possible, and now the service is running normally.
We’re really sorry for that and we’ll work to make more robust and avoid such issues in the future. To be totally transparent with you, let me outline some actions we’ll take:
The Spreaker Chat service has been unavailable for about 3 hours. We had a severe issue in the datacenter where the chat is running and we’ve worked hard to bring it back as soon as possible. We’ve immediately migrated the servers to another provider and the chat service is now working again.
We’re really sorry for the service disruption.