Procurify incident

Spend Insights - Data Freshness

Minor Resolved View vendor source →

Procurify experienced a minor incident on January 10, 2026 affecting Spend Insights, lasting 12h 32m. The incident has been resolved; the full update timeline is below.

Started
Jan 10, 2026, 10:33 AM UTC
Resolved
Jan 10, 2026, 11:05 PM UTC
Duration
12h 32m
Detected by Pingoru
Jan 10, 2026, 10:33 AM UTC

Affected components

Spend Insights

Update timeline

  1. identified Jan 10, 2026, 10:33 AM UTC

    We are investigating a partial outage for our Spend Insights service. Our team is currently working to restore the service. This outage affects: • viewing Spend Insights data from 2026-01-09 and later We apologize for any inconvenience caused. We will provide another updated in 1 hour. Thank you for your understanding.

  2. identified Jan 10, 2026, 11:23 AM UTC

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

  3. identified Jan 10, 2026, 11:52 AM UTC

    We are continuing to work on a fix for this issue. We will provide another updated in 1 hour. Thank you for your understanding.

  4. identified Jan 10, 2026, 12:41 PM UTC

    We are continuing to work on a fix for this issue. We will provide another updated in 1 hour. Thank you for your understanding.

  5. identified Jan 10, 2026, 01:39 PM UTC

    We are continuing to work on a fix for this issue. We will provide another updated in 1 hour. Thank you for your understanding.

  6. identified Jan 10, 2026, 03:01 PM UTC

    We are continuing to work on a fix for this issue. We will provide another updated in 1 hour. Thank you for your understanding.

  7. identified Jan 10, 2026, 04:04 PM UTC

    We are continuing to work on a fix for this issue. We will provide another updated in 1 hour. Thank you for your understanding.

  8. identified Jan 10, 2026, 05:20 PM UTC

    We are continuing to work on a fix for this issue. We will provide another updated in 1 hour. Thank you for your understanding.

  9. identified Jan 10, 2026, 06:17 PM UTC

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

  10. identified Jan 10, 2026, 08:42 PM UTC

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

  11. monitoring Jan 10, 2026, 10:20 PM UTC

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

  12. resolved Jan 10, 2026, 11:05 PM UTC

    This incident has been resolved.