Teem Outage History
Teem is up right nowTeem had 9 outages in the last 2 years totaling 644h 43m of downtime — averaging 0.4 incidents per month.
There were 9 Teem outages since August 10, 2024 totaling 644h 43m of downtime. Each is summarised below — incident details, duration, and resolution information.
S2- All day bookings made through the Outlook plugin are not reflecting as expected.
Timeline · 14 updates
S1 - TEEM Performance Issues
Timeline · 8 updates
S2 - Google Calendar Duplicates/O365 Syncing and Performance Issues
Timeline · 3 updates
S1 - App.teem.com degraded performance
Timeline · 6 updates
S2 - Calendar Events using Google & O365 are not syncing
Timeline · 11 updates
Calendar Sync issues
Timeline · 6 updates
- investigating Aug 22, 2024, 05:51 PM UTC
We are currently experiencing issues with Calendar syncing. Our engineering team has been notified and we'll be updating this status page at 1:51 MST.
- investigating Aug 22, 2024, 07:49 PM UTC
We are continuing to investigate this issue. We'll be updating the status page at 4:51 PM MST
- investigating Aug 22, 2024, 10:49 PM UTC
We are continuing to investigate this issue. We'll be updating the status page at 8:51 PM MST
- investigating Aug 23, 2024, 02:42 AM UTC
We are continuing to investigate this issue. We'll be updating the status page at 12:51 AM MST
- investigating Aug 23, 2024, 06:51 AM UTC
We are continuing to investigate this issue. We'll be updating the status page at 4:51 AM MST
- resolved Aug 23, 2024, 10:11 AM UTC
We have found this issue to be mitigated and is only affecting a small subset of customers that we are working diligently to support and find a resolution. If you are experiencing issues, please don't hesitate to reach out to support.
S2 - Inability to Access Teem using O365 SSO
Timeline · 4 updates
We are investigating an issue with Teem
Timeline · 2 updates
- investigating Aug 19, 2024, 03:07 PM UTC
We are currently investigating an issue with Teem. We will update you when we have more information.
- resolved Aug 19, 2024, 03:24 PM UTC
This was an internal incident and has been resolved. Thank you for understanding.