Ansarada incident

Ansarada platform outage

Critical Resolved View vendor source →

Ansarada experienced a critical incident on November 18, 2025 affecting Ansarada.com website and User Administration and 1 more component, lasting 3h 30m. The incident has been resolved; the full update timeline is below.

Started
Nov 18, 2025, 11:58 AM UTC
Resolved
Nov 18, 2025, 03:28 PM UTC
Duration
3h 30m
Detected by Pingoru
Nov 18, 2025, 11:58 AM UTC

Affected components

Ansarada.com websiteUser AdministrationHome DashboardDataroom ManagementAnsarada IdentityDocumentsQ&AReportingTenders Submission ToolTender Evaluation Tool

Update timeline

  1. identified Nov 18, 2025, 11:58 AM UTC

    The Ansarada platform is currently experiencing an outage. We have identified the issue with third party provider and are working with them to get it resolved ASAP. We will provide an update here in 15 minutes.

  2. identified Nov 18, 2025, 12:15 PM UTC

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

  3. monitoring Nov 18, 2025, 12:22 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. identified Nov 18, 2025, 12:28 PM UTC

    Unfortunately the provider issue still persists, we will update here as we get more information

  5. monitoring Nov 18, 2025, 12:35 PM UTC

    A fix has been implemented and we are monitoring the results.

  6. monitoring Nov 18, 2025, 12:56 PM UTC

    We are continuing to monitor for any further issues.

  7. monitoring Nov 18, 2025, 01:20 PM UTC

    We are continuing to monitor for any further issues.

  8. identified Nov 18, 2025, 01:39 PM UTC

    Provider services still experience high error rate, which results in some of Ansarada web sites periodically becoming inaccessible. They have reported the underlying issue has been identify and is being fixed. We will keep you informed when the issue gets resolved.

  9. identified Nov 18, 2025, 02:03 PM UTC

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

  10. identified Nov 18, 2025, 02:34 PM UTC

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

  11. monitoring Nov 18, 2025, 02:43 PM UTC

    A fix has been implemented and we are monitoring the results.

  12. resolved Nov 18, 2025, 03:28 PM UTC

    This incident has been resolved.