Luscii - Notice history

Luscii Android App experiencing degraded performance

Luscii Web App - Operational

100% - uptime
Jul 2026 · 100.0%Aug · 100.0%Sep · 100.0%
Jul 2026
Aug 2026
Sep 2026

Luscii Android App - Degraded performance

100% - uptime
Jul 2026 · 100.0%Aug · 100.0%Sep · 100.0%
Jul 2026
Aug 2026
Sep 2026

Luscii iOS App - Operational

100% - uptime
Jul 2026 · 100.0%Aug · 100.0%Sep · 100.0%
Jul 2026
Aug 2026
Sep 2026

Luscii Integrations - Operational

100% - uptime
Jul 2026 · 100.0%Aug · 100.0%Sep · 100.0%
Jul 2026
Aug 2026
Sep 2026

Luscii Metabase - Operational

Customer portal - Operational

48% - uptime
Jul 2026 · 1.03%Aug · 43.97%Sep · 100.0%
Jul 2026
Aug 2026
Sep 2026

Notice history

Aug 2026

No notices reported this month

Jul 2026

Priority 3: PPG report occasionally not visible for Happitech measurement
  • Resolved
    UTC
    Resolved

    Update:

    The issue has been resolved. If the Happitech software is unable to generate the report, the measurement is no longer saved and the app asks the patient to repeat the measurement (same as on iPhones). This way, no measurements without a report end up in the Luscii patient record.

    The fix is included in the latest app version: Android 5.75.0. iPhones were not affected.

    Resolving the incidental failure to generate the report sits with Happitech, in their own software. We have informed them and are following up. Thank you for your patience.

  • Identified
    UTC
    Identified

    We have identified the cause. The report is delivered by our measurement partner Happitech and in incidental cases it is not included. This affects a very small share of all Happitech measurements.

    On iPhones this is already handled well: if the report is not delivered, the measurement is not saved and the patient can simply take a new measurement straight away. So a measurement without its report never ends up in the patient record. On Android devices, in those incidental cases, the measurement is correctly saved but without the report, which is exactly what we have seen.

    We are therefore aligning Android with iOS: if the report is missing, the measurement is not saved and the patient simply takes a new measurement. That way, a saved measurement is always complete. We will let you know once that change has been rolled out.

    In addition, the structural fix sits with Happitech: they need to resolve this in their own software. We have raised this with them as urgent and are actively following up.

  • Investigating
    UTC
    Investigating

    Complication:
    In rare cases, the report accompanying a Happitech measurement is not shown. This affects a small number of measurements: the measurement itself is received correctly and alerts continue to work as normal. For organisations that (partly) base care on the report, this means they cannot fully assess what happened during the measurement in those isolated cases.

    Next steps:
    Because the report is important to some organisations in their care delivery, we have raised the priority. We are investigating (with Happitech) in which situations the report is missing. We will keep you posted as soon as we know more.

Priority 2: Recording of measurements for patients enrolled in multiple programmes
  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Monitoring
    UTC
    Monitoring

    Update:

    Our investigation has shown that what initially appeared to be a single problem in fact had two separate causes. Both occur only in the Android app and only for patients enrolled in more than one programme at the same time; neither occurs on iPhone.

    Importantly, no data has been lost. Every measurement was recorded - in a small number of cases it was simply filed under the wrong programme belonging to the same patient.

    The first pattern involves scheduled measurements and is very rare, affecting a small number of patients. The second pattern involves separate, self-added measurements and affects a somewhat larger but still limited group of patients.

    We have implemented a fix so the issue can no longer occur, and we are making additional improvements in the next app release. If this issue has occurred within your organisation, Luscii will contact you about it.

  • Update
    UTC
    Update

    We are currently mapping the definitive scope. So far this still appears to concern a small number of isolated cases, affecting very few patients. In addition, we have identified a possible scenario that may explain the issue. As soon as we know more, we will post an update.

  • Investigating
    UTC
    Investigating

    Complication:

    For patients enrolled in more than one programme at the same time, a single measurement may in some cases be recorded under the wrong programme and, where applicable, the associated alert. As far as currently known, this concerns only a very small amount of patients. The measurement is not lost, but it may not appear in the programme where it belongs.

    Next steps:

    We are investigating the cause as a priority. We expect to provide an update later today, and will report back sooner as soon as we know more.

Jul 2026 to Sep 2026

Next