54 incidente Lyyti înregistrate începând din iunie 2023, cu actualizări oficiale, componente afectate, durată și informații despre rezolvare.
Serviciul nostru de editori de mesaje se confruntă cu o pană majoră, ne pare rău pentru orice inconvenient.
Problema a fost identificată și se pune în aplicare o soluție.
A fost implementată o soluţie şi monitorizăm rezultatele.
Acest incident a fost rezolvat.
Traducere automată din actualizarea oficială a incidentului.
În prezent investigăm această problemă.
Continuăm să investigăm această problemă.
Problema a fost identificată și se pune în aplicare o soluție.
Acest incident a fost rezolvat.
Traducere automată din actualizarea oficială a incidentului.
În prezent, avem o perturbare a serviciilor noastre de sprijin din cauza unei întreruperi cu furnizorul nostru de servicii. Puteți experimenta întârzieri în timpii de răspuns sau dificultăți în a ajunge la echipa noastră de sprijin prin toate canalele.
A fost implementat un fix și serviciile noastre de sprijin par să fie din nou disponibile. Rețineți că întârzierile și întreruperile pot încă să apară. Monitorizăm situaţia.
Serviciile de sprijin sunt pe deplin operaționale fără întreruperi.
Traducere automată din actualizarea oficială a incidentului.
Datorită unei probleme globale în mediul Microsoft 365, ne confruntăm în prezent cu probleme de livrare de e-mail către adresele de e-mail găzduite de Microsoft. Monitorizăm situaţia.
Problema globală Microsoft 365 a fost rezolvată, iar livrarea prin e-mail a revenit la normal. Orice e-mail întârziat afectat de pană sunt în prezent resentimente.
Traducere automată din actualizarea oficială a incidentului.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
We are continuing to monitor for any further issues.
We're currently experiencing unusual high amounts of traffic.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
**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.
We're currently investigating a major outage, no data is lost or corrupted.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
We are continuing to investigate this issue.
Knowledge base is available again!
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
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.
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.
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.
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.
Our support services are currently unavailable due to a major Cloudfare outage. We're monitoring the situation.
Our support services are slowly up and running again.
The incident has been resolved and our support services are up and running again.
We are currently investigating this issue.
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.
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.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
The issue has been identified and a fix is being implemented by our email service provider.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
We are currently investigating this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
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.
