Störungsverlauf von Finalsite

1. 1. September 2026 um 16:25 UTCinvestigating

   Wir untersuchen derzeit Probleme mit einer Untergruppe von Composer-Websites in der US-Zentrale. Wir arbeiten daran, dieses Problem zu analysieren und zu mildern. Weitere Updates folgen in Kürze.

2. 1. September 2026 um 17:30 UTCmonitoring

   Wir sehen, dass sich die Leistung derzeit auf allen US Central-Websites verbessert hat, und wir überwachen weiterhin.

3. 2. September 2026 um 12:21 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 16. August 2026 um 22:03 UTCinvestigating

   Wir untersuchen derzeit ein Problem, das dazu führt, dass SMS-Nachrichten im Posteingang stehen bleiben. Unser Ingenieurteam untersucht diese Angelegenheit aktiv, um die Ursache zu identifizieren. Weitere Updates werden bereitgestellt, sobald weitere Informationen verfügbar sind.

2. 17. August 2026 um 00:23 UTCinvestigating

   Wir untersuchen derzeit ein Problem, das die SMS-Zustellung aufgrund einer Serviceunterbrechung mit einem vorgelagerten Infrastrukturpartner betrifft. Auswirkungen: Nachrichten können länger als üblich in Ihrem Posteingang mit dem Status "Senden" verbleiben oder sie können nicht vollständig zugestellt werden. Wir arbeiten aktiv mit unserem Partner zusammen, um den Full-Service wiederherzustellen.

3. 17. August 2026 um 12:38 UTCmonitoring

   Unser vorgelagerter SMS-Partner beobachtet keine weiteren Probleme mehr, aber er überwacht seine Dienste weiterhin genau. Die ausgehende SMS-Zustellung normalisiert sich wieder, und unser Team wird die Zustellungsraten weiterhin überwachen, um Stabilität zu gewährleisten.

4. 17. August 2026 um 20:15 UTCresolved

   Die SMS-Zustellung ist den ganzen Tag über normal geblieben, ohne dass weitere Störungen von unserem Upstream-Anbieter gemeldet wurden. Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 14. August 2026 um 15:17 UTCinvestigating

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

2. 14. August 2026 um 15:41 UTCmonitoring

   We are observing improved performance and will continue to closely monitor.

3. 18. August 2026 um 17:02 UTCresolved

   This incident has been resolved.

1. 13. August 2026 um 13:52 UTCinvestigating

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

2. 13. August 2026 um 22:17 UTCidentified

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

3. 14. August 2026 um 13:41 UTCresolved

   This incident has been resolved.

1. 7. August 2026 um 12:42 UTCinvestigating

   Wir untersuchen derzeit ein Problem mit Composer-Sites. Wir werden hier weitere Updates zur Verfügung stellen, sobald sie verfügbar sind.

2. 7. August 2026 um 13:09 UTCmonitoring

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

3. 7. August 2026 um 15:34 UTCresolved

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

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 2. Juli 2026 um 17:44 UTCinvestigating

   Wir untersuchen derzeit dieses Problem.

2. 2. Juli 2026 um 17:59 UTCidentified

   Eltern und Administratoren, die sich mit Microsoft (Azure) Login bei FS Enrollment anmelden, können derzeit nicht auf die Anwendung zugreifen und sehen beim Anmeldeversuch eine rote Fehlermeldung. Wir haben die Ursache des Problems identifiziert und arbeiten daran, dies schnell zu beheben. Vielen Dank für Ihre Geduld und Ihr Verständnis.

3. 2. Juli 2026 um 20:46 UTCresolved

   Der Vorfall wurde behoben und die Anmeldung über Microsoft (Azure) ist nun wiederhergestellt.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 4. Juni 2026 um 17:11 UTCinvestigating

   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. 4. Juni 2026 um 18:40 UTCinvestigating

   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. 4. Juni 2026 um 20:58 UTCidentified

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

4. 5. Juni 2026 um 00:13 UTCidentified

   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. 5. Juni 2026 um 11:27 UTCmonitoring

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

6. 5. Juni 2026 um 18:36 UTCresolved

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

1. 18. Mai 2026 um 13:44 UTCinvestigating

   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. 18. Mai 2026 um 15:20 UTCresolved

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

1. 13. Mai 2026 um 17:03 UTCinvestigating

   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. 13. Mai 2026 um 18:07 UTCidentified

   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. 13. Mai 2026 um 18:38 UTCmonitoring

   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. 13. Mai 2026 um 18:52 UTCresolved

   This issue has been resolved.

1. 6. Mai 2026 um 19:41 UTCinvestigating

   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. 6. Mai 2026 um 20:39 UTCmonitoring

   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. 7. Mai 2026 um 19:08 UTCresolved

   This incident has been resolved.

1. 5. Mai 2026 um 14:52 UTCinvestigating

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

2. 5. Mai 2026 um 15:06 UTCmonitoring

   We are no longer seeing issues in the US Central region. Our team is continuing to monitor at this time. If you are still seeing any issues, please contact Composer Support.

3. 5. Mai 2026 um 17:45 UTCresolved

   This incident has been resolved.

1. 28. April 2026 um 15:00 UTCinvestigating

   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. 1. Mai 2026 um 12:06 UTCresolved

   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.

1. 23. März 2026 um 16:01 UTCidentified

   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. 24. März 2026 um 17:33 UTCmonitoring

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

3. 24. März 2026 um 17:44 UTCresolved

   This incident has been resolved.

1. 27. Februar 2026 um 17:00 UTCinvestigating

   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. 27. Februar 2026 um 17:35 UTCidentified

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

3. 27. Februar 2026 um 18:37 UTCidentified

   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. 27. Februar 2026 um 19:15 UTCmonitoring

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

5. 27. Februar 2026 um 23:08 UTCresolved

   This incident has been resolved.

1. 22. Februar 2026 um 22:59 UTCinvestigating

   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. 23. Februar 2026 um 00:56 UTCresolved

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

1. 19. Februar 2026 um 17:24 UTCinvestigating

   Our team is investigating SMS sending delays and degraded performance.

2. 19. Februar 2026 um 18:29 UTCmonitoring

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

3. 19. Februar 2026 um 21:53 UTCmonitoring

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

4. 19. Februar 2026 um 22:20 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 20. Februar 2026 um 14:21 UTCresolved

   This incident has been resolved.

1. 18. Februar 2026 um 23:19 UTCinvestigating

   Our team is investigating SMS sending delays and degraded performance.

2. 19. Februar 2026 um 00:49 UTCmonitoring

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

3. 19. Februar 2026 um 12:26 UTCresolved

   This incident has been resolved.

1. 12. Februar 2026 um 14:03 UTCinvestigating

   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. 12. Februar 2026 um 17:40 UTCidentified

   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. 12. Februar 2026 um 18:57 UTCmonitoring

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

4. 12. Februar 2026 um 21:36 UTCresolved

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

1. 10. Februar 2026 um 15:08 UTCinvestigating

   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. 10. Februar 2026 um 19:35 UTCidentified

   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. 11. Februar 2026 um 13:34 UTCmonitoring

   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. 11. Februar 2026 um 23:28 UTCresolved

   This issue has been resolved.

1. 22. Januar 2026 um 18:21 UTCinvestigating

   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. 23. Januar 2026 um 19:26 UTCidentified

   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. 24. Januar 2026 um 19:59 UTCresolved

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