Finalsite Outage History

Started Oct 21, 2026, 07:02 PM UTC· resolved Oct 22, 2026, 01:28 AM UTC

1. investigating Oct 21, 2026, 07:02 PM UTC

   Our team is investigating reports of performance/availability problems on your website. We will provide additional information as soon as possible.

2. monitoring Oct 21, 2026, 07:30 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Oct 22, 2026, 01:28 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 01, 2026, 04:25 PM UTC· resolved Sep 02, 2026, 12:21 PM UTC

1. investigating Sep 01, 2026, 04:25 PM UTC

   We are currently investigating issues with a subset of Composer websites in the US Central. We are working to analyze and mitigate this problem. More updates to follow shortly.

2. monitoring Sep 01, 2026, 05:30 PM UTC

   We are seeing performance improved at this time across all US Central websites, and we are continuing to monitor.

3. resolved Sep 02, 2026, 12:21 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 16, 2026, 10:03 PM UTC· resolved Aug 17, 2026, 08:15 PM UTC

1. investigating Aug 16, 2026, 10:03 PM UTC

   We are currently investigating an issue that is causing SMS messages to stall in the outbox. Our engineering team is actively investigating this matter to identify the root cause. Further updates will be provided as soon as more information becomes available.

2. investigating Aug 17, 2026, 12:23 AM UTC

   We are currently investigating an issue affecting SMS delivery due to a service disruption with an upstream infrastructure partner. Impact: Messages may remain in your outbox with a "sending" status for longer than usual, or they may fail to deliver entirely. We are actively working with our partner to restore full service.

3. monitoring Aug 17, 2026, 12:38 PM UTC

   Our upstream SMS partner is no longer observing any further issues, but they continue to monitor their services closely. Outgoing SMS delivery is returning to normal, and our team will continue monitoring delivery rates to ensure stability.

4. resolved Aug 17, 2026, 08:15 PM UTC

   SMS delivery has remained normal throughout the day, with no further disruptions reported by our upstream provider. This incident has been resolved.

Read the full incident report →

Started Aug 13, 2026, 01:52 PM UTC· resolved Aug 14, 2026, 01:41 PM UTC

1. investigating Aug 13, 2026, 01:52 PM UTC

   We're investigating an issue that is causing incorrect dashboard numbers and searches to not populate correctly.

2. identified Aug 13, 2026, 10:17 PM UTC

   The issue has been identified. We're working through reindexing all EMS sites gradually.

3. resolved Aug 14, 2026, 01:41 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 07, 2026, 12:42 PM UTC· resolved Aug 07, 2026, 03:34 PM UTC

1. investigating Aug 07, 2026, 12:42 PM UTC

   We're currently investigating an issue with Composer sites. We'll provide more updates here as they become available.

2. monitoring Aug 07, 2026, 01:09 PM UTC

   We're seeing sites stabilize and are continuing to monitor the situation.

3. resolved Aug 07, 2026, 03:34 PM UTC

   This incident has been resolved. We apologize for the inconvenience.

Read the full incident report →

Started Jul 02, 2026, 05:44 PM UTC· resolved Jul 02, 2026, 08:46 PM UTC

1. investigating Jul 02, 2026, 05:44 PM UTC

   We are currently investigating this issue.

2. identified Jul 02, 2026, 05:59 PM UTC

   Parents and admins that sign into FS Enrollment using Microsoft (Azure) Login are currently not able to access the application and will see a red error message upon attempting to log in. We have identified the cause of the issue and are working to quickly remediate this. Thank you for your patience & understanding.

3. resolved Jul 02, 2026, 08:46 PM UTC

   Тhe incident has been resolved and login through Microsoft (Azure) is now restored.

Read the full incident report →

Started Jun 04, 2026, 05:11 PM UTC· resolved Jun 05, 2026, 06:36 PM UTC

1. investigating Jun 04, 2026, 05:11 PM UTC

   We are currently experiencing a 504 Gateway Timeout error, which is preventing some users from accessing the site. Our engineering team is actively investigating the root cause. We sincerely apologize for the disruption and will provide another update as soon as we have more information.

2. investigating Jun 04, 2026, 06:40 PM UTC

   Our engineering team is continuing to actively investigate the root cause of the 504 Gateway Timeout errors preventing access to the platform. We are treating this issue with the highest priority and are working diligently to resolve it as quickly as possible. We will provide regular progress updates on this page as the investigation continues. If you have an urgent message that cannot wait until the system is fully restored, we have an alternative platform available to send it on your behalf. To initiate this, the request must come directly from an Account Admin (Super User Top) Please contact our support team with the following: -Message Details: Provide the exact message content and your desired delivery channels (SMS, Email, etc.). -Recipient File: Email us a file containing the recipient addresses (phone/SMS numbers or email addresses). -Data Security: For your security, please send this file as a password-protected .zip file. -File Password: Provide the password for the .zip file to our support team by phone so we can securely access it and queue your message. Thank you for your continued patience and understanding while we work through this.

3. identified Jun 04, 2026, 08:58 PM UTC

   We've identified the issue and are working to restore service.

4. identified Jun 05, 2026, 12:13 AM UTC

   Access to the application has been restored, but we are continuing to address residual issues involving UI performance, Email, and SMS sending. We are actively working to restore full functionality and will provide further updates here as soon as we have them.

5. monitoring Jun 05, 2026, 11:27 AM UTC

   A fix has been implemented and our team is monitoring the results to ensure all functionality is working as expected.

6. resolved Jun 05, 2026, 06:36 PM UTC

   After extensive monitoring, we have confirmed that the system is running as expected.

Read the full incident report →

Started May 18, 2026, 01:44 PM UTC· resolved May 18, 2026, 03:20 PM UTC

1. investigating May 18, 2026, 01:44 PM UTC

   We are currently investigating an issue where users are receiving an error message when attempting to add or change images within the Messages editor. Our team is aware of the problem and is actively working on a resolution. We apologize for the inconvenience and will provide another update as soon as we have more information.

2. resolved May 18, 2026, 03:20 PM UTC

   This incident has been resolved and our team has confirmed that image editing functionality has been restored.

Read the full incident report →

Started May 13, 2026, 05:03 PM UTC· resolved May 13, 2026, 06:52 PM UTC

1. investigating May 13, 2026, 05:03 PM UTC

   Our team is aware of an issue impacting the ability to reach our Support teams via our dedicated phone lines. We are monitoring the situation with our provider and will provide an additional update as soon as possible. Email and tickets submitted via the Support Portal form are reaching us as expected at this time.

2. identified May 13, 2026, 06:07 PM UTC

   We are continuing to monitor the issue impacting our voice provider, and will pass along additional updates as soon as possible. Support requests submitted via email or ticketing forms continue to reach our teams as expected at this time.

3. monitoring May 13, 2026, 06:38 PM UTC

   Our voice provider has advised of a fix for this issue, and we are once again seeing calls to our Support lines connecting as expected. We appreciate your patience.

4. resolved May 13, 2026, 06:52 PM UTC

   This issue has been resolved.

Read the full incident report →

Started May 06, 2026, 07:41 PM UTC· resolved May 07, 2026, 07:08 PM UTC

1. investigating May 06, 2026, 07:41 PM UTC

   We are currently investigating issues with Composer performance in the US Central region. We are working to analyze and mitigate this problem. More updates to follow shortly.

2. monitoring May 06, 2026, 08:39 PM UTC

   Performance has stabilized in the US Central region, and our team is continuing to monitor at this time. If you are still seeing any issues, please contact Composer Support.

3. resolved May 07, 2026, 07:08 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 28, 2026, 03:00 PM UTC· resolved May 01, 2026, 12:06 PM UTC

1. investigating Apr 28, 2026, 03:00 PM UTC

   Our team discovered an issue that causes phone messages using “Text to Speech” to not deliver as expected. Call-In to Record as well as all other delivery methods are functioning as expected. If you are unable to record an audio message, please reach out to support and we will assist you in creating the message. Our development team is working to resolve the issue as quickly as possible.

2. resolved May 01, 2026, 12:06 PM UTC

   Our team has successfully resolved the technical issue that prevented Text-to-Speech messages from being delivered correctly. Thank you for your patience while we worked to get this back up and running.

Read the full incident report →

Started Mar 23, 2026, 04:01 PM UTC· resolved Mar 24, 2026, 05:44 PM UTC

1. identified Mar 23, 2026, 04:01 PM UTC

   Open dates in our Sent Emails page are currently empty due to an intermittent issue with our external email delivery provider. We are working with our email provider to resolve the issue as soon as possible. Emails are still being successfully sent and opened by recipients.

2. monitoring Mar 24, 2026, 05:33 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Mar 24, 2026, 05:44 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 27, 2026, 05:00 PM UTC· resolved Feb 27, 2026, 11:08 PM UTC

1. investigating Feb 27, 2026, 05:00 PM UTC

   We're currently investigating an increase in errors on Composer sites. We'll continue to provide more information as it becomes available. We apologize for the inconvenience.

2. identified Feb 27, 2026, 05:35 PM UTC

   We've identified the issue and are working to restore service.

3. identified Feb 27, 2026, 06:37 PM UTC

   We are continuing to work to restore full functionality. We are noting impacts to logins and a subset of Composer features. We will post another update within the next half hour.

4. monitoring Feb 27, 2026, 07:15 PM UTC

   Service has been restored at this time, and we are continuing to monitor. Site logins and Composer features should be operating as expected.

5. resolved Feb 27, 2026, 11:08 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 22, 2026, 10:59 PM UTC· resolved Feb 23, 2026, 12:56 AM UTC

1. investigating Feb 22, 2026, 10:59 PM UTC

   Our development team has identified an issue that is causing message creation to get stuck in Initializing and not complete for a subset of clients. We are working to resolve this as quickly as possible.

2. resolved Feb 23, 2026, 12:56 AM UTC

   Our development team has resolved the issue and all services are functioning as expected.

Read the full incident report →

Started Feb 19, 2026, 05:24 PM UTC· resolved Feb 20, 2026, 02:21 PM UTC

1. investigating Feb 19, 2026, 05:24 PM UTC

   Our team is investigating SMS sending delays and degraded performance.

2. monitoring Feb 19, 2026, 06:29 PM UTC

   We are seeing performance return to normal and will continue to closely monitor the situation.

3. monitoring Feb 19, 2026, 09:53 PM UTC

   SMS Message sending remains stable. Our team will continue to closely monitor the situation.

4. monitoring Feb 19, 2026, 10:20 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Feb 20, 2026, 02:21 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 12, 2026, 02:03 PM UTC· resolved Feb 12, 2026, 09:36 PM UTC

1. investigating Feb 12, 2026, 02:03 PM UTC

   Our team is aware of sending delays from the Messages/XR platforms, impacting a subset of clients in the US East hosting region. We are working to address this issue and will provide additional updates as soon as possible.

2. identified Feb 12, 2026, 05:40 PM UTC

   The issue causing the message delivery delays for US East clients has been identified. We will provide an additional update as soon as possible.

3. monitoring Feb 12, 2026, 06:57 PM UTC

   We are seeing message sends process as expected at this time. Our team is continuing to monitor.

4. resolved Feb 12, 2026, 09:36 PM UTC

   This issue, which caused sending delays impacting a subset of clients in the US East hosting region, has been resolved.

Read the full incident report →

Started Feb 10, 2026, 03:08 PM UTC· resolved Feb 11, 2026, 11:28 PM UTC

1. investigating Feb 10, 2026, 03:08 PM UTC

   We are aware of an issue preventing images from displaying as expected on Composer websites, impacting a subset of US Central clients. We are working to resolve this issue and will provide additional updates as soon as possible.

2. identified Feb 10, 2026, 07:35 PM UTC

   The root cause of this issue has been identified, and our team is working to implement a fix. We will provide additional updates as soon as possible.

3. monitoring Feb 11, 2026, 01:34 PM UTC

   A fix was deployed overnight, and as of 7:00 AM CST, all affected sites have been updated to the latest version. We are continuing to monitor performance. If you continue to experience issues, please contact Support. Thank you for your patience.

4. resolved Feb 11, 2026, 11:28 PM UTC

   This issue has been resolved.

Read the full incident report →

Started Jan 22, 2026, 06:21 PM UTC· resolved Jan 24, 2026, 07:59 PM UTC

1. investigating Jan 22, 2026, 06:21 PM UTC

   We are currently investigating an issue that is preventing users from scheduling messages. Affected users receive an error message stating: "Unfortunately, we are currently unable to schedule this message. Please contact our Support Department for assistance with this issue." This is being caused by a timeout within our automated content security scanner. The tool is currently failing to complete its safety scan for certain messages, preventing the message from being scheduled. This issue is impacting all clients except those in the US West region. Workaround: Our team has identified that re-uploading image assets directly into the message can bypass the timeout. If you need to send an urgent message, please follow these steps: 1. Capture Image URLs: Copy the resource URL for each image currently in your message. 2. Download Images: Open the URLs in a new browser tab, right-click, and "Save Image As" to your desktop. 3. Clean the Message: In your message editor, remove the current images and the entire row they were housed in one image and row at a time. 4. Rebuild & Upload: Re-add the row(s) and the Image Element. Drag and drop the saved images from your computer into the message. 5. Finalize: Click Update, proceed to Message Details, and attempt to Schedule Send. We apologize for this significant inconvenience. Our engineering team is currently working to restore normal service.

2. identified Jan 23, 2026, 07:26 PM UTC

   Our engineering team has identified the cause of the error that is preventing users from scheduling and sending messages. A fix for this issue is scheduled for deployment early next week. Until the fix is live, the "Unable to Schedule" error remains a possibility for all regions except US West and US Central. If you need to send an urgent message before early next week, please continue to use the following workaround: 1. Capture Image URLs: Copy the resource URL for each image currently in your message. 2. Download Images: Open the URLs in a new browser tab, right-click, and "Save Image As" to your desktop. 3. Clean the Message: In your message editor, remove the current images and the entire row they were housed in one image and row at a time. 4. Rebuild & Upload: Re-add the row(s) and the Image Element. Drag and drop the saved images from your computer into the message. 5. Finalize: Click Update, proceed to Message Details, and attempt to Schedule Send. We understand this adds additional manual effort to your workflow and appreciate your continued patience. We will provide a final update once the fix has been successfully implemented.

3. resolved Jan 24, 2026, 07:59 PM UTC

   This incident has been resolved. If you observe any future issues, please contact Finalsite Support.

Read the full incident report →

Started Jan 22, 2026, 06:11 PM UTC· resolved Jan 23, 2026, 03:24 PM UTC

1. investigating Jan 22, 2026, 06:11 PM UTC

   We are currently investigating an issue affecting the group selection interface when creating an Important Announcement. This issue specifically impacts a subset of clients in our US West region. While affected users can still select groups and send messages, the selection list currently displays all groups (including archived ones) in a long list format. We understand this makes selecting groups difficult, and we are working to restore the group selection layout. Workaround: Users can still send Important Announcements by scrolling to find the intended group, though we advise double-checking group names when making your selections.

2. resolved Jan 23, 2026, 03:24 PM UTC

   The issue impacting the group selection interface for Important Announcements has been resolved. The group selection interface has returned to its standard, organized format. Users in the US West region should now see their groups appearing correctly. If you are still seeing the incorrect group layout, please refresh your browser or clear your cache to ensure the update takes effect.

Read the full incident report →

Started Dec 08, 2025, 03:53 PM UTC· resolved Dec 08, 2025, 08:19 PM UTC

1. investigating Dec 08, 2025, 03:53 PM UTC

   Our team is aware of sending delays from the Messages/XR platforms, impacting a subset of clients in the US Central hosting region. We are working to address this issue and will provide additional updates as soon as possible.

2. resolved Dec 08, 2025, 08:19 PM UTC

   The message sending delays affecting the US Central region have been resolved, and messages are now processing and sending as expected.

Read the full incident report →

Started Dec 08, 2025, 02:27 PM UTC· resolved Dec 08, 2025, 09:17 PM UTC

1. investigating Dec 08, 2025, 02:27 PM UTC

   We are currently investigating an issue that is inadvertently forcing LDAP users to reset passwords preventing the ability to log in to websites. We will provide an update as soon as possible.

2. monitoring Dec 08, 2025, 04:14 PM UTC

   A fix has been implemented and we are monitoring results. Please reach out to Support if you continue to experience issues.

3. resolved Dec 08, 2025, 09:17 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 24, 2025, 09:03 PM UTC· resolved Nov 24, 2025, 11:46 PM UTC

1. investigating Nov 24, 2025, 09:03 PM UTC

   Our development team has identified an issue that is causing SMS messages to not go out. We are working to resolve this issue as quickly as possible. While we work on this, phone calls and emails are still functioning as intended. Please reach out to the support team if you have any questions or need additional assistance with sending messages.

2. identified Nov 24, 2025, 10:39 PM UTC

   Our development team has identified the issue and are working to get this cleared up. Once this is resolved, all previously sent SMS messages will begin delivering to recipients. We apologize for the delay in delivery and thank you for your patience.

3. resolved Nov 24, 2025, 11:46 PM UTC

   We have confirmed that SMS messages are once again going out as expected. Thank you for your patience while we worked to resolve this.

Read the full incident report →

Started Nov 17, 2025, 07:07 PM UTC· resolved Nov 18, 2025, 09:21 PM UTC

1. investigating Nov 17, 2025, 07:07 PM UTC

   Our team is aware of a message-sending delay impacting a subset of clients using the Messages XR Enterprise and Mass Notification platforms. We are working to address this issue and will provide additional updates as soon as possible.

2. identified Nov 17, 2025, 08:51 PM UTC

   Our team is continuing to work on this issue, and sending delays may remain for a subset of clients. We will provide an additional update as soon as possible.

3. monitoring Nov 17, 2025, 10:15 PM UTC

   We are seeing message sends process as expected at this time, our team is continuing to monitor.

4. resolved Nov 18, 2025, 09:21 PM UTC

   The issue that was causing message sending delays for a subset of clients has been resolved.

Read the full incident report →

Started Nov 14, 2025, 06:00 PM UTC· resolved Nov 14, 2025, 09:16 PM UTC

1. identified Nov 14, 2025, 06:00 PM UTC

   We are working to resolve an issue that is preventing some users from logging into Composer.

2. monitoring Nov 14, 2025, 06:44 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Nov 14, 2025, 09:16 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 23, 2025, 11:13 PM UTC· resolved Oct 27, 2025, 06:26 PM UTC

1. investigating Oct 23, 2025, 11:13 PM UTC

   We are currently investigating SMS deliverability issues affecting a subset of clients.

2. resolved Oct 27, 2025, 06:26 PM UTC

   This incident has been resolved.

Read the full incident report →