История сбоев Lyyti

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.

We are currently investigating this issue.

Issue been caused by security systems, proceeding with reconfigure

Issue has been resolved, monitoring system stability.

This incident has been resolved.

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

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.

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.

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.

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.

This incident has been resolved.

Due to technical issues, event websites were unavailable today between 09:35-09:54 UTC. The outage affected published, public-facing websites. We are sorry for the inconvenience caused by this outage.