Is Rebill down?
Last checked just nowNo incidents right now.
Rebill is operational right now. Last checked just now; the most recent incident resolved 59d ago.
Real-time Rebill status, recent outages, and incident history: pulled directly from Rebill's official status page at status.rebill.com every 5 minutes. Pingoru tracks 34 Rebill services and has captured 2 incidents in the last 90 days (99.87% uptime). Get email, Slack, Discord, or webhook alerts the moment Rebill reports a new incident, free for 3 monitors, no credit card.
Recent outages & incidents
Past 90 days- Payment ProcessingPayment Processing
Timeline · 3 updates
- identified · Sep 01, 2026, 11:22 PM UTC
Since 20:00 UTC today, we have been observing degraded performance in card payment processing for transactions in Mexico. Some transactions may be declined or take longer than usual to complete. The cause has been identified and our team is actively working to restore full service as soon as possible. A further update will be provided as soon as additional information is available. If you require assistance, please contact us at [email protected].
- monitoring · Sep 02, 2026, 02:13 AM UTC
The issue affecting card payment processing in Mexico has been resolved and transactions are processing normally. We are monitoring the service closely to confirm stable performance before closing this incident. Any transaction declined during the affected window can be retried successfully. If you require assistance, please contact us at [email protected].
- resolved · Sep 02, 2026, 11:49 AM UTC
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].
Latest: 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, pleas…
-
- Payment Processing
Timeline · 1 update
- resolved · Aug 29, 2026, 05:49 PM UTC
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].
Latest: 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:…
-
Incident record
Since April 2026 · Statuspage by Atlassian · 34 components checked every 5 minutesThe longest incident in the last year, Intermittent webhook delivery delays on June 26, 2026, ran for 24 hours. 7 maintenance windows announced in the same period.
Most affected components, last 12 months
- Payment Processing2
- Webhooks2
- Payment Processing1
- Payment Processing1
- Payment Processing1
Latest incidents
- Degraded card payment processing in Mexico
Since 20:00 UTC today, we have been observing degraded performance in card payment processing for transactions in Mexico. Some transactions may be declined or…
- Pix payments in Brazil temporarily unavailable
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…
- Intermittent webhook delivery delays
Identified – June 26, 2026, 08:08 UTC We have identified an issue affecting outbound webhook delivery to merchant endpoints, starting at approximately 08:08…
- Started Sep 01, 2026, 11:22 PM UTC · Resolved Sep 02, 2026, 11:49 AM UTC · 12h 26m
- Started Aug 29, 2026, 10:21 AM UTC · Resolved Aug 29, 2026, 03:11 PM UTC · 4h 50m