pingoru pingoru Runalyze had 19 outages in the last 2 years totaling 8172h 47m of downtime, averaging 0.8 incidents per month.
There were 19 Runalyze outages since July 2, 2025 totaling 8172h 47m of downtime. Each is summarised below. Incident details, duration, and resolution information.
We're currently aware of the issue and are investigating the cause. We will provide further updates as we have them.
We implemented a fix, which might have caused the issue. Activities are flowing in again. Monitoring the situation.
Operational
Our Weather Provider seems to have a problem. Forecasts are wrong!
It was fixed by our third party data provider
Operational
We are aware of the issue. One of our provider have some performance issues.
Problem seems to be resolved. The queue is being processed very fast.
Works
We found an issue where connections with Zepp expire so that we cannot get the data anymore. We are working on a fix. When you experience that issue please reconnect
Monitoring
Currently we are not aware of any issues.
All Polar online services are all down See https://status.polar.com/incidents/h4r2509080hq
Polar is back online since Jul 16, 2026 - 11:48 UTC
We're currently aware of the issue and are investigating the cause. We will provide further updates as we have them.
We had an outage between 0.54 and 3.45 - The monitoring system called us too late (we need to check why).
ok
A fix is on the way
Already fixed
We are aware that the login is currently limited - Fix is on the way and will be live in some minutes
Login is possible again
Deploy is done
Fit files coming automatically via the Garmin API to Runalyze are missing some data. This seems to be an issue on the Garmin API We are in contact with Garmin already. Current workround: Delete the activity within Runalyze, download the original (fit) activity from Garmin connect and upload it to Runalyze https://board.runalyze.com/d/143-garmin-fit-details-file/6
Garmin reverted that change. so the data comes in again
Activities may missing - working on a fix
Between 5pm (GMT+1) until 19.30 we had a problem receiving informations about new activities. Most of the activities will be synced within the next 30 minutes. When you are missing an activity please sync it manually
Monitoring
fixed
We had a slight overload on our database cluster in the night which resulted in a delay of activities this morning between 4 and 8.30
operational
In order for us to retrieve historical data (history import tool), you must activate the toggle at Garmin (also for existing connections) (https://connect.garmin.com/modern/settings/accountInformation).
Operational
Yes again, Cloudflare is down. We have not changed the infrastructure yet for an alternative way (Are in the process). We have not even bought new popcorn for these half-internet outage. Waiting to recover fully. Activities might be delayed or missing. Use the history import, when the global outage is over
Seems to be recovering
Operational
We're currently aware of the issue and are investigating the cause. We will provide further updates as we have them.
Currently regenerating all heatmaps for all "valid" users. This will take some hours
Reason was a technical upgrade. We fixed the problem.
If you still have a problem get in touch at [email protected] (Please mention your username).
fixed
Investigating
Misconfigured routing on a server
Fixed route, monitoring situation
done
Cloudflare was down between 14.30 and 15.40 (UTC+1). Currently waiting that all partner send us webhooks again
We receive events from Garmin again. There is still a delay in importing activities
done
Dear Runalyze user, We sincerely apologize for the multiple emails you may have received recently. Due to an unexpected technical issue, our system mistakenly sent several messages in a loop. The issue has been identified and resolved, and no further emails should be sent in error. We’re truly sorry for the inconvenience and appreciate your understanding. Thank you for your patience and continued support.
Fixed
We're currently aware of the issue and are investigating the cause. We will provide further updates as we have them.
Fixed
For a new feature some database changes are needed. They are done currently.
Fixed