A third party library we were using used some old invalid urls to request tokens. This has been fixed. If you have problems with the Withings connection please disconnect and reconnect.

Read more in our help article or start by generating your own token in your account.

Our API got an bulk endpoint for health metrics.

Our "PrivacyGuard" had a bug which caused the graphs/raw data to be missing for some activities. If you are affected by such an activity, you have to import this activity again.

We have extended our API for our partners.

Two months ago we started respecting the 'main' privacy settings from your dataset. Now, almost all privacy settings are respected. For example, if you set your average heart rate to private, the heart rate data series for other people will also be hidden.

VAM is the average ascent speed in meters per hour, calculated based on all classified climbs in Runalyze. This value is now available for all upcoming activities (with at least one classified climb).

You can now set all your activities public or private with one click from your privacy settings.

The activity view now includes a plot for flight time (assuming cadence and ground contact time are available).

Our ANOVA tool can now group values additionally by month (and year), weekday and daytime.

We have upgraded several internal dependencies of Runalyze.

Due to a bug no weight or rest heart rate data was received. This should work again for future entries.

Runalyze can automatically calculate power for running and cycling activities. Previously, this was always done when no recorded data was available. From now on you can choose for each sport whether Runalyze should calculate power always, never or only when empty.

Runalyze now has same settings for limiting Polar Sync as for Garmin Sync. Still, sleep sync is not yet available for Polar due to problems on Polar's side

As some users have requested we have now created a setting to restrict the Garmin synchronization.

Select whether you want to have the resting heart rate, sleep data and/or body composition automatically synchronized. Default remains "yes"

In rare cases an invalid connection to these services resulted in problems disconnecting those accounts. This has been fixed.

You can now set your locale dependent date, time and number format in your account settings.

Garmin beat us to it a few days ago, but this feature has also been on our wish list for a long time. Now it’s done and you can also colorize all your tracks by speed in Runalyze. So you can see directly on which sections you were especially fast or slow.

Read more at our blog.

Some activities were assigned to the wrong day within the poster tool.

Gradients above 40% (or below -40%) were incorrectly evaluated when calculating the Grade Adjusted Pace.

We have updated our device list and are now able to detect a lot of new devices and vendors.

Synchronization of health data from Withings is now enabled for Runalyze Supporters.

The Garmin history import can now be used again without any limitation by Garmin. Requesting more than 1000 days of history is possible again.

Body composition, sleep data and resting heart rate are now available for syncing too. Duplicates can occur for health data if entries already exist for requested time period.

The recovery heart rate (2 minutes after stopping) had been available as dataset value and is now shown in the activity view as well.

Relative TRIMP is simply TRIMP per hour. It can be used as an intensity metric, similar to average heart rate, but taking into account the changing workloads during the activity.

The 'main' privacy settings from your dataset are now respected for your shared activities (daytime, title, notes, route name, training partners, tags and equipment). You may want to set those fields to private in your dataset settings.

Resting heart rate and weight should now also be automatically synchronized from Polar to Runalyze. Sleep data cannot yet be synchronized due to a problem with Polar.

Due to a misunderstanding of sleep and resting heart rate synchronization with Garmin, there were many duplicates. A fix was applied. Most duplicates for Resting Heart Rate and sleeps have been removed.

All kind of health data like weight, sleep, mental state, blood pressure, maxium heart rate and resting heart rate have their own tables now where you can edit and delete all entries.

The Garmin history import is available again. But as we are limited temporarily by Garmin with 1000 days/minute the tool maybe shows an information that you need to wait a minute.

Weight and sleep data is now synced automatically from Garmin to Runalyze. Resting heart rate should be synced automatically too.

New health section: We have migrated all data to the new health section.

A blog post with all changes will be available in the end of the next week.

Mood, fatigue and stress can have quite an impact on everyday training. Both positive and negative. Looking at these values over a longer period of time is therefore not only important for training, but also to be able to counteract in everyday life if the fatigue and stress continues for too long.

You can track your blood pressure. Automatic sync with e.g. Withings is in work

We will explain to you in detail what the values mean in detail soon. But you can already find the values for all future (!) activities in the activity view, in the dataset (must be activated) and in the usual tools (trend analysis, ANOVA, sorting by search). - And you can find a short info about the values in our glossary.

We know that you would like to see the values for all past activities - so would we. But this requires the re-processing of many millions of activities. We have this on our radar and will let you know as soon as this is possible or available.

We have rebuilt, updated and extended our database infrastructure.

After a long time in beta status, the Grade Adjusted Pace (GAP) is finally here. We have made some adjustments to the calculation parameters and from now on we will show you the GAP for the running activities, for single laps and for climbs.

We have added the total distance to the shown streak (statistics 'plugin' below calendar view).

The full equipment table has a new column for the last use of each object.

Climbs are now available in the activity view. In addition, you can activate the number of climbs (and their categories) in your dataset for the calendar view.

Some weather conditions were wrongly assigned for data of the service provider darksky with us.

From now on you can view the progress chart for the different sports and time periods on Runalyze.

Compare your distance, duration, ascending altitude, TRIMP or number of activities in the current period (year/month/week) with a previous one (up to the beginning of last year at the most), and keep track of where you will end up.

Runalyze does now import and store all developer fields from FIT files. Read more at our blog.

Due to a bug in the new account setup guide we had to reset the privacy settings for all users in the sports to private. If you want to have the activities automatically set to public when importing, you have to reconfigure that setting for each sport.

Athletes can now easily set up their account to provide all the data necessary for specific calculations. Read more at our blog.

There was a bug resulting in wrong best sub segments for power data in case of non-equidistant data. This behavior has been fixed.

Multisport sessions (e.g. Triathlon) with short transitions (less than one minute) led to false duplicates.

The sports panel did ignore the user's time zone when showing e.g. current week.

Our two new views for the current marathon shape and for the running performance status are now available for all users. Read more on marathon shape view and running performance status at our blog.

Plot tooltips in activity view did not respect imperial units.

It is now possible to recalculate TRIMP, VO2max and altitude for an individual activity.

You can now take over your complete history via Decathlon sync.

We have added support for incline data from Runn™ Smart Treadmill Sensor from North Pole Engineering.

For users with supporter status there are two new views for the current marathon shape and for the running performance status. We explain the new Marathon Shape View in detail on our blog and an article on the running performance status view will follow. After a few weeks those features will be freely available for every user.

We have internally refactored the activity view (to get rid of some legacy code) and added a few improvements. Heart rate and pace zone tables as well as computed laps do now show average power and power zone table does now show average pace.

The Google login did not work for everyone lately. We have fixed the issue by updating a third-party library.

Direct synchronization with Decathlon & Domyos E-Connected is now possible. Read more at our blog.

We have added various new entries in our glossary for running dynamics (cadence, stride length, ground contact time/balance, vertical oscillation/ratio, flight time/ratio).

Average power was added to the Climb Score view. You can switch between pace and power now.

To be able to invest more time in RUNALYZE in the long term, we are now launching a subscription model. You can become a RUNALYZE supporter. Read more at our blog.

In view of the current situation and numerous cancelled events, we have organised a virtual Easter run. Read more at our blog.

Read more at our blog.

Polar sync now uses *.fit-files by default. The option to switch formats has been removed.

The user can switch between "Never correct", "Only if device has no barometer" or "Always". The new option "Always" is intended for cases when the barometer of a device is broken or provides useless data.

If a device that has a barometer is detected during import, no automatic altitude correction is performed, even if it is activated in the configuration. Barometric altitude data is usually much more accurate than data corrected by satellite data. A manual correction is still possible afterwards.

Elevation data from a device with a barometer was erroneously stored as 'corrected' data. Affected are activities between 13 and 17 March. In this case the data was not corrected, only the displayed message is incorrect.

Due to some recurring questions, we have added new glossary entries for rest days and calculated power.

When importing fit files, the device is now automatically detected in almost all cases.

Sometimes Suunto only informs us with a significant time delay if a new activity is available. If in doubt, you can now directly trigger a sync of individual activities.

In rare cases an invalid vo2max correction factor was calculated.

After a recent change the generation of the images did not work anymore.

We have added the swim metrics total strokes and SWOLF to our anova and trend analysis tools.

The link to delete the account in the account settings was temporarily not available.

We have limited the maximum number of zones you can set per metric (heart rate, pace, power) to 20.

Instead of a single value (to reach TSB = 0) 'Easy TRIMP' now shows a range to keep an optimal workload ratio of 0.8 < A:C < 1.3.

The anova tool wasn't available after our latest internal framework update.

We have updated the framework we use internally.

The levels we have shown so far for Running Effectiveness are only valid for data coming from Stryd. Running Effectiveness based on calculated power data (as done by us via GOVSS) do not have a high information content.

Power values have not been calculated if the imported file contained only zeros. This behavior has been fixed now.

Due to another uncommunicated change on Polar's side our history import for your Polar data did not work correctly.

You now have the option to use the gravatar as profile image (shown in the upper right corner of the dashboard and your public athlete page).

The Race Performance Chart has a new option to use the date as x-axis.

The elevation data from Mapzen has been set as the default elevation service. The service uses the terrain tiles dataset from AWS' open data registry.

Backups were not working since 4th December. This has been fixed now.

Runtastic's official backup does include gpx files with heart rate and altimeter information from now on. The converter is not required anymore and has been disabled.

Ascent and descent can now be edited and can be entered for activities without elevation profile. So far, most sections used only a single elevation value (which was the maximum of ascent/descent). From now on, a single elevation value always shows the ascent.

xPower is a weighted average of your power output and serves as an alternative stress metric.

Read more in our glossary.

From now on the developer field "description" Suunto uses in FIT files is mapped to our description field in RUNALYZE.

Invalid power values (e.g. negative values) are now ignored when parsing a file. We discovered some tcx files that failed while importing because of those invalid values.

Exported activities (e.g. as tcx file) will now contain the correct laps instead of default 1k auto-lap.

The Acute:Chronic workload ratio (ACWR), which is simply the ratio of ATL and CTL, is now shown in the calculations panel. It can be used to determine injury risk.

Read more in our glossary.

You can now also subscribe to the changelog as an RSS feed.

Until now, poincaré plots of hrv data always displayed only one (the last) y-value for an x-value. This behavior has now been fixed.

From now on the estimated vo2max by Suunto is mapped to our internal "estimated vo2max field" from fit files. You can activate this value in your dataset.

We have fixed a configuration that resulted in slower page calls.

The "remember me" functionality has not worked correctly since our recent redesign. This bug has now been fixed so that users can stay logged in for a longer period of time.

The time zone detection, based on the activity's coordinates, was broken for some time. During that time, we only used the user's default time zone which may be incorrect in case of e.g. vacations.

The start location is now automatically added to the "Route" field if the activity contains gps coordinates.

We have redesigned the publicly accessible pages such as the landing page, login and registration or our glossary and help pages.

For all running and cycling activities for which no recorded power is available, power is automatically calculated. This calculation is now correctly performed (or removed) even if the sport is changed later and updated if the elevation profile is changed (by elevation correction or removing a data series).

When syncing Suunto activities there were problems with the laps. We only support flat laps. This if fixed for all future activities.

Missing altitude values were wrongly imported as "0", which leads to different problems. These values are now imported correctly as unknown.

Illegally high speeds (e.g. due to errors in data recording) may have led to negative power values. This behavior is now suppressed.

Help articles will be automatically translated into German, French, Spanish, Portuguese, Dutch, Italian, Polish or Russian if we have not translated them yet manually.

Air Power data streams by Stryd will be imported for all upcoming activities. Still, we don't show the data in the activity view yet.

From now on we are storing all uploaded fit files. You can download them from every individual activity.

In the sports configuration, the individual equipment categories of a sport can now be viewed, assigned and removed.

The automatic estimation of power data, if no recorded data is available, was previously only available for cycling. We now have such an estimate for running activities as well.

Read more in our blog post Running Power for everyone.

Mobile browsers like Safari do not support the list of supported file extensions. We added a temporary workaround until all mobile browsers fix that issue.

We work on RUNALYZE day in and day out. To give you a better idea of all the changes, bugfixes and new features we're releasing, we've added a public changelog.

The calculation of the paces in the section "Training paces" contained a small error. Speeds below 100% were a bit too fast, above 100% a bit too slow.

Problem was caused by swimming heart rate, which is at the end of the file but belongs to the second session.

Tracked pauses must cause elevation calculation to split trackdata into different segments and add ascent/descent values of all segments separately to total ascent/descent.

As a preparation for scaling the activity import, activities from history import, API import and normal sync now end up in the same queue.

We are evaluating new data sources for elevation data and added Mapzen as a new elevation service. The service uses the terrain tiles dataset from AWS' open data registry.

Activity titles (as provided in some file types) will be used to guess the user's correct sport type.

Runtastic has decided to discontinue its web platform. Downloading all your data from Runtastic is easy, but the data is stored in a non-usual format. We made a converter written by Glenn Reyes available to let you get your activity files in a standard gpx format. You can find our converter at runalyze.com/runtastic-converter.

We have updated the framework we use internally by some versions.

Garmin's new API provides information about the file type. Unfortunately, for older activities, this is always mistakenly FIT, whether or not the file type is actually GPX. Garmin knows the bug but will not fix it. We now check the file content so that the import works accordingly.

The outdated Garmin api has been removed. Users that have not switched to the new api will not have any activities synchronized until they have connected to the new api.

Power by Garmin Connect IQ app Running Power Estimator does not use the standard power field to store power data. This is now mapped to the power field in Runalyze.

We are now able to provide a full history import (except third party activities and manual activities) from Garmin.

We have introduced a new Help and Support section at runalyze.com/help trying to answer the most frequent questions.