Our database cluster is currently experiencing problems. We are working on fixing the issue.
Update: Runalyze should recover at eta ~11:15
Final Update and report:
Due to a server outage at our service provider, Runalyze was unavailable from about 9:15 am to 2 (CET) pm on Monday 01/18/2021. The outage affected our database server, so none of our services worked as usual. Unfortunately, the recovery takes a bit longer than initially announced. The database was damaged by the outage in such a way that we had to import our last complete database backup from 2 o'clock (CET). Repairing the defective entries, on the other hand, would have cost us much more time.
Changes made between 2am and 9:15am were unfortunately lost in the process. You have to repeat the changes manually. Likewise, you may have to manually re-upload activities that were imported into Runalyze via automatic synchronization during this time. Activities that were still in the queue should now be processed one by one. If in doubt, please manually upload your current activity to Runalyze.
Also, there may be issues with API connections in some circumstances. If an automatic synchronization of new data (i.e. after 2pm on Monday) does not work, please reconnect to the corresponding API once. Unfortunately, we cannot check individual cases here.
We apologize for the outage and the resulting missing data. We are working hard to ensure that such outages do not occur and that, in case of doubt, no data is lost and Runalyze is quickly available again. We will analyze the incident in more detail later and adjust our infrastructure accordingly.