Sense incident

Elevated API Errors and Increased Latency in Sense Meetings

Minor Resolved View vendor source →

Sense experienced a minor incident on February 24, 2026 affecting Sense Meetings, lasting 1h 45m. The incident has been resolved; the full update timeline is below.

Started
Feb 24, 2026, 08:15 PM UTC
Resolved
Feb 24, 2026, 10:00 PM UTC
Duration
1h 45m
Detected by Pingoru
Feb 24, 2026, 08:15 PM UTC

Affected components

Sense Meetings

Update timeline

  1. identified Feb 24, 2026, 08:15 PM UTC

    We have been alerted of intermittent users not being able to connect their calendars to Sense Meetings or slowness in the Meetings product due to elevated error rates and increased latency with our downstream scheduler service provider. This has been confirmed to be identified and is actively being worked on to mitigate the issue as we work with them for updates.

  2. monitoring Feb 24, 2026, 09:36 PM UTC

    We have received confirmation that a fix has been successfully implemented by our downstream scheduler service and seeing stability in Sense Meetings for all users once more. We will continue to monitor to ensure we don't see these error rates or latency recur. If you believe you're still facing issues, please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new and our team will review.

  3. resolved Feb 24, 2026, 10:00 PM UTC

    After monitoring, we are continuing to see Sense Meetings and all other Sense products work as expected and error rates have continued to stay at normal levels. We have received confirmation from our downstream scheduler partner that all services will continue to be monitored and additional preventive measures will be implemented to prevent this from recurring. If you believe you're still facing issues, please submit a ticket to our support team at https://support.sensehq.co/hc/en-us/requests/new and our team will review on a case by case basis.