Major incident
Mews: Bills can only contain up to 0 items
Jul 9, 2026, 14:10 UTC
started
14:24 UTC
resolved
15 min
duration
Current status of Mews: Operational — live Mews status
Timeline
- Jul 9, 2026, 14:10 UTCidentifiedThe Mews team identified the issue and is working on a resolution. Further updates will follow as we make progress.
- Jul 9, 2026, 14:14 UTCmonitoringWe have resolved the issue, customer are confirming that bills can be closed again. We are monitoring the systems now before we close this incident
- Jul 9, 2026, 14:24 UTCresolvedThe issue is now fully resolved. Us and customers confirmed they are now unblocked and can close bills.
- Jul 16, 2026, 15:33 UTCpostmortem**Problem** On 2026-07-09T13:37:00Z, a deployment introduced a configuration change that inadvertently set the maximum number of items allowed on a bill to zero. As a result, all customers across the production environment were unable to close bills. Users saw the error message: "Bills can only contain up to 0 items.". **Action** Our team identified the root cause within minutes of the incident being reported and corrected the configuration at 2026-07-09T14:05:34Z. Bill closing was restored immediately. **Causes** A newly configuration defaulted to 0 instead to the correct number.
Updates as published by Mews (original).
Other services with incidents at the same time
- Subsplash 14:22 UTC · Error Loading Trends AI and Giving Analytics pages
- Thomson Reuters Legal 13:56 UTC · HighQ US iSheet Update Issue
- DTN 13:25 UTC · Upstream Internet Issue
More Mews incidents
- October 22, 2026 An issue with sending inventory updates to Booking.com
- October 21, 2026 Critical 0 day PHP vulnerability
- October 19, 2026 Downgraded Performance - Delayed emails
- October 19, 2026 Delays in accounting ledgers and trial balance updates
- October 18, 2026 Issue with check in flow in Mews
- October 15, 2026 Booking.com reservations delayed