Inspera incident

Delays in Inspera Assessment

Notice Resolved View vendor source →

Inspera experienced a notice incident on May 15, 2025 affecting Inspera Assessment - Admin and Inspera Assessment - Student, lasting 1d 2h. The incident has been resolved; the full update timeline is below.

Started
May 15, 2025, 07:48 AM UTC
Resolved
May 16, 2025, 09:48 AM UTC
Duration
1d 2h
Detected by Pingoru
May 15, 2025, 07:48 AM UTC

Affected components

Inspera Assessment - AdminInspera Assessment - Student

Update timeline

  1. investigating May 15, 2025, 07:48 AM UTC

    We are currently experiencing an issue causing delays in operations for all users in Inspera Assessment. We are investigating the issue with the highest priority and a new update will be posted as soon as we know more.

  2. investigating May 15, 2025, 08:24 AM UTC

    We are continuing to investigate this issue.

  3. monitoring May 15, 2025, 09:05 AM UTC

    Our team have implemented mitigating actions to resolve the issue, which has reduced the operational delays. We will keep monitoring the situation closely. Further updates will be provided every 30 minutes or until the issue is resolved.

  4. monitoring May 15, 2025, 09:35 AM UTC

    We are still monitoring the situation. This page will be updated every 30 minutes until the issue is resolved.

  5. monitoring May 15, 2025, 10:10 AM UTC

    We are continuing to monitor the situation. This page will be updated at least every hour until the issue is resolved.

  6. monitoring May 15, 2025, 10:14 AM UTC

    We are continuing to monitor the situation. This page will be updated at least every hour until the issue is resolved.

  7. monitoring May 15, 2025, 10:33 AM UTC

    We are continuing to monitor for any further issues.

  8. monitoring May 15, 2025, 11:30 AM UTC

    We are continuing to monitor the situation.

  9. monitoring May 15, 2025, 12:37 PM UTC

    The changes we have done today, perform as expected. We have not planned any further actions for today. We will monitor the situation, and give a new update about the status tomorrow 12:00 CEST.

  10. resolved May 16, 2025, 09:48 AM UTC

    This incident has been resolved.