Respond.io incident
Push Notification for browsers not received by user
Respond.io experienced a minor incident on August 5, 2026 affecting Notifications (Notifications), lasting 6d 2h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Aug 05, 2026, 05:30 AM UTC
We are currently experiencing an issue where browser notifications are not being delivered, despite browser notification settings being configured correctly. Our engineering team has been alerted and is actively investigating the root cause. We apologize for the inconvenience and will...
- investigating Aug 05, 2026, 05:35 AM UTC
Our engineering team has identified the issue affecting browser notifications and is actively investigating the root cause. We are working to identify the cause of the disruption and restore normal browser notification delivery as quickly as possible. We will continue to provide...
- investigating Aug 05, 2026, 07:00 AM UTC
Our engineering team has identified the cause of the browser notification issue and is actively working on a fix. The issue is related to how the browser notification service initializes and resets under certain conditions, which can prevent notifications from being delivered as expected. ...
- investigating Aug 05, 2026, 08:00 AM UTC
Our engineering team has identified the cause of the browser notification issue and is actively working on a fix. We will provide another update as soon as more information becomes available.
- resolved Aug 11, 2026, 08:10 AM UTC
We are happy to report that the issue affecting browser push notifications has been resolved. Our engineering team deployed a hotfix to address the issue, and browser notifications are now being delivered as expected. The fix is continuing to propagate across all users, with related errors...