Awell - Notice history

100% - uptime

[EU] Awell Operate - Operational

100% - uptime
Apr 2024 · 100.0%May · 100.0%Jun · 100.0%
Apr 2024
May 2024
Jun 2024

[EU] Awell Design - Operational

100% - uptime
Apr 2024 · 100.0%May · 100.0%Jun · 100.0%
Apr 2024
May 2024
Jun 2024

[EU] Awell Manage - Operational

100% - uptime
Apr 2024 · 100.0%May · 100.0%Jun · 100.0%
Apr 2024
May 2024
Jun 2024

[EU] Mirth - Operational

100% - uptime
Apr 2024 · 100.0%May · 100.0%Jun · 100.0%
Apr 2024
May 2024
Jun 2024
100% - uptime

[UK] Awell Operate - Operational

100% - uptime
Apr 2024 · 100.0%May · 100.0%Jun · 100.0%
Apr 2024
May 2024
Jun 2024

[UK] Awell Design - Operational

100% - uptime
Apr 2024 · 100.0%May · 100.0%Jun · 100.0%
Apr 2024
May 2024
Jun 2024

[UK] Awell Manage - Operational

100% - uptime
Apr 2024 · 100.0%May · 100.0%Jun · 100.0%
Apr 2024
May 2024
Jun 2024
100% - uptime

[US] Awell Operate - Operational

100% - uptime
Apr 2024 · 100.0%May · 100.0%Jun · 99.87%
Apr 2024
May 2024
Jun 2024

[US] Awell Design - Operational

100% - uptime
Apr 2024 · 100.0%May · 100.0%Jun · 100.0%
Apr 2024
May 2024
Jun 2024

[US] Awell Platform - Web App - Operational

100% - uptime
Apr 2024 · 100.0%May · 100.0%Jun · 100.0%
Apr 2024
May 2024
Jun 2024
100% - uptime

Mailgun Outbound Delivery - Operational

Third Party: Retool → Infrastructure - Operational

Third Party: Retool → Resource Queries - Operational

Third Party: Retool → Web Application and APIs - Operational

Third Party: Retool → Source Control - Operational

Notice history

Jun 2024

[US] Orchestration - GraphQL API outage
  • Update
    Update

    We’re happy to let you know that we’ve wrapped up all the steps to fix the recent outage. Our team has identified and resumed 26 stuck care flows.

    Here’s what we’ve done:

    1. Fixing Bottlenecks: We found the root causes of the bottlenecks and made the necessary changes to sort them out.

    2. Better Alerts: We’ve set up new alerting policies that will notify us proactively if something similar happens again.

    3. Improved Recovery: We’ve added more recovery strategies to make sure care flows don’t get stuck after incidents like this.

    Thank you for your patience and understanding as we worked through this. We’re committed to providing you with reliable service and will continue to improve our systems.

  • Update
    Update

    An unexpected increase in the usage of the product put two key systems under stress (Message broker and Application database). We have identified what caused the bottleneck in each system (memory leak in the message broker, throttled CPU in the application database) and made the necessary changes to remove them.

    In addition, we've created new alerting policies that will proactively inform us should a similar scenario play out. This will enable us to take mitigation actions early enough to prevent system failures.

    We are still investigating the impact of this incident and will post another update when it has been identified.

  • Update
    Update

    The team is investigating the root cause to ensure the issue does not reoccur. Further updates will be provided once the investigation is complete.

  • Resolved
    Resolved

    [US] Orchestration - GraphQL API is now operational! This update was created by an automated monitoring service.

  • Investigating
    Investigating

    [US] Orchestration - GraphQL API cannot be accessed at the moment. This incident was created by an automated monitoring service.

May 2024

No notices reported this month

Apr 2024 to Jun 2024

Next