Procurify incident

Degraded Performance: Web Application

Minor Resolved View vendor source →

Procurify experienced a minor incident on November 18, 2025 affecting Web Application and Mobile Applications and 1 more component, lasting 5h 33m. The incident has been resolved; the full update timeline is below.

Started
Nov 18, 2025, 06:14 PM UTC
Resolved
Nov 18, 2025, 11:48 PM UTC
Duration
5h 33m
Detected by Pingoru
Nov 18, 2025, 06:14 PM UTC

Affected components

Web ApplicationMobile ApplicationsSpending CardAP AutomationBill PaymentsNotificationsData ManagementLogin/SSOAccounting IntegrationsPunchOuts

Update timeline

  1. investigating Nov 18, 2025, 06:14 PM UTC

    We are investigating degraded performance of our Procurify web application. Our team is currently working to isolate and remediate the issue. We apologize for any inconvenience caused. We will provide another updated in 30 minutes. Thank you for your understanding.

  2. monitoring Nov 18, 2025, 06:31 PM UTC

    We have identified the performance issue and have applied a fix. Performance is restored but we will continue to monitor for the next 30 minutes.

  3. monitoring Nov 18, 2025, 07:04 PM UTC

    Performance remains steady, but we have identified additional areas of concern and continue to monitor. We will provide another update in 30 minutes or upon final resolution.

  4. monitoring Nov 18, 2025, 07:36 PM UTC

    The team continues to monitor performance, and has rolled out an additional mitigation. Site performance remains stable. We will provide another updated in 60 minutes or upon final resolution.

  5. monitoring Nov 18, 2025, 08:42 PM UTC

    While performance remains stable, the team is leaving this incident open out of an abundance of caution as we work through applying additional mitigations. The next update will be in two hours, or upon final resolution.

  6. monitoring Nov 18, 2025, 10:41 PM UTC

    We have rolled out all mitigations for this issue, and will continue to monitor for the next hour.

  7. resolved Nov 18, 2025, 11:48 PM UTC

    This incident has been resolved.