All systems are operational

About This Site

Welcome to the Withings status page! To stay up to date with maintenance and incident notifications, please subscribe using the button at the bottom of the page. There is no need to re-subscribe if you already were on status.withings.com.

All times are CET/CEST.

Past Incidents

Saturday 19th June 2021

No incidents reported

Friday 18th June 2021

API Error - Date format

Calls to measure.getmeas through the Public API could lead to a 503 error if the date format was Y-m-d regarding startdate and enddate parameters. Incident has been fixed the 3rd of June 2021.

Thursday 17th June 2021

No incidents reported

Wednesday 16th June 2021

No incidents reported

Tuesday 15th June 2021

No incidents reported

Monday 14th June 2021

EU Services
High error rate on nights storage

Night storage are currently failing, the issue is identified and a fix is in progress

  • Timeline

    • The table managing our sleepscore overflowed an int32 signed integer foreign key column.
    • An ALTER was started but due to the size of the table we changed strategy and added a new column as BIGINT.
    • The Index on this table was then added.
    • Service was restored once an “ANALYZE” was performed on the table.
    • Backfill process was then started to fill the old values of the new column.

    Remediation Actions

    • Monitoring of near depleted int32 columns already exists on primary keys, but monitoring needs to be added on foreign keys.

  • Incident has been resolved

  • A fix has been implemented, we're now monitoring

    • Sunday 13th June 2021

    No incidents reported

    Saturday 12th June 2021

    No incidents reported

    Friday 11th June 2021

    No incidents reported

    Thursday 10th June 2021

    No incidents reported

    Wednesday 9th June 2021

    No incidents reported

    Tuesday 8th June 2021

    Website and Shop
    shop website unavailable

    CDN provider is undergoing partial downtime, which impact our main shop website

  • Timeline

    • 11:55 detection of issue
    • 12:05 change DNS to bypass CDN
    • 12:15 shop website back to normal for most users
    • 13:00 CDN provider back up

    What happened

    Our CDN provider experienced a widespread downtime, causing all requests to return 503 errors. DNS was then changed to bypass our CDN and received traffic directly, which fixed the issue once DNS was propagated.

  • incident resolved

  • A fix has been implemented and we are monitoring the results.

  • The issue has been identified and a fix is being implemented.

    • Monday 7th June 2021

    No incidents reported

    Sunday 6th June 2021

    No incidents reported