Problems with new account creation / API: 2012-02-09 09:15 CET

Update 11:25 CET:
Problem has been resolved.

Update 10:35 CET:
Reason for downtime is a power failure due to malfunction. Redundant standby current immediately kicked in, but was not distributed evenly to all circuits as should have happened. They are currently working on fixing that issue. We will keep you updated.

Some of our Wuala services (new Account creation, Web API) are offline due to networking problems at one of our sites. Our hosting partner is currently working on resolving the issue.
Wuala-Team

Metadata saving problem

Update 11:15 CET:
Issue has been resolved

Due to an HW-issue with one of our core servers that handles new meta data storage in Wuala, a small number of users may be unable to currently save/update metadata information on files stored in Wuala. We will keep you updated, as soon as the service is back online again.

Connection Problems

2011-16-12 14:00: Our hosting partner is having connection problems that affects part of our online system. We are currently investigating this error.

Update 15:00: Issue has been resolved.

Web Download Problems

From roughly 3:30 to 6:30, downloading shared files from the web site did not work properly any more. These downloads still worked using the Wuala client.

Small file access problem

Starting at 16:00 CEST, some users may experience difficulties to download/upload small files (up to 300kb) from/to Wuala. The root cause has been identified and we are working to resolve the issue.

Update 16:20 CEST: Service is up again

Network Problems

2011-10-23, 11:05: Due to a partial power outage in one of our data centers, Wuala may currently have problems when uploading or downloading files.

12:00: All download problems could be resolved. For about 10% of all small files (<300kB), Wuala remains in read-only mode.

Update 20:55 CEST: Wuala is fully operational and the read-only mode disabled again.

Connection Problems

Our hosting partner is having connection problems that affects part of our online system. We are currently investigating this error.

Update 16:55 CEST:
Issue resolved