Between 05:26 and 06:01 IST on 23 October 2026, most Plum requests failed. Users could not log in, the storefront and checkout were unavailable, Plum Pro API orders failed, and GV link redemptions could not be completed.
Cause: following the earlier performance degradation (02:07–05:26 IST), the overloaded caching component that our authentication service depends on became unresponsive.
Resolution: our engineering team traced the load to an internal background process, stopped it, cleaned up the affected component and restored the authentication service. Services recovered at 06:01 IST, and all systems have operated normally since 06:05 IST. We are monitoring closely.
What you should do: some orders and API requests submitted between 02:07 and 06:01 IST may have failed or timed out. Plum Pro API clients should retry orders that failed during that window. Orders that completed successfully are not affected. If you see a discrepancy, contact your account manager or Plum support with your order reference.
Next steps: we are tightening safeguards so background jobs cannot overload shared infrastructure, and adding earlier alerting on this component. We apologise for the disruption.
Posted Oct 23, 2026 - 00:31 UTC
This incident affected: Plum (Plum Accounts, Plum Stores).