Teem outages and incidents
Outage and incident data over the last 30 days for Teem.
There have been 0 outages or incidents for Teem in the last 30 days.
Severity Breakdown:
Tired of searching for status updates?
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowComponents and Services Monitored for Teem
Outlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| API | Active |
| Authentication (SSO) | Active |
| Datadog Events | Active |
| EventBoard | Active |
| Exchange Sync | Active |
| Google Apps Calendar | Active |
| LobbyConnect | Active |
| Mandrill US East | Active |
| Mandrill US West | Active |
| Mobile Data | Active |
| Phone System | Active |
| Support Articles | Active |
| Web Interface | Active |
Latest Teem outages and incidents.
View the latest incidents for Teem and check for official updates:
Office 365 and Exchange Sync Issues
Description: After our fix we have confirmed that Calendar Sync functionality has returned to normal.
Status: Resolved
Impact: Major | Started At: April 22, 2021, 9:29 a.m.
Updates:
-
Time: April 22, 2021, 4:55 p.m.Status: ResolvedUpdate: After our fix we have confirmed that Calendar Sync functionality has returned to normal.
-
Time: April 22, 2021, 4:16 p.m.Status: MonitoringUpdate: We have not see any Calendar Sync issues since the last update and functionality is retuning to normal. We are continuing to monitor and expect this be resolved shortly.
-
Time: April 22, 2021, 3:06 p.m.Status: MonitoringUpdate: Engineering has deployed a fix for this issue, O365 and Exchange calendars appear to have returned to normal. We will continue to monitor the logs for any recurring issues but we don't expect any at this time.
-
Time: April 22, 2021, 2:04 p.m.Status: IdentifiedUpdate: Engineering has isolated the issue to a single location and has visibility into the exact error. They are working on a solution and intend to have it in testing shortly. Our next update will be at 9MT
-
Time: April 22, 2021, 12:57 p.m.Status: InvestigatingUpdate: We continue to investigate the root cause of the issue. as of now, the incident is classified as S1. Hourly updates will be provided. Next update is on 8:00 AM. This is effecting only O365 and Exchange calendars at this time.
-
Time: April 22, 2021, 12:54 p.m.Status: InvestigatingUpdate: We continue to investigate the root cause of the issue. as of now, the incident is classified as S1. Hourly updates will be provided. Next update is on 8:00 AM.
-
Time: April 22, 2021, 11:20 a.m.Status: InvestigatingUpdate: Engineering is still investigating this issue.
-
Time: April 22, 2021, 9:29 a.m.Status: InvestigatingUpdate: We have received isolated reports from customers utilizing O365 and Exchange calendars and them not able being able to sync. Our Engineering team is currently investigating and an update will be provided at 5:30 AM MST.
O365 SSO & Google Calendar Functionality Impaired
Description: Earlier this month, we notified you of the unexpected technical challenges some customers experienced as a result of a major infrastructure upgrade for the Teem platform. We take performance and security very seriously, which is why we initiated the update to align with SOC 2 Type 2 data security standards. We appreciate your patience and understanding while we worked to resolve the temporary outages. Our first priority was to get you back up and running; our second is to give you some background on what happened. Here’s what we determined through our root cause analysis and how we’re preventing this moving forward. **Issue: O365 Sign-in Error 500** Cause: During a routine deployment, one of the third-party software libraries Teem SSO relies on was inadvertently upgraded to the latest major release of that library, which included noticeable changes. **Remediation**: · Reverted the library by specifying previous version with package management to avoid any unintentional upgrades **Issue: Post-Upgrade Device Connectivity** **Cause**: Teem’s core service had an interruption starting on Jan.9, 2021. During the interruption, when the EventBoard device made API calls to the service, the response status could be one of many error codes, including 401 Unauthorized. While this status code was in error, the device executed its designed security protocols and logged off. During a logout, EventBoard deletes all API tokens, downloaded themes, settings, and calendar data. It then reverts to a not-signed-in state and provides a 6-digit pin code for reactivation. Some customers were stuck on a “Authenticating with Teem …” screen. In these cases, after logging out EventBoard showed a message saying it could not communicate with Teem, and selecting “Retry” locked the app on that screen \(a secondary symptom of the core issue\). After logging out, the core service interruption would return an error instead of a pin code **Remediation**: · Deployed hotfix allowing devices to automatically activate and log in at pin code screen if they still exist in Teem database and are connected to only one Teem customer instance · Modified EventBoard app to increase fault tolerance on false 401s and to no longer get stuck at “Authenticating with Teem …” screen · Modified core service \(monolith\) so it doesn’t return 401s incorrectly **Issue:** [**App.Teem.com**](http://App.Teem.com) **Platform Outage** **Cause**: When deploying code on Jan. 14, 2021, an errant pip upgrade caused servers to not receive the deploying code and services to be stopped, interrupting all aspects of Teem. **Solutions**: · Updated deploy script to pin pip version · Cleared salt cache and confirmed correct deploy script on servers · Changed canary process to better detect downed servers · Ongoing: Updating underlying framework and all packages We apologize for any inconvenience and are continually working toward providing a more reliable experience for you. For additional information or to report an issue, please reach out to your Account Manager or visit [help.teem.com](http://help.teem.com) to contact our Customer Support team. Thank you
Status: Postmortem
Impact: Major | Started At: Jan. 15, 2021, 6:52 p.m.
Updates:
-
Time: Jan. 29, 2021, 10:16 p.m.Status: PostmortemUpdate: Earlier this month, we notified you of the unexpected technical challenges some customers experienced as a result of a major infrastructure upgrade for the Teem platform. We take performance and security very seriously, which is why we initiated the update to align with SOC 2 Type 2 data security standards. We appreciate your patience and understanding while we worked to resolve the temporary outages. Our first priority was to get you back up and running; our second is to give you some background on what happened. Here’s what we determined through our root cause analysis and how we’re preventing this moving forward. **Issue: O365 Sign-in Error 500** Cause: During a routine deployment, one of the third-party software libraries Teem SSO relies on was inadvertently upgraded to the latest major release of that library, which included noticeable changes. **Remediation**: · Reverted the library by specifying previous version with package management to avoid any unintentional upgrades **Issue: Post-Upgrade Device Connectivity** **Cause**: Teem’s core service had an interruption starting on Jan.9, 2021. During the interruption, when the EventBoard device made API calls to the service, the response status could be one of many error codes, including 401 Unauthorized. While this status code was in error, the device executed its designed security protocols and logged off. During a logout, EventBoard deletes all API tokens, downloaded themes, settings, and calendar data. It then reverts to a not-signed-in state and provides a 6-digit pin code for reactivation. Some customers were stuck on a “Authenticating with Teem …” screen. In these cases, after logging out EventBoard showed a message saying it could not communicate with Teem, and selecting “Retry” locked the app on that screen \(a secondary symptom of the core issue\). After logging out, the core service interruption would return an error instead of a pin code **Remediation**: · Deployed hotfix allowing devices to automatically activate and log in at pin code screen if they still exist in Teem database and are connected to only one Teem customer instance · Modified EventBoard app to increase fault tolerance on false 401s and to no longer get stuck at “Authenticating with Teem …” screen · Modified core service \(monolith\) so it doesn’t return 401s incorrectly **Issue:** [**App.Teem.com**](http://App.Teem.com) **Platform Outage** **Cause**: When deploying code on Jan. 14, 2021, an errant pip upgrade caused servers to not receive the deploying code and services to be stopped, interrupting all aspects of Teem. **Solutions**: · Updated deploy script to pin pip version · Cleared salt cache and confirmed correct deploy script on servers · Changed canary process to better detect downed servers · Ongoing: Updating underlying framework and all packages We apologize for any inconvenience and are continually working toward providing a more reliable experience for you. For additional information or to report an issue, please reach out to your Account Manager or visit [help.teem.com](http://help.teem.com) to contact our Customer Support team. Thank you
-
Time: Jan. 16, 2021, 12:54 a.m.Status: ResolvedUpdate: We have verified that the Google synch is back to normal performance. As such, this incident is now marked as resolved.
-
Time: Jan. 15, 2021, 11:10 p.m.Status: IdentifiedUpdate: The Engineering team has identified the source of the problem with Google Calendar functionality and are working to mitigate the problem. The next update will be provided at 8pm MST.
-
Time: Jan. 15, 2021, 9 p.m.Status: InvestigatingUpdate: At this time, SSO functionality has been restored and is operational. During the investigation process we have identified that Google Calendar functionality is impaired, therefore this incident will remain open. We will provide another update at 4pm MST regarding this component.
-
Time: Jan. 15, 2021, 6:52 p.m.Status: InvestigatingUpdate: We have received reports from a subset of customers utilizing O365 SSO are not able to authenticate into Teem products. Our Engineering team is currently investigating and an update will be provided at 2pm MST.
EventBoard and Customer Portal Service Disruption
Description: Earlier this month, we notified you of the unexpected technical challenges some customers experienced as a result of a major infrastructure upgrade for the Teem platform. We take performance and security very seriously, which is why we initiated the update to align with SOC 2 Type 2 data security standards. We appreciate your patience and understanding while we worked to resolve the temporary outages. Our first priority was to get you back up and running; our second is to give you some background on what happened. Here’s what we determined through our root cause analysis and how we’re preventing this moving forward. **Issue: O365 Sign-in Error 500** Cause: During a routine deployment, one of the third-party software libraries Teem SSO relies on was inadvertently upgraded to the latest major release of that library, which included noticeable changes. **Remediation**: · Reverted the library by specifying previous version with package management to avoid any unintentional upgrades **Issue: Post-Upgrade Device Connectivity** **Cause**: Teem’s core service had an interruption starting on Jan.9, 2021. During the interruption, when the EventBoard device made API calls to the service, the response status could be one of many error codes, including 401 Unauthorized. While this status code was in error, the device executed its designed security protocols and logged off. During a logout, EventBoard deletes all API tokens, downloaded themes, settings, and calendar data. It then reverts to a not-signed-in state and provides a 6-digit pin code for reactivation. Some customers were stuck on a “Authenticating with Teem …” screen. In these cases, after logging out EventBoard showed a message saying it could not communicate with Teem, and selecting “Retry” locked the app on that screen \(a secondary symptom of the core issue\). After logging out, the core service interruption would return an error instead of a pin code **Remediation**: · Deployed hotfix allowing devices to automatically activate and log in at pin code screen if they still exist in Teem database and are connected to only one Teem customer instance · Modified EventBoard app to increase fault tolerance on false 401s and to no longer get stuck at “Authenticating with Teem …” screen · Modified core service \(monolith\) so it doesn’t return 401s incorrectly **Issue:** [**App.Teem.com**](http://App.Teem.com) **Platform Outage** **Cause**: When deploying code on Jan. 14, 2021, an errant pip upgrade caused servers to not receive the deploying code and services to be stopped, interrupting all aspects of Teem. **Solutions**: · Updated deploy script to pin pip version · Cleared salt cache and confirmed correct deploy script on servers · Changed canary process to better detect downed servers · Ongoing: Updating underlying framework and all packages We apologize for any inconvenience and are continually working toward providing a more reliable experience for you. For additional information or to report an issue, please reach out to your Account Manager or visit [help.teem.com](http://help.teem.com) to contact our Customer Support team. Thank you
Status: Postmortem
Impact: Critical | Started At: Jan. 15, 2021, 2:43 a.m.
Updates:
-
Time: Jan. 29, 2021, 10:13 p.m.Status: PostmortemUpdate: Earlier this month, we notified you of the unexpected technical challenges some customers experienced as a result of a major infrastructure upgrade for the Teem platform. We take performance and security very seriously, which is why we initiated the update to align with SOC 2 Type 2 data security standards. We appreciate your patience and understanding while we worked to resolve the temporary outages. Our first priority was to get you back up and running; our second is to give you some background on what happened. Here’s what we determined through our root cause analysis and how we’re preventing this moving forward. **Issue: O365 Sign-in Error 500** Cause: During a routine deployment, one of the third-party software libraries Teem SSO relies on was inadvertently upgraded to the latest major release of that library, which included noticeable changes. **Remediation**: · Reverted the library by specifying previous version with package management to avoid any unintentional upgrades **Issue: Post-Upgrade Device Connectivity** **Cause**: Teem’s core service had an interruption starting on Jan.9, 2021. During the interruption, when the EventBoard device made API calls to the service, the response status could be one of many error codes, including 401 Unauthorized. While this status code was in error, the device executed its designed security protocols and logged off. During a logout, EventBoard deletes all API tokens, downloaded themes, settings, and calendar data. It then reverts to a not-signed-in state and provides a 6-digit pin code for reactivation. Some customers were stuck on a “Authenticating with Teem …” screen. In these cases, after logging out EventBoard showed a message saying it could not communicate with Teem, and selecting “Retry” locked the app on that screen \(a secondary symptom of the core issue\). After logging out, the core service interruption would return an error instead of a pin code **Remediation**: · Deployed hotfix allowing devices to automatically activate and log in at pin code screen if they still exist in Teem database and are connected to only one Teem customer instance · Modified EventBoard app to increase fault tolerance on false 401s and to no longer get stuck at “Authenticating with Teem …” screen · Modified core service \(monolith\) so it doesn’t return 401s incorrectly **Issue:** [**App.Teem.com**](http://App.Teem.com) **Platform Outage** **Cause**: When deploying code on Jan. 14, 2021, an errant pip upgrade caused servers to not receive the deploying code and services to be stopped, interrupting all aspects of Teem. **Solutions**: · Updated deploy script to pin pip version · Cleared salt cache and confirmed correct deploy script on servers · Changed canary process to better detect downed servers · Ongoing: Updating underlying framework and all packages We apologize for any inconvenience and are continually working toward providing a more reliable experience for you. For additional information or to report an issue, please reach out to your Account Manager or visit [help.teem.com](http://help.teem.com) to contact our Customer Support team. Thank you
-
Time: Jan. 15, 2021, 3:14 a.m.Status: ResolvedUpdate: At this time, our Engineers were able to identify the root cause of the incident and they have implemented a fix. We have verified all systems are operational. This will be monitored, however this incident will be marked resolved at this time. A formal Root Cause Analysis will be posted in the near future.
-
Time: Jan. 15, 2021, 2:43 a.m.Status: InvestigatingUpdate: We have received reports that EventBoard and the Product Portal are not responsive. This is a Severity 1 incident. Our engineering team is aware and an update will be posted at 9 PM MST if not before.
Performance Degraded / Devices Disconnected
Description: Earlier this month, we notified you of the unexpected technical challenges some customers experienced as a result of a major infrastructure upgrade for the Teem platform. We take performance and security very seriously, which is why we initiated the update to align with SOC 2 Type 2 data security standards. We appreciate your patience and understanding while we worked to resolve the temporary outages. Our first priority was to get you back up and running; our second is to give you some background on what happened. Here’s what we determined through our root cause analysis and how we’re preventing this moving forward. **Issue: O365 Sign-in Error 500** Cause: During a routine deployment, one of the third-party software libraries Teem SSO relies on was inadvertently upgraded to the latest major release of that library, which included noticeable changes. **Remediation**: · Reverted the library by specifying previous version with package management to avoid any unintentional upgrades **Issue: Post-Upgrade Device Connectivity** **Cause**: Teem’s core service had an interruption starting on Jan.9, 2021. During the interruption, when the EventBoard device made API calls to the service, the response status could be one of many error codes, including 401 Unauthorized. While this status code was in error, the device executed its designed security protocols and logged off. During a logout, EventBoard deletes all API tokens, downloaded themes, settings, and calendar data. It then reverts to a not-signed-in state and provides a 6-digit pin code for reactivation. Some customers were stuck on a “Authenticating with Teem …” screen. In these cases, after logging out EventBoard showed a message saying it could not communicate with Teem, and selecting “Retry” locked the app on that screen \(a secondary symptom of the core issue\). After logging out, the core service interruption would return an error instead of a pin code **Remediation**: · Deployed hotfix allowing devices to automatically activate and log in at pin code screen if they still exist in Teem database and are connected to only one Teem customer instance · Modified EventBoard app to increase fault tolerance on false 401s and to no longer get stuck at “Authenticating with Teem …” screen · Modified core service \(monolith\) so it doesn’t return 401s incorrectly **Issue:** [**App.Teem.com**](http://App.Teem.com) **Platform Outage** **Cause**: When deploying code on Jan. 14, 2021, an errant pip upgrade caused servers to not receive the deploying code and services to be stopped, interrupting all aspects of Teem. **Solutions**: · Updated deploy script to pin pip version · Cleared salt cache and confirmed correct deploy script on servers · Changed canary process to better detect downed servers · Ongoing: Updating underlying framework and all packages We apologize for any inconvenience and are continually working toward providing a more reliable experience for you. For additional information or to report an issue, please reach out to your Account Manager or visit [help.teem.com](http://help.teem.com) to contact our Customer Support team. Thank you
Status: Postmortem
Impact: Minor | Started At: Jan. 12, 2021, 2:02 a.m.
Updates:
-
Time: Jan. 29, 2021, 10:17 p.m.Status: PostmortemUpdate: Earlier this month, we notified you of the unexpected technical challenges some customers experienced as a result of a major infrastructure upgrade for the Teem platform. We take performance and security very seriously, which is why we initiated the update to align with SOC 2 Type 2 data security standards. We appreciate your patience and understanding while we worked to resolve the temporary outages. Our first priority was to get you back up and running; our second is to give you some background on what happened. Here’s what we determined through our root cause analysis and how we’re preventing this moving forward. **Issue: O365 Sign-in Error 500** Cause: During a routine deployment, one of the third-party software libraries Teem SSO relies on was inadvertently upgraded to the latest major release of that library, which included noticeable changes. **Remediation**: · Reverted the library by specifying previous version with package management to avoid any unintentional upgrades **Issue: Post-Upgrade Device Connectivity** **Cause**: Teem’s core service had an interruption starting on Jan.9, 2021. During the interruption, when the EventBoard device made API calls to the service, the response status could be one of many error codes, including 401 Unauthorized. While this status code was in error, the device executed its designed security protocols and logged off. During a logout, EventBoard deletes all API tokens, downloaded themes, settings, and calendar data. It then reverts to a not-signed-in state and provides a 6-digit pin code for reactivation. Some customers were stuck on a “Authenticating with Teem …” screen. In these cases, after logging out EventBoard showed a message saying it could not communicate with Teem, and selecting “Retry” locked the app on that screen \(a secondary symptom of the core issue\). After logging out, the core service interruption would return an error instead of a pin code **Remediation**: · Deployed hotfix allowing devices to automatically activate and log in at pin code screen if they still exist in Teem database and are connected to only one Teem customer instance · Modified EventBoard app to increase fault tolerance on false 401s and to no longer get stuck at “Authenticating with Teem …” screen · Modified core service \(monolith\) so it doesn’t return 401s incorrectly **Issue:** [**App.Teem.com**](http://App.Teem.com) **Platform Outage** **Cause**: When deploying code on Jan. 14, 2021, an errant pip upgrade caused servers to not receive the deploying code and services to be stopped, interrupting all aspects of Teem. **Solutions**: · Updated deploy script to pin pip version · Cleared salt cache and confirmed correct deploy script on servers · Changed canary process to better detect downed servers · Ongoing: Updating underlying framework and all packages We apologize for any inconvenience and are continually working toward providing a more reliable experience for you. For additional information or to report an issue, please reach out to your Account Manager or visit [help.teem.com](http://help.teem.com) to contact our Customer Support team. Thank you
-
Time: Jan. 14, 2021, 10:35 p.m.Status: ResolvedUpdate: Our Engineering team has identified a solution to the current incident. A separate communication has been sent to customers who we believe were impacted by this incident. Please contact our support team at help.teem.com if you are still experiencing issues and did not receive additional communication from us. We will be posting a Root Cause Analysis of this incident in the immediate future. At this time, we will close this incident as resolved.
-
Time: Jan. 14, 2021, 7:07 p.m.Status: InvestigatingUpdate: At this time, we have identified the subset of customers who are affected by this incident. We will continue to investigate the root cause of the incident and our Engineers are monitoring the system for any additional issues. Customers that we believe are affected will receive additional communication in the next two hours.
-
Time: Jan. 14, 2021, 5 p.m.Status: InvestigatingUpdate: Our engineers are continuing to investigate the current incident. The next update will be provided at 12pm MST.
-
Time: Jan. 14, 2021, 2:54 p.m.Status: InvestigatingUpdate: Our engineers are continuing to investigate the current incident. The next update will be provided at 10am MST.
-
Time: Jan. 14, 2021, 1:01 p.m.Status: InvestigatingUpdate: We continue to investigate the current incident and another update will be provided at 8am MST.
-
Time: Jan. 14, 2021, 11:02 a.m.Status: InvestigatingUpdate: Our engineers continue to investigate the current incident. Another update with be provided at 6am MST.
-
Time: Jan. 14, 2021, 9:06 a.m.Status: InvestigatingUpdate: We are continuing to investigate and will provide another update at 4am MST.
-
Time: Jan. 14, 2021, 7:31 a.m.Status: InvestigatingUpdate: We are continuing to investigate and will provide another update at 2am MST.
-
Time: Jan. 14, 2021, 5:02 a.m.Status: InvestigatingUpdate: We are continuing to investigate and will provide another update at 12 am MST.
-
Time: Jan. 14, 2021, 2:48 a.m.Status: InvestigatingUpdate: We are continuing to investigate and will provide another update at 10pm MST.
-
Time: Jan. 13, 2021, 11:58 p.m.Status: InvestigatingUpdate: Our Engineering team is continuing their investigation to identify the root cause of this issue. We will provide another update at 7pm MST”.
-
Time: Jan. 13, 2021, 9:51 p.m.Status: InvestigatingUpdate: At this time, our monitoring has indicated that performance has improved significantly. However, we are receiving reports of devices that are disconnected from Teem servers. Our reports indicate that this is affecting a subset of our customers. Given the impact to these customers, we are elevating this incident to a Severity 1. As a Severity 1 incident, we will provide updates every two hours. We ask affected customers to reach out to Teem support at help.teem.com if they have not done so previously
-
Time: Jan. 13, 2021, 1:44 a.m.Status: MonitoringUpdate: At this time, performance has improved and we will continue to monitor. We will be sending communication to customers who have been known to be affected by this incident. If you are still experiencing issues, contact support at help.teem.com.
-
Time: Jan. 12, 2021, 10:04 p.m.Status: MonitoringUpdate: At this time we are continuing to monitoring performance and stability. Next update will be at 7pm MST.
-
Time: Jan. 12, 2021, 6:01 p.m.Status: MonitoringUpdate: Our Engineering team continues to make performance enhancements and we are seeing improvements with functionality. Engineering will continue to monitor system stability and performance. The next update will be at 3pm MST.
-
Time: Jan. 12, 2021, 2:02 p.m.Status: MonitoringUpdate: The engineering team has identified an area of reduced performance and is in the process of making configuration adjustments to remove it from the system. This should result in improvements for most customers. The system will continue to be monitored for any further degradation and our next update will be at 1100 Hours MST.
-
Time: Jan. 12, 2021, 2:02 a.m.Status: InvestigatingUpdate: We are continuing to investigate this issue.
-
Time: Jan. 12, 2021, 2:02 a.m.Status: InvestigatingUpdate: We have received reports of performance issues on Teem Products and devices that are becoming disconnected from the server. Our Engineers are investigating the issues. Next update will be provided at 0700 Hours MST 1/12/20.
Office 365 Authentication Errors
Description: The issue was fixed and normal operations resumed at approximately 7:00pm MT on Sept. 8. Teem has been monitoring sync traffic since that time. After working with vendors to eliminate possible problems and bottlenecks, a subtle networking issue with the hosting platform itself was discovered. The issue left the subsystems that handle calendar synchronization for Office 365 and Exchange clients in a partially working state with most networking successfully transacting but many or our O365 clients heavily affected. Replacement VMs were created, tested and deployed to clear any underlying issues with the networking, hypervisor or hardware.
Status: Resolved
Impact: Major | Started At: Sept. 8, 2020, 1:39 p.m.
Updates:
-
Time: Sept. 9, 2020, 1:39 p.m.Status: ResolvedUpdate: The issue was fixed and normal operations resumed at approximately 7:00pm MT on Sept. 8. Teem has been monitoring sync traffic since that time. After working with vendors to eliminate possible problems and bottlenecks, a subtle networking issue with the hosting platform itself was discovered. The issue left the subsystems that handle calendar synchronization for Office 365 and Exchange clients in a partially working state with most networking successfully transacting but many or our O365 clients heavily affected. Replacement VMs were created, tested and deployed to clear any underlying issues with the networking, hypervisor or hardware.
-
Time: Sept. 8, 2020, 9:13 p.m.Status: InvestigatingUpdate: Teem has determined that connections to the EWS API for Office365 clients are unavailable and the team is working with Microsoft to determine the root cause and resolution of the issue.
-
Time: Sept. 8, 2020, 6:39 p.m.Status: InvestigatingUpdate: Our engineering team is continuing to work diligently in identifying the root cause of these issues so that we can provide a solution immediately. We will provide updates as they become available.
-
Time: Sept. 8, 2020, 1:39 p.m.Status: InvestigatingUpdate: We are aware of an issue affecting some customers using Office 365 calendar sync for room calendars. An authentication error presents itself when attempting to sync room calendars or authenticate using an Office 365 account on the Teem platform.
