Resolved after 13 hours 23 minutes, affecting Subscriptions, on May 18, 2026.
2026-05-18 - 20.30 UTC-0 The recurring billing engine is fully restored and processing scheduled charges normally. Cycles that were delayed during the incident window will be automatically retried in the upcoming engine runs, following each merchant's configured retry policy. New subscriptions, one-time payments, refunds, and all other checkout flows were not affected.
Affected components
Update timeline
- identified May 18, 2026, 10:22 PM UTC
2026-05-18 - 09.00 UTC-0 We identified an infrastructure event from our messaging provider that caused a degradation in the asynchronous dispatch of scheduled charges. New subscription checkout flows, refunds, and one-time payments were not impacted. We are deploying a mitigation.
- monitoring May 18, 2026, 10:23 PM UTC
2026-05-18 - 19.56 UTC-0 We have deployed a platform-level mitigation and are monitoring the recovery of recurring charge processing across all merchants. Backlogged cycles are being automatically retried.
- resolved May 18, 2026, 10:24 PM UTC
2026-05-18 - 20.30 UTC-0 The recurring billing engine is fully restored and processing scheduled charges normally. Cycles that were delayed during the incident window will be automatically retried in the upcoming engine runs, following each merchant's configured retry policy. New subscriptions, one-time payments, refunds, and all other checkout flows were not affected.
Your product runs on more than Rebill
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services