Exoprise continuously monitors the operations of its service — using synthetic sensors from all over the world, in addition to real-user monitoring from everywhere. If there are any interruptions in service, planned or unplanned, a note will be posted here.
| Core Servers | Public Sites | Alarms | Dependant Services | Service Comms API |
|---|---|---|---|---|
 | | | | |
Monday, August 12th 8:30 PM
Microsoft has updated the status of TM859179 indicating that they believe the situation has resolved itself. Sensor performance has improved.
https://admin.microsoft.com/#/servicehealth/:/alerts/TM859179
Monday, August 12th 4:43 PM
Microsoft continues to vaguely report issues with their Team’s infrastructure under the ticket TM859179, but details that they “suspect a third-party Internet Service Provider (ISP)…”.
The issue does seem to be improving a little, but for some customers there are still Teams AV outages.
Monday, August 12th 9:00 AM
Microsoft is reporting issues with Teams in tickets TM859179 and TM859168 but now reporting false positives. They sometimes do this until they really realize and discover what the problem is.
Sunday, August 11th 11:40 AM
We have reported the BOT infrastructure issue to Microsoft. Adding BOT capacity hasn’t improved the issue at this time.
Sunday, August 11th 7:00 AM
We have expanded the BOTs in order to deal with slower Azure capacity and will continue to watch the performance closely.
Saturday, August 10th 9:00 PM
We are examining capacity and utilization issues with the Teams AV BOT. We will closely monitor the issue until the next update.
Monday, April 1st 2024 6:00 PM
A fix for the latest “Targeted version” of OneDrive for Business has been released. OneDrive for Business sensors should receive the rolling updates within the next few hours.
Monday, April 1st 2024 12:00 PM
We have reverted a fix for OneDrive for Business related to an update. We should have a solution for old and new versions this afternoon or by tomorrow at the latest. We still do see Teams V2 instability related to the turnover.
Monday, April 1st 2024 9:00 AM
OneDrive for Business is experiencing issues related to updates. We are investigating. Teams V2 rollout is causing elevated connection problems.
Tuesday, March 12th 2024 5:00 PM
Teams V2 stats and navigation for synthetics should be mostly fixed and working in production (ahead of the final switchover). There are periodic navigation and resource issues still being addressed. Teams V2 automatic teams creation is not currently supported and will be forthcoming. Create the Team/Channel before setting up the sensor.
Monday, March 11th 2024 5:00 PM
Progress has been made on handling Teams V2 WebRtc stats and should be greatly improved from the synthetic tests. There still remain navigation and resource issues that we believe are related to V2 scaling and capacity so we are investigating.
Thursday, March 7th, 2024 4:00 PM
We continue to investigate timing and setup issues for WebRtc synthetic statistics under the new Teams V2. We expect to have more to report within the next 1 to 2 days and continue to recommend staying on Teams V1.
Wednesday, March 6th, 2024 3:00 PM
While we continue to investigate the lack of synthetic WebRtc statistics from the Teams V2 servers, we recommend forcing sensor accounts to be Teams v1.
Wednesday, March 6th, 2024 10:00 AM
The forced switch to Teams V2 from Microsoft is causing BOT joining issues, and we continue to investigate the issue.
Tuesday, March 5th, 2024 3:00 PM
We are investigating issues with RTC / WebRtc stat collection from the Teams AV sensors due to forced Teams V2 upgrades from Microsoft. We hope to have to have additional information by the end of the day.