Luscii - Notice history

Luscii Web App experiencing degraded performance

Luscii Web App - Degraded performance

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

Previous page

Next page

Jul 2025
Aug 2025
Sep 2025

Luscii Android App - Operational

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

Previous page

Next page

Jul 2025
Aug 2025
Sep 2025

Luscii iOS App - Operational

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

Previous page

Next page

Jul 2025
Aug 2025
Sep 2025

Luscii Integrations - Operational

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

Previous page

Next page

Jul 2025
Aug 2025
Sep 2025

Luscii Metabase - Operational

Customer portal - Operational

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

Previous page

Next page

Jul 2025
Aug 2025
Sep 2025

Notice history

Sep 2025

No notices reported this month

Aug 2025

iOS users experiencing crashes when opening action on selfcare page
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    We released iOS app version 2.96.1 which fixes the issues and are currently monitoring the result.

  • Identified
    Identified

    We identified that opening planned actions that have patient information in them might also crash for patients on this version of the iOS app. We are currently working on a hotfix for these issues and aiming to release that today.

  • Investigating
    Investigating

    We are currently investigating an incident where users on iOS using the latest version 2.96.0 experience a crash of the app when opening an action (education module, patient information) on the selfcare page.
    At this moment, there is no workaround for these users trying to access actions on the selfcare page.

    Planned actions scheduled on the home page in the app are not affected.
    We are working on a fix to prevent this crash from happening.

Some patients on iOS app version 2.96.0 that use Dutch as their app language might see their actions in English instead. We are investigating.
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    We released iOS app version 2.96.1 which fixes the issues.

  • Update
    Update
    We are currently investigating this incident.
  • Investigating
    Investigating
    We are currently investigating this incident.
Issue not all overdues generated
  • Monitoring
    Monitoring

    Yesterday we released a hotfix, and at this moment all overdue alerts are being generated as expected — the issue has stabilized.

    The problem was caused by the process creating overdue alerts occasionally crashing under heavy system load. The hotfix improves logging and distributes the load more efficiently, so the issue should no longer occur. If it does, we now have better logging in place to quickly identify what happens and which protocols are affected.

    We will continue to closely monitor the situation in the coming days to ensure the fix remains effective and no new cases arise.

    For those who would like more details, please send support@luscii.com a message. We can share on which day a failure in overdues might may have occurred for a specific protocol. However, we cannot confirm whether the protocol itself actually failed.

  • Identified
    Identified

    Luscii has released a hotfix to improve logging.
    This update gives us better visibility into when and where overdues are not being generated. It will help us investigate whether the issue is still occurring. We are actively monitoring the situation and will keep you informed.

  • Investigating
    Investigating

    At this moment we are investigating an issue in which some cases overdue alerts are not generated. At this moment there is no workaround, we are working on a hotfix for this issue.

iOS users experiencing crash of app due to connected devices
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    We implemented a fix in the iOS 2.96.0 release and are currently monitoring the result.

  • Update
    Update

    We are continuing to work on a fix for this incident. At this moment, we expect the fix to be released on monday 25th.

  • Identified
    Identified

    At this moment patients using the iOS version of the Luscii app experience crashes for connected devices. Patients can still send in measurement manually, instead of using the connected measurement. If a patient experiences a crash they can use the workaround mentioned below. A fix has already been identified and is being tested at this moment. As soon as the fix is confirmed, it will be released.

    Workaround for patients

    • Delete the app

    • Reinstall from the App Store

    • Open the action and choose “Send measurements manually”

Emails Temporarily Unavailable
  • Completed
    19-08-2025 at 4:00 AM
    Completed
    19-08-2025 at 4:00 AM
    Maintenance has completed successfully
  • In progress
    19-08-2025 at 2:00 AM
    In progress
    19-08-2025 at 2:00 AM
    Maintenance is now in progress
  • Planned
    19-08-2025 at 2:00 AM
    Planned
    19-08-2025 at 2:00 AM

    On August 19th, 2025, between 03:00 and 05:00 (BST) / 04:00–06:00 (CEST), our email provider will be performing scheduled maintenance on the email infrastructure.

    During this time, no verification codes or email notifications about open actions will be sent.

    If you are working at night, please make sure to log in before 03:00 (BST) or 04:00 (CEST). A care professional’s login session remains valid for up to 4 hours, even during maintenance.

    Also patients attempting to log in during this period will not receive a verification code. However, given the timing, we expect this to occur only in rare or exceptional cases.

Jul 2025

Priority 2: Patient information blocks duplicated when switching protocols
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    Update: The hotfix has been released and the issue can no longer occur. We’re working on a solution for the already duplicated information blocks.

  • Identified
    Identified

    Update: Tomorrow we will release a fix to prevent this issue from happening again. A separate fix is still needed for the already duplicated information blocks.

  • Investigating
    Investigating

    Situation: We have discovered an issue where patient information blocks are duplicated when switching protocols within the same program. In some cases, editing these duplicated information blocks causes personalized information to not be displayed correctly to patients.

    Complication: These duplicates are visible in the web version (not to patients in the mobile app), but can be personalized. In specific cases, this results in missing personalized information for patients.

    Next steps: We are investigating this issue with high urgency. Updates will follow as more becomes known.

Jul 2025 to Sep 2025

Next