Histórico de interrupções do Lyyti

1. 4 Gwengolo 2026 da 12:11 UTCidentified

   Devido a um problema global no ambiente Microsoft 365, estamos atualmente experimentando problemas de entrega de email para endereços de email hospedados Microsoft. Estamos a acompanhar a situação.

2. 4 Gwengolo 2026 da 13:27 UTCresolved

   O problema global da Microsoft 365 foi resolvido e a entrega de e-mail retornou ao normal. Quaisquer e-mails atrasados afetados pela interrupção estão sendo ressentidos.

Traduzido automaticamente da atualização oficial do incidente.

1. 1 Gouere 2026 da 07:06 UTCinvestigating

   We are currently investigating this issue.

2. 1 Gouere 2026 da 07:13 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 1 Gouere 2026 da 07:30 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 1 Gouere 2026 da 07:48 UTCidentified

   We're currently experiencing unusual high amounts of traffic.

5. 1 Gouere 2026 da 08:47 UTCmonitoring

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

6. 1 Gouere 2026 da 09:26 UTCresolved

   This incident has been resolved.

7. 2 Gouere 2026 da 10:12 UTCpostmortem

   **Status update: Service disruption on 1 July 2026** On Monday 2026-07-01, between 07:00 and 08:55 UTC, Lyyti experienced unavailability and degraded performance affecting Lyyti core, including Portal, registration pages, API, integrations and mobile apps. Due to unforeseen circumstances, a high-traffic registration event triggered multiple edge cases in our system, resulting in significantly higher than expected load on our servers, which in turn caused slowness and disruption to our normal services. This was more than a routine traffic spike, and our team worked throughout the incident to restore full service. As part of our post-mortem analysis, we have identified the underlying causes. We have since deployed fixes to mitigate the identified issues and prevent this from happening again. We apologize for the inconvenience caused by this outage. If you have any further questions regarding this incident, do not hesitate to contact us.

1. 16 Mezheven 2026 da 09:14 UTCinvestigating

   We're currently investigating a major outage, no data is lost or corrupted.

2. 16 Mezheven 2026 da 09:28 UTCmonitoring

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

3. 16 Mezheven 2026 da 09:57 UTCresolved

   This incident has been resolved.

1. 15 Mae 2026 da 07:41 UTCinvestigating

   We are currently investigating this issue.

2. 15 Mae 2026 da 07:43 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 15 Mae 2026 da 07:52 UTCmonitoring

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

4. 15 Mae 2026 da 08:28 UTCresolved

   This incident has been resolved.

1. 30 Ebrel 2026 da 09:44 UTCinvestigating

   We are currently investigating this issue.

2. 30 Ebrel 2026 da 09:47 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 30 Ebrel 2026 da 09:48 UTCmonitoring

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

4. 30 Ebrel 2026 da 09:53 UTCresolved

   This incident has been resolved.

1. 27 Ebrel 2026 da 11:43 UTCinvestigating

   We are currently investigating this issue.

2. 27 Ebrel 2026 da 12:58 UTCmonitoring

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

3. 27 Ebrel 2026 da 13:30 UTCresolved

   This incident has been resolved.

1. 23 Meurzh 2026 da 08:37 UTCinvestigating

   We are currently experiencing issues with our knowledge base and Lyyti's help articles are therefore unavailable. We're investigating the issue and hope to resolve it quickly.

2. 23 Meurzh 2026 da 09:45 UTCinvestigating

   We are continuing to investigate this issue.

3. 23 Meurzh 2026 da 11:44 UTCresolved

   Knowledge base is available again!

1. 18 Meurzh 2026 da 07:47 UTCinvestigating

   We are currently investigating this issue.

2. 18 Meurzh 2026 da 07:47 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 18 Meurzh 2026 da 07:58 UTCresolved

   This incident has been resolved.

1. 23 Cʼhwevrer 2026 da 13:55 UTCresolved

   Statuses for outbound email messages were not properly reflected in the messaging statistics in Lyyti Portal. The status update was out of order between Friday 18:50 UTC and Monday 13:25 UTC, and mail statuses updated during this time will unfortunately not be reflected in the messaging statistics in Lyyti Portal. Rest assured that the incident only concerns the visibility of message statuses. Email messages has been delivered as normal during the whole period of this incident. We are sorry for the inconvenience caused by this issue.

1. 18 Cʼhwevrer 2026 da 12:53 UTCinvestigating

   Since approximately 8:40 UTC today, statuses for outbound email messages are not properly reflected in the messaging statistics in Lyyti Portal. This causes all messages to be shown as 'sent' regardless of the actual status. In other words, statuses like 'opened', 'clicked', 'bounced', 'blocked', are not currently reflected for most messages sent today. Rest assured that messages are being delivered as normal, and the issue at hand only concerns the statistics and the visibility of statuses for specific messages. We are investigating the issue together with the email service provider, and we will let you know once the issue has been resolved.

2. 18 Cʼhwevrer 2026 da 13:33 UTCmonitoring

   The cause for the issue with the statuses has been located and the issue has been resolved. Email status updates are currently flowing normally, but it will take a moment for the statuses for the last few hours to be updated within Lyyti. We are monitoring the situation and will close the incident once all statuses have been properly updated.

3. 18 Cʼhwevrer 2026 da 15:39 UTCresolved

   Retroactive email statuses that had accumulated during the day have been updated, and statuses are updating in real-time as of approximately 14:05 UTC. This incident has been resolved.

1. 5 Kerzu 2025 da 09:10 UTCinvestigating

   Our support services are currently unavailable due to a major Cloudfare outage. We're monitoring the situation.

2. 5 Kerzu 2025 da 09:19 UTCmonitoring

   Our support services are slowly up and running again.

3. 5 Kerzu 2025 da 09:25 UTCresolved

   The incident has been resolved and our support services are up and running again.

1. 7 Du 2025 da 13:28 UTCinvestigating

   We are currently investigating this issue.

2. 7 Du 2025 da 13:40 UTCidentified

   The initial root cause is still being investigated. An operational issue affecting a cluster compute node was identified and the node has been recreated. Service has been restored, and we are monitoring the cluster for full stability.

3. 7 Du 2025 da 13:55 UTCmonitoring

   The operational issue has been mitigated, and services are now reporting as operational. We are under a period of enhanced monitoring. A key cluster compute node, which was previously unavailable, has been successfully recreated and brought back online. We are now closely monitoring the stability and performance of the cluster. We continue to investigate the root cause of the initial compute node failure.

4. 7 Du 2025 da 14:01 UTCresolved

   This incident has been resolved.

1. 2 Here 2025 da 06:34 UTCinvestigating

   We are currently investigating this issue.

2. 2 Here 2025 da 06:37 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 2 Here 2025 da 06:44 UTCmonitoring

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

4. 2 Here 2025 da 07:09 UTCresolved

   This incident has been resolved.

1. 30 Gwengolo 2025 da 10:28 UTCinvestigating

   We are currently experiencing a delay in email send outs. Messages will be delivered, but with a delay. We're currently investigating the issue with our email service provider.

2. 30 Gwengolo 2025 da 11:24 UTCidentified

   The issue has been identified and a fix is being implemented by our email service provider.

3. 30 Gwengolo 2025 da 14:49 UTCresolved

   This incident has been resolved.

1. 11 Gwengolo 2025 da 08:45 UTCinvestigating

   We are currently investigating this issue.

2. 11 Gwengolo 2025 da 08:57 UTCmonitoring

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

3. 11 Gwengolo 2025 da 09:06 UTCresolved

   This incident has been resolved.

1. 14 Eost 2025 da 06:12 UTCresolved

   Due to abnormally high load on some production servers, our web services experienced an intermittent outage between 15:00-15:10 UTC. This resulted in momentary inability to access event registration pages and other web services. The underlying causes have been analyzed and fixes are being implemented to prevent similar outages from occurring in the future. We are sorry for the inconvenience caused by this outage.

1. 7 Eost 2025 da 10:21 UTCinvestigating

   We are currently investigating this issue.

2. 7 Eost 2025 da 10:21 UTCinvestigating

   We are continuing to investigate this issue.

3. 7 Eost 2025 da 10:26 UTCmonitoring

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

4. 7 Eost 2025 da 11:03 UTCresolved

   This incident has been resolved. The root cause for the incident was related to code changes that were deployed into production by our production team. Despite being properly reviewed and approved, the code changes caused unforeseen issues under certain circumstances. As a result, there were issues accessing Lyyti's services between 10:00-10:23 UTC. We are sorry for the inconvenience caused by this outage.

1. 21 Mae 2025 da 10:26 UTCinvestigating

   We are currently investigating this issue.

2. 21 Mae 2025 da 10:34 UTCidentified

   Issue been caused by security systems, proceeding with reconfigure

3. 21 Mae 2025 da 10:37 UTCmonitoring

   Issue has been resolved, monitoring system stability.

4. 21 Mae 2025 da 10:54 UTCresolved

   This incident has been resolved.

1. 20 Mae 2025 da 14:22 UTCinvestigating

   Event websites are currently unavailable and returning HTTP 500 errors, we are investigating the issue and will report back shortly.

2. 20 Mae 2025 da 14:34 UTCresolved

   A fix has been implemented and event websites are working again as of 15:26 UTC. We are truly sorry for the inconvenience caused by this outage. This incident has been resolved.

1. 13 Mae 2025 da 21:09 UTCinvestigating

   We are currently investigating an issue related to outbound email messages sent through Lyyti. Outbound email messages might not currently reach their recipients as intended. We are sorry for the inconvenience, and we will keep you updated as the situation progresses.

2. 13 Mae 2025 da 23:08 UTCidentified

   The issue has been identifed and is related to the Mailjet email service provider. Messages that are normally sent through Lyyti using Mailjet are currently not being delivered, as of Tuesday 2025-05-14 20:36 UTC. This includes most email messages sent through Lyyti, including both transactional and non-transactional email. Clients using a custom SMTP relay are unaffected. We are working together with Mailjet to resolve the issue and restore email service as soon as possible. We are truly sorry for the inconvenience caused by this incident.

3. 14 Mae 2025 da 07:05 UTCmonitoring

   A fix has been implemented and previously queued messages are currently being sent. No email messages have been lost, i.e. all messages are being sent, albeit with a delay. Once again, we are sorry for the inconvenience caused by this outage.

4. 14 Mae 2025 da 07:34 UTCresolved

   This incident has been resolved.