Historial de interrupciones de Finalsite

1. September 1, 2026 at 4:25 PM UTCinvestigating

   Actualmente estamos investigando problemas con un subconjunto de sitios web de Composer en el Centro de Estados Unidos. Estamos trabajando para analizar y mitigar este problema. Más actualizaciones a seguir en breve.

2. September 1, 2026 at 5:30 PM UTCmonitoring

   Estamos viendo el rendimiento mejorado en este momento en todos los sitios web de US Central, y seguimos monitoreando.

3. September 2, 2026 at 12:21 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 16, 2026 at 10:03 PM UTCinvestigating

   Actualmente estamos investigando un problema que está causando que los mensajes SMS se detengan en el buzón de salida. Nuestro equipo de ingeniería está investigando activamente este asunto para identificar la causa raíz. Se proporcionarán más actualizaciones tan pronto como se disponga de más información.

2. August 17, 2026 at 12:23 AM UTCinvestigating

   Actualmente estamos investigando un problema que afecta a la entrega de SMS debido a una interrupción del servicio con un socio de infraestructura de corriente avanzada. Impacto: Los mensajes pueden permanecer en su buzón de salida con un estado de "sending" por más tiempo de lo habitual, o pueden no entregarse por completo. Trabajamos activamente con nuestro socio para restaurar el servicio completo.

3. August 17, 2026 at 12:38 PM UTCmonitoring

   Nuestro socio de SMS avanzado ya no está observando más problemas, pero siguen monitoreando sus servicios de cerca. El envío saliente de SMS está volviendo a la normalidad, y nuestro equipo seguirá vigilando las tasas de entrega para garantizar la estabilidad.

4. August 17, 2026 at 8:15 PM UTCresolved

   La entrega de SMS ha permanecido normal durante todo el día, sin más interrupciones reportadas por nuestro proveedor de corriente. Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 14, 2026 at 3:17 PM UTCinvestigating

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

2. August 14, 2026 at 3:41 PM UTCmonitoring

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

3. August 18, 2026 at 5:02 PM UTCresolved

   This incident has been resolved.

1. August 13, 2026 at 1:52 PM UTCinvestigating

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

2. August 13, 2026 at 10:17 PM UTCidentified

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

3. August 14, 2026 at 1:41 PM UTCresolved

   This incident has been resolved.

1. August 7, 2026 at 12:42 PM UTCinvestigating

   Actualmente estamos investigando un problema con los sitios de Composer. Proporcionaremos más actualizaciones aquí cuando estén disponibles.

2. August 7, 2026 at 1:09 PM UTCmonitoring

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

3. August 7, 2026 at 3:34 PM UTCresolved

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

Traducido automáticamente desde la actualización oficial del incidente.

1. July 2, 2026 at 5:44 PM UTCinvestigating

   Actualmente estamos investigando esta cuestión.

2. July 2, 2026 at 5:59 PM UTCidentified

   Padres y administradores que se inscriben en la inscripción de FS usando Microsoft (Azure) Iniciar sesión no son capaces de acceder a la aplicación y verán un mensaje de error rojo al intentar iniciar sesión. Hemos identificado la causa del problema y estamos trabajando para remediar rápidamente esto. Gracias por su paciencia y comprensión.

3. July 2, 2026 at 8:46 PM UTCresolved

   El incidente se ha resuelto y ahora se restablece el inicio de sesión a través de Microsoft (Azure).

Traducido automáticamente desde la actualización oficial del incidente.

1. June 4, 2026 at 5:11 PM 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. June 4, 2026 at 6:40 PM 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. June 4, 2026 at 8:58 PM UTCidentified

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

4. June 5, 2026 at 12:13 AM 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. June 5, 2026 at 11:27 AM UTCmonitoring

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

6. June 5, 2026 at 6:36 PM UTCresolved

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

1. May 18, 2026 at 1:44 PM 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. May 18, 2026 at 3:20 PM UTCresolved

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

1. May 13, 2026 at 5:03 PM 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. May 13, 2026 at 6:07 PM 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. May 13, 2026 at 6:38 PM 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. May 13, 2026 at 6:52 PM UTCresolved

   This issue has been resolved.

1. May 6, 2026 at 7:41 PM 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. May 6, 2026 at 8:39 PM 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. May 7, 2026 at 7:08 PM UTCresolved

   This incident has been resolved.

1. May 5, 2026 at 2:52 PM 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. May 5, 2026 at 3:06 PM 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. May 5, 2026 at 5:45 PM UTCresolved

   This incident has been resolved.

1. April 28, 2026 at 3:00 PM 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. May 1, 2026 at 12:06 PM 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. March 23, 2026 at 4:01 PM 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. March 24, 2026 at 5:33 PM UTCmonitoring

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

3. March 24, 2026 at 5:44 PM UTCresolved

   This incident has been resolved.

1. February 27, 2026 at 5:00 PM 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. February 27, 2026 at 5:35 PM UTCidentified

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

3. February 27, 2026 at 6:37 PM 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. February 27, 2026 at 7:15 PM 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. February 27, 2026 at 11:08 PM UTCresolved

   This incident has been resolved.

1. February 22, 2026 at 10:59 PM 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. February 23, 2026 at 12:56 AM UTCresolved

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

1. February 19, 2026 at 5:24 PM UTCinvestigating

   Our team is investigating SMS sending delays and degraded performance.

2. February 19, 2026 at 6:29 PM UTCmonitoring

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

3. February 19, 2026 at 9:53 PM UTCmonitoring

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

4. February 19, 2026 at 10:20 PM UTCmonitoring

   We are continuing to monitor for any further issues.

5. February 20, 2026 at 2:21 PM UTCresolved

   This incident has been resolved.

1. February 18, 2026 at 11:19 PM UTCinvestigating

   Our team is investigating SMS sending delays and degraded performance.

2. February 19, 2026 at 12:49 AM UTCmonitoring

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

3. February 19, 2026 at 12:26 PM UTCresolved

   This incident has been resolved.

1. February 12, 2026 at 2:03 PM 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. February 12, 2026 at 5:40 PM 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. February 12, 2026 at 6:57 PM UTCmonitoring

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

4. February 12, 2026 at 9:36 PM UTCresolved

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

1. February 10, 2026 at 3:08 PM 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. February 10, 2026 at 7:35 PM 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. February 11, 2026 at 1:34 PM 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. February 11, 2026 at 11:28 PM UTCresolved

   This issue has been resolved.

1. January 22, 2026 at 6:21 PM 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. January 23, 2026 at 7:26 PM 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. January 24, 2026 at 7:59 PM UTCresolved

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