Get short, timely messages from fruux_status.

Twitter is a rich source of instantly updated information. It's easy to stay updated on an incredibly wide variety of topics. Join today and follow @fruux_status.

Get updates via SMS by texting follow fruux_status to 40404 in the United States
Codes for other countries

Two-way (sending and receiving) short codes:
Country Code For customers of
Australia
  • 0198089488 Telstra
Canada
  • 21212 (any)
United Kingdom
  • 86444 Vodafone, Orange, 3, O2
Indonesia
  • 89887 AXIS, 3, Telkomsel
Ireland
  • 51210 O2
India
  • 53000 Bharti Airtel, Videocon
Jordan
  • 90903 Zain
New Zealand
  • 8987 Vodafone, Telecom NZ
United States
  • 40404 (any)

fruux_status

  1. We're up and running again!
  2. Syncing is currently disabled while we are deploying optimizations in the cloud.
  3. We're up and running again!
  4. The issue was resolved at #AWS
  5. The busy bees over at #AWS just identified the issue and dispatched engineers. They are now working on the problem.
  6. We've switched to maintenance mode, while investigating an issue over at #AWS
  7. Syncing is currently disabled while we are deploying optimizations in the cloud.
  8. We're up and running again!
  9. Syncing is currently disabled while we are deploying optimizations in the cloud.
  10. We're up and running again!
  11. Syncing is currently disabled while we are deploying optimizations in the cloud.
  12. Up and running again! We'd point our fingers at the @awscloud folks, but we wouldn't have such a great uptime (besides this glitch) w/o them
  13. The folks over at @awscloud expect the restoration process to continue over the next several hours and will update as they have new info.
  14. The hard working bees over at @awscloud estimate that it will take another 3-4 hours until full access is restored.
  15. We're still experiencing downtime due to an issue at @awscloud - @AmazonRDS is currently unavailable. Hope they'll fix it soon.
  16. Service disruption at #AWS: status.aws.amazon.com - You might experience delayed or dropped syncs. They are working on it.
  17. Our service currently suffers from occasional uptime issues (blog.fruux.com/occasional-upt…). We're working on the problem.
  18. The service is now operating normally.
  19. We are currently investigating increased latencies and error rates affecting some sync sessions.
  20. Only a few seconds later: Up and running again. :-)