Rebill Outage History

Card payment processing in Mexico has remained stable since the fix was applied. This incident is now resolved. We apologize for the inconvenience. If you require assistance, please contact us at [email protected].

STATUS Resolved DURATION Aug 29, 10:21 – 15:11 UTC UPDATE · Resolved · Aug 29, 17:30 UTC This incident has been resolved. Pix payments in Brazil are operating normally. Between 10:21 and 15:11 UTC, payment requests sent to the Pix processing service were not being completed, which prevented charges from being created. Affected attempts returned a generic decline message. No amount was charged and no funds were withheld from end customers. Card payments were not affected at any point, and payments in other countries operated normally throughout. Customers who could not complete a payment during that window can retry with no issues. If you have questions about a specific transaction, contact 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.

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 - 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.

Dear merchant, We’re pleased to confirm that the issue affecting Argentina has now been fully resolved. Following the recovery of the external fraud-prevention tool involved, all Visa card transactions are processing normally again, and the platform is fully operational across all services. If you require any assistance, please contact us at [email protected]. Thank you for your patience and understanding while this incident was being addressed.

Dear merchant, We experienced a service degradation affecting our API between 18:36 and 19:36 UTC. During this period, some requests may have failed or experienced higher latency. Our team identified and corrected the root cause, and all systems have now returned to normal operation. We apologize for any inconvenience this may have caused and appreciate your understanding. If you need assistance, please don’t hesitate to reach out to us at [email protected].

AWS has confirmed full recovery of the affected services in the US-EAST-1 (N. Virginia) region. We have verified that all Rebill systems are now operating normally, including Subscriptions, Dashboard, and email notifications. The issue has been fully resolved, and we will continue to monitor closely to ensure ongoing stability across all services. If you need any assistance, please don’t hesitate to contact us at [email protected]. Thank you for your patience and understanding throughout this incident.

Dear merchant, The issue that caused service intermittency affecting access to the platform and payment links has been fully resolved. The platform is now operating normally. Our team will continue monitoring to ensure full stability. We appreciate your patience and understanding throughout this process. If you need assistance, please don’t hesitate to reach out to us at [email protected].

Dear merchant, We experienced a temporary service disruption affecting API access from 20:25 UTC to 21:25 UTC on July 4th, 2025. The incident was caused by a configuration update that temporarily impacted external connectivity to our API endpoints. During this period, direct API integrations may have experienced connectivity issues. We're pleased to report that all core payment processing services, including subscription management, automated billing, and notification systems, remained fully operational throughout this time. Our technical team quickly identified and resolved the configuration issue, restoring full API accessibility. We have implemented additional monitoring measures to prevent similar occurrences. We sincerely apologize for any inconvenience this may have caused and appreciate your patience. If you experienced any issues or have questions, please don't hesitate to contact us at [email protected].

Dear merchant, We experienced a temporary downtime affecting card payment processing in Mexico from 18:50 UTC to 20:25 UTC on June 25th, 2025. The incident originated from our local partner and was limited exclusively to card transactions. Other payment methods remained fully operational during this time. Our team coordinated with the provider, and the issue has been successfully resolved. Full service has been restored and we continue to monitor the platform to ensure ongoing stability. We sincerely apologize for any inconvenience this may have caused. If you have any questions or need assistance, please feel free to reach out to us at [email protected].

Resolved – The issue affecting email notifications has been fully resolved as of March 26 at 12:01 UTC. Between March 19 at 21:02 UTC and March 26 at 12:01 UTC, email notifications experienced degraded performance and were not delivered reliably. All other notification channels — including SMS, WhatsApp, and Webhooks — functioned normally throughout this period. All systems are now operating as expected and email notifications are being sent without issues. We sincerely apologize for any inconvenience this may have caused and appreciate your understanding. If you have any questions or concerns, please feel free to contact us at [email protected].

Resolved - The service degradation affecting email, SMS, WhatsApp notifications, and Webhooks has been fully resolved as of November 27 at 08:15 UTC. All systems are now operating normally, and notifications and Webhooks are functioning as expected. We sincerely apologize for any inconvenience this may have caused and appreciate your understanding during this time. If you have any further questions or concerns, please contact us at [email protected].

We experienced a temporary service degradation affecting recurring payments from 16.42 (GTM-3) to 13.50 (GTM, resulting in the error message "Request failed with status code 502." This indicates an internal error, and during this period, some users may have encountered issues processing payments. The degradation started yesterday at 16:42 PM (GMT-3) and lasted until today at 13:50 PM (GMT-3). Please rest assured that any failed payment attempts during this time will automatically be retried. Our team identified the issue and resolved it promptly. Full functionality has been restored, and we are closely monitoring the situation to ensure continued stability. We apologize for any inconvenience this may have caused and appreciate your understanding. If you have any questions, please feel free to contact us at [email protected].

We experienced a performance degradation affecting our Dashboard and API from 7:00 AM to 10:26 AM (UTC-3). During this time, some users may have encountered slower response times or difficulty accessing these services. The issue was caused by a failure in the automatic renewal of the SSL certificate for rebill.com, which is managed by AWS Certificate Manager. Our team quickly identified the problem and implemented a fix. Full functionality has been restored, and we are monitoring the situation to ensure continued stability. We apologize for any inconvenience this may have caused and appreciate your understanding. If you have any questions, please feel free to contact us at [email protected].