Resolved after 43 minutes, affecting Checkout, on August 10, 2026.
Service Disruption - August 10, 2026 \(Resolved\) On August 10, between 12:39 and 14:08 UTC, checkout was not working, affecting 29 users and 77 purchases. The issue was caused by a routine update that relied on a database field mistakenly present in engineer's local development database and missing from production; a fix was deployed and all services were fully restored by 14:08 UTC. All the payments during this window were processed without orders or invoices being created. All affected charges should be refunded.
Affected components
Update timeline
- identified Aug 10, 2026, 01:53 PM UTC
We've temporarily disabled the checkouts to avoid double charges. The team is working on the fix.
- monitoring Aug 10, 2026, 02:14 PM UTC
We've identified the root cause and deployed a fix. Checkouts are fully operational again. We're keeping this incident open while we monitor checkout behavior and assess the impact on orders placed during the disruption. We'll post a final update once monitoring confirms stability.
- resolved Aug 10, 2026, 02:36 PM UTC
Incident has been resolved and the system is fully operational. Check the postmortem for additional information.
- postmortem Aug 10, 2026, 03:25 PM UTC
Service Disruption - August 10, 2026 \(Resolved\) On August 10, between 12:39 and 14:08 UTC, checkout was not working, affecting 29 users and 77 purchases. The issue was caused by a routine update that relied on a database field mistakenly present in engineer's local development database and missing from production; a fix was deployed and all services were fully restored by 14:08 UTC. All the payments during this window were processed without orders or invoices being created. All affected charges should be refunded.
Your product runs on more than Subbly
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