SEVENROOMS Outage History
7 incidents recorded over the last 365 days, 7 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded SEVENROOMS Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 21, 2026 | SevenRooms OS – Delayed Real-Time Updates Due to Google Firebase IncidentGoogle Firebase has confirmed full recovery and have resolved the incident on their side Impact to our product was limited to 1:00-4:45 PM ET on October 21 and was minor: some updates took longer to appear across… | 21h 4m | Resolved |
| Sep 7, 2026 | SevenRooms Partial Outage Affecting VMS and WidgetsThis incident is resolved and SevenRooms is fully operational. A mitigation at 8:27 AM ET restored normal operation, and systems have remained stable since. | 3h 43m | Resolved |
| Aug 4, 2026 | Investigating service degradation affecting API, Booking, and Sync servicesThis incident has been resolved. | 18 min | Resolved |
| Jun 21, 2026 | Investigating cloud service disruptionThis incident has been resolved. | 4h 25m | Resolved |
| Feb 3, 2026 | Intermittent Reservation Widget ConnectivityThis issue has been fully resolved, and all reservation widgets and services are now operating normally. We will continue to monitor performance throughout the day to ensure continued stability. | 2h 0m | Resolved |
| Dec 8, 2025 | SevenRooms Widget Loading IssuesWhat Happened? -Some clients reported encountering errors upon loading widgets on our platform. Impact -The issue temporarily affected the proper loading of widgets on the SevenRooms platform. What We Did / Resolution… | -16 min | Resolved |
| Nov 19, 2025 | Resolved – Stripe incident impacting card payments on Reservation WidgetOn November 18, 2025, between approximately 5:00 PM and 10:00 PM Eastern, some guests using our reservation widget experienced issues loading the payment form and completing card payments when processed via… | -1320 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next SEVENROOMS incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This SEVENROOMS Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before SEVENROOMS acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single SEVENROOMS outage in this window ran 21h 4m, against a mean recovery of 6h 18m. If you depend on SEVENROOMS in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.