TSC System Status
Welcome to the Information Technology system status page for Tallahassee State College. This page provides up-to-date information about the operations of key TSC IT systems.
Last Checked:
Enterprise Applications:
2026/10/06 03:46 PM (Success)
Microsoft 365:
2026/10/06 03:47 PM (Success)
Miscellaneous:
2026/10/06 03:46 PM (Success)
Workday:
2026/10/06 03:31 PM (Success)
Service Degradation
System: VisitorAware Started: 10/05/2026 06:30 PM Last Updated: 10/06/2026 02:40 PM Feature: VisitorAware (SingleWire) Issue Id: zsv798x4lvp8 Status: Service Degradation Post Type: Regular
Update - We are continuing to monitor for any further issues.
Oct 06, 2026 - 13:37 CDT
Oct 06, 2026 - 13:37 CDT
Monitoring - A fix has been implemented and we are monitoring the results.
Oct 06, 2026 - 13:37 CDT
Oct 06, 2026 - 13:37 CDT
Identified - iOS users who start a Mobile Panic Button or choose a response that turns on location tracking are not having their location shared, and responders will not see them on the tracking map.
A root cause has been identified and we plan to deploy a fix as soon as possible. We apologize for the disruption in service.
Oct 05, 2026 - 17:26 CDT
A root cause has been identified and we plan to deploy a fix as soon as possible. We apologize for the disruption in service.
Oct 05, 2026 - 17:26 CDT
System: Email Started: 09/27/2026 10:36 PM Last Updated: 10/05/2026 08:20 PM Feature: Mailflow - delayed sending to Internet Issue Id: EX1483619 Status: Service Degradation Post Type: Regular
Title: Some users' email with DocuSign URLs may not be delivered and may be quarantined due to URL reputation
User impact: Users' email with DocuSign URLs may not have been delivered and may have been quarantined due to URL reputation.
Final status: We've completed manual mitigation of the remaining affected messages and completed implementation of adjustments to our ML model to ensure its correctly sorting email messages containing DocuSign URLs while maintaining the ability to identify and prevent harmful content from reaching users. We've validated from our service telemetry and from a subset of reporting affected users that impact is remediated.
Scope of impact: This issue may have affected some users attempting to send emails with DocuSign URLs, who may have seen messages not being delivered and quarantined due to URL reputation.
Start time: Monday, September 28, 2026, at 2:36 AM UTC
End time: Thursday, October 1, 2026, at 11:59 PM UTC
Root cause: The Microsoft URL evaluation process was incorrectly identifying the affected messages as potentially malicious due to the URL inclusion, resulting in impact.
Next steps: - We're analyzing our URL evaluation process to validate what additional changes we can implement to ensure similar impact scenarios don't occur in the future while also protecting Exchange Online users from potentially malicious senders.
This is the final update for the event.
System: Microsoft Teams Started: 09/25/2026 04:09 PM Last Updated: 10/05/2026 06:15 PM Feature: Calling Issue Id: TM1488543 Status: Service Degradation Post Type: Regular
Title: Some users conferenced into a Microsoft Teams emergency call may not be automatically muted or able to mute themselves
User impact: Users conferenced into a Microsoft Teams emergency call may not be automatically muted or able to mute themselves.
More info: Users conferenced into a Microsoft Teams emergency call are also unable to mute themselves and would need to leave the call.
Current status: We've initiated deployment of our code change to address the code mismatch causing users to not be automatically muted as expected or being able to mute themselves in emergency calls. We anticipate deployment to be completed by Monday, October 12, 2026, and we aim to provide updates on our timeline to remediation as deployment progresses.
Scope of impact: Users conferenced into a Microsoft Teams emergency call and attempting to mute their audio are affected by this issue. This section may be updated as the investigation progresses.
Start time: Friday, September 25, 2026, at 8:09 PM UTC
Estimated time to resolve: We anticipate impact to be resolved by Monday, October 12, 2026.
Root cause: A code mismatch in the components utilized when marking a Microsoft Teams emergency call as a multi-party call is causing the code to mute participants to not be enabled as expected.
Next update by: Friday, October 9, 2026, at 11:00 PM UTC
System: Email Started: 09/25/2026 11:52 AM Last Updated: 10/05/2026 07:32 PM Feature: All clients Issue Id: EX1479349 Status: Service Degradation Post Type: Regular
Title: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online
User impact: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online.
More info: As a temporary alternative, impacted users may reply or reply all to email messages through user inboxes.
Current status: Our fix deployment is nearing completion, and most affected users should now be experiencing recovery. We’ll continue monitoring the deployment to ensure it completes and restores service for all affected users.
Scope of impact: This issue impacts any user attempting to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online. This information may be updated as our investigation continues.
Next update by: Wednesday, October 7, 2026, at 1:00 AM UTC