Is Rebill down?

Identified – June 26, 2026, 08:08 UTC We have identified an issue affecting outbound webhook delivery to merchant endpoints, starting at approximately 08:08 UTC today. Events are being generated and queued correctly, but the delivery worker is experiencing periods of reduced throughput, causing notifications to arrive with delays. Payment and subscription processing are operating normally on our side. The impact is limited to the timing of webhook notifications. Our engineering team is actively investigating and we will post the next update as soon as we have more information. We apologize for the inconvenience, and if you need assistance, please reach out to us at [email protected].

Resolved – June 26, 2026, 20:11 UTC Outbound webhook delivery has been fully restored as of 20:11 UTC. All events queued during the affected window (08:08 UTC to 20:11 UTC) have been successfully delivered to merchant endpoints. Payment and subscription processing were not affected at any point. The impact was limited to the timing of webhook notifications, which arrived with delays ranging from a few minutes up to several hours for some events. We apologize for the inconvenience this may have caused. If you notice any missing notification on your end, please reach out to us at [email protected] and we will trace it individually.

Identified – June 18, 2026, 14:35 UTC We identified an issue affecting outbound webhook delivery to merchant endpoints, starting at approximately 10:40 UTC today. During this window, payment events (payment.created and payment.updated) have been processing normally, but the corresponding webhook notifications have not been dispatched to merchant URLs. Payments themselves are unaffected — checkout, authorization, capture and settlement continue to operate normally. The impact is limited to the delivery of webhook notifications. In the meantime, the status of any payment can be retrieved directly through the Dashboard or the GET /v3/payments/{id} API. Our engineering team has identified the root cause and is working on restoring the service. We will post the next update as soon as it is back online. We apologize for the inconvenience, and if you need assistance, please reach out to us at [email protected].

Resolved – June 18, 2026, 15:30 UTC The issue affecting outbound webhook delivery has been resolved. Our engineering team applied a fix at 15:25 UTC, and all webhook notifications generated during the incident window (10:40 UTC to 15:25 UTC) were automatically re-dispatched to merchant endpoints between 15:26 UTC and 15:28 UTC. From that point onward, webhook delivery has resumed normal operation. Payment processing was not affected at any point during the incident. We apologize for the inconvenience, and if you need assistance, please reach out to us at [email protected].

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.

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.

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.