Teem Outage History

Teem is up right now

Teem had 10 outages in the last 2 years totaling 694h 9m of downtime — averaging 0.4 incidents per month.

There were 10 Teem outages since June 12, 2024 totaling 694h 9m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.teem.com

Major March 4, 2025

S1 - TEEM Performance Issues

Detected by Pingoru
Mar 04, 2025, 02:19 PM UTC
Resolved
Mar 05, 2025, 06:31 PM UTC
Duration
1d 4h
Affected: Web InterfaceMobile DataAPIGoogle Apps CalendarExchange SyncSupport ArticlesMandrill US EastMandrill US WestEventBoardPhone SystemLobbyConnectAuthentication (SSO)Datadog Events
Timeline · 8 updates

Read the full incident report →

Critical August 22, 2024

Calendar Sync issues

Detected by Pingoru
Aug 22, 2024, 05:51 PM UTC
Resolved
Aug 23, 2024, 10:11 AM UTC
Duration
16h 20m
Affected: Google Apps CalendarExchange Sync
Timeline · 6 updates
  1. 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.

  2. 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

  3. 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

  4. 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

  5. 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

  6. 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.

Read the full incident report →

Notice August 19, 2024

We are investigating an issue with Teem

Detected by Pingoru
Aug 19, 2024, 03:07 PM UTC
Resolved
Aug 19, 2024, 03:24 PM UTC
Duration
17m
Timeline · 2 updates
  1. 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.

  2. resolved Aug 19, 2024, 03:24 PM UTC

    This was an internal incident and has been resolved. Thank you for understanding.

Read the full incident report →

Notice June 12, 2024

S2 - Teem Insights Not Generating Data

Detected by Pingoru
Jun 12, 2024, 05:11 PM UTC
Resolved
Jun 14, 2024, 06:37 PM UTC
Duration
2d 1h
Timeline · 8 updates
  1. investigating Jun 12, 2024, 05:11 PM UTC

    We are currently investigating an issue with Insights not generating data. Our internal team is currently investigating to determine the cause of the disruption. The next update will be posted at 4:10pm CST.

  2. investigating Jun 12, 2024, 09:14 PM UTC

    We are continuing to investigate this issue.

  3. investigating Jun 13, 2024, 02:05 AM UTC

    We are continuing to investigate this issue.

  4. investigating Jun 13, 2024, 06:59 AM UTC

    We are continuing to investigate this issue.

  5. investigating Jun 13, 2024, 12:55 PM UTC

    We are continuing to investigate this issue.

  6. investigating Jun 13, 2024, 05:13 PM UTC

    We are continuing to investigate this issue.

  7. investigating Jun 13, 2024, 09:20 PM UTC

    Our engineering team continues to investigate the inability pull data from Insights. We appreciate your patience as we work through this.

  8. resolved Jun 14, 2024, 06:37 PM UTC

    We appreciate your patience and are pleased to share that our team has identified the source of the Insight data disruption and is implementing a fix. We are responding directly to open tickets with details on the resolution for specific customer environments and will continue to monitor overall Insights performance. For further questions, please reach out to our dedicated support team. Thank you.

Read the full incident report →