LoungeUp - Notice history

All systems operational

100% - uptime

LoungeUp Portal - Operational

100% - uptime
1st Feb 2024 · 100.0%1st Mar · 100.0%30th Apr · 100.0%

Previous page

Next page

1st Feb 2024
1st Mar 2024
30th Apr 2024

LoungeUp ID - Operational

100% - uptime
1st Feb 2024 · 100.0%1st Mar · 99.99%30th Apr · 100.0%

Previous page

Next page

1st Feb 2024
1st Mar 2024
30th Apr 2024

LoungeUp Back-Office - Operational

100% - uptime
1st Feb 2024 · 100.0%1st Mar · 100.0%30th Apr · 100.0%

Previous page

Next page

1st Feb 2024
1st Mar 2024
30th Apr 2024

LoungeUp Dmbook - Operational

100% - uptime
1st Feb 2024 · 100.0%1st Mar · 100.0%30th Apr · 100.0%

Previous page

Next page

1st Feb 2024
1st Mar 2024
30th Apr 2024

Notice history

1st Apr 2024

Some PMS synchronizations are late
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Identified
    Identified

    The faulty data has been identified and isolated.

    The data is now imported timely and campaigns are delivered on time.

    We will update this incident as soon as we have fixed the origin of it.

  • Investigating
    Investigating
    We are currently investigating this incident.

1st Mar 2024

Important delays in some PMS updates
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    The situation is now far better and the delay is decreasing. All campaigns triggered by a change in booking state are delivered successfully. We monitor the situation.

  • Investigating
    Investigating

    We have identified a bottleneck on some PMS updates leading to delays in delivering some email or SMS campaigns. We are working towards a quick resolution.

LoungeUp ID (our identity service) is responding with delay
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    The fix is deployed, we are now monitoring the situation.

  • Identified
    Identified

    Our reverse-proxy component is crash looping. We have identified the reason and are deploying a fix.

  • Investigating
    Investigating

    These delays are slowing down the whole platform.

    We are currently investigating this incident.

1st Feb 2024

Slow Application
  • Resolved
    Resolved
    This incident has been resolved.
  • Investigating
    Investigating
    We are currently investigating this incident.
Web applications and backoffice are repsonding very slowly
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    We are monitoring the situation which is now back to normal

  • Identified
    Identified

    The database was experiencing bad performances

  • Investigating
    Investigating
    We are currently investigating this incident.

1st Feb 2024 to 1st Apr 2024

Next