RaiseNow incident

Incident detected

Notice Ongoing View vendor source →

RaiseNow is currently experiencing a notice incident, which began 2h ago. The vendor's full update timeline is below.

Started
May 31, 2026, 06:22 AM UTC
Resolved
Ongoing
Duration
● 1h 45m
Detected by Pingoru
May 31, 2026, 06:22 AM UTC

Update timeline

  1. investigating May 31, 2026, 06:22 AM UTC

    We are aware of an issue affecting our services and currently working on identifying its root cause. You can expect an update on the incident in the next hour.

  2. investigating May 31, 2026, 06:27 AM UTC

    We have identified the cause of the incident and are actively working on a resolution. As soon as a fix has been implemented, you'll find an update here.

  3. investigating May 31, 2026, 06:31 AM UTC

    We have identified the cause of the incident and are actively working on a resolution. As soon as a fix has been implemented, you'll find an update here.

  4. investigating May 31, 2026, 07:01 AM UTC

    We have identified the cause of the incident and are actively working on a resolution. As soon as a fix has been implemented, you'll find an update here.

  5. investigating May 31, 2026, 07:01 AM UTC

    We have identified the cause of the incident and are actively working on a resolution. As soon as a fix has been implemented, you'll find an update here.

  6. investigating May 31, 2026, 07:15 AM UTC

    We have identified the cause of the incident and are actively working on a resolution. As soon as a fix has been implemented, you'll find an update here.

  7. investigating May 31, 2026, 07:17 AM UTC

    We have identified the cause of the incident and are actively working on a resolution. As soon as a fix has been implemented, you'll find an update here.

  8. investigating May 31, 2026, 07:47 AM UTC

    We have identified the cause of the incident and are actively working on a resolution. As soon as a fix has been implemented, you'll find an update here.

  9. investigating May 31, 2026, 07:48 AM UTC

    We have identified the cause of the incident and are actively working on a resolution. As soon as a fix has been implemented, you'll find an update here.