Procurify incident

Spend Insights not loading

Major Resolved View vendor source →

Procurify experienced a major incident on October 20, 2025 affecting Spend Insights, lasting 13h 43m. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2025, 10:45 PM UTC
Resolved
Oct 21, 2025, 12:29 PM UTC
Duration
13h 43m
Detected by Pingoru
Oct 20, 2025, 10:45 PM UTC

Affected components

Spend Insights

Update timeline

  1. investigating Oct 20, 2025, 10:45 PM UTC

    We have identified an issue with a third-party service preventing users from accessing Spend Insights. We are working closely with the third-party service to restore functionality and will provide updates as available. Thank you.

  2. investigating Oct 20, 2025, 11:07 PM UTC

    We are continuing to investigate this issue.

  3. investigating Oct 20, 2025, 11:23 PM UTC

    We have identified an issue with a third-party service related to the ongoing AWS region outage. We will monitor the status of the affected third-party service and provide updates.

  4. identified Oct 20, 2025, 11:57 PM UTC

    We have identified an issue with a third-party service related to the ongoing AWS region outage. We will monitor the status of the affected third-party service and provide updates.

  5. identified Oct 21, 2025, 12:26 AM UTC

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

  6. identified Oct 21, 2025, 01:59 AM UTC

    The third-party service is continuing to work on a fix for this issue. Users may be able to intermittently access Spend Insights.

  7. identified Oct 21, 2025, 02:59 AM UTC

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

  8. identified Oct 21, 2025, 04:21 AM UTC

    The third-party service is continuing to work on a fix for this issue. Users may be able to intermittently access Spend Insights.

  9. identified Oct 21, 2025, 06:53 AM UTC

    The Spend Insights feature is intermittently accessible. Our third-party partner is working toward a fix to restore service fully. We will provide an update whenever there is new information.

  10. monitoring Oct 21, 2025, 10:14 AM UTC

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

  11. resolved Oct 21, 2025, 12:29 PM UTC

    This incident has been resolved.