RLDatix incident

[RL6] [ALL] SERVICE INTERRUPTION

Critical Resolved View vendor source →

RLDatix experienced a critical incident on July 19, 2024 affecting EASTERN Time Zone and RL6 US Hosted AWS (Production) and 1 more component, lasting 2d 20h. The incident has been resolved; the full update timeline is below.

Started
Jul 19, 2024, 06:06 AM UTC
Resolved
Jul 22, 2024, 02:37 AM UTC
Duration
2d 20h
Detected by Pingoru
Jul 19, 2024, 06:06 AM UTC

Affected components

EASTERN Time ZoneRL6 US Hosted AWS (Production)CENTRAL Time ZoneRL6 US Hosted AWS (Test)MOUNTAIN Time ZoneRL6 US Hosted AWS (Training)PACIFIC Time ZoneTEST (ALL Time Zones)TRAINING (ALL Time Zones)ARIZONA Time Zone

Update timeline

  1. investigating Jul 19, 2024, 06:06 AM UTC

    Hello RL6 Hosted Customers, We are experiencing technical problems at this time. Some customers may experience a short service interruption accompanied by a "service unavailable" or "please try again" message. Our operations team is in the process of troubleshooting the issue and will provide periodic updates via the RL6 Hosting Status Page, located at: https://rl6-hosting-status.rldatix.com/ If you have submitted a support ticket, please note that interim updates on this service interruption will be posted to the RL6 Hosting Status Page. Support tickets will only be updated once the issue has been resolved. We apologize for the disruption and wish to reassure you that our operations team is working to resolve the issue as quickly as possible. Thank you, The RLDatix Team

  2. investigating Jul 19, 2024, 06:07 AM UTC

    We are continuing to investigate this issue.

  3. identified Jul 19, 2024, 07:19 AM UTC

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

  4. identified Jul 19, 2024, 11:11 AM UTC

    We are continuing to work on a fix for this issue.

  5. identified Jul 19, 2024, 11:59 AM UTC

    We are continuing to work on a fix for this issue.

  6. identified Jul 19, 2024, 03:29 PM UTC

    We are continuing to work on a fix for this issue.

  7. resolved Jul 22, 2024, 02:37 AM UTC

    This incident has been resolved.