Following the incident on Frankfurt, we want to share with you the post-mortem and the next steps we're taking.
https://meilisearch.notion.site/2026-03-25-Frankfurt-cluster-incident-report-Kong-failure-32f4b06b651f809c83d4fde9fd7d27e2

We sincerely apologize for any disruption this incident has caused.

All instances in the Frankfurt cluster are back online and operating normally. We will continue monitoring to ensure stability.

Thank you for your patience during this incident.

The issue affecting the Frankfurt cluster has been resolved. Instances are coming back online and service is being restored. We will continue to monitor the situation to ensure stability.
We appreciate your patience throughout this incident and apologize again for any disruption caused.

We are still actively investigating the issue affecting the Frankfurt cluster. Our team has been working through multiple avenues to identify a solution and is continuing to do so with urgency. We will share another update as soon as we have more information.
Thank you for your patience and apologies for the disruption caused.

We are continuing to investigate an ongoing issue affecting the Frankfurt cluster. The issue has been narrowed to Kong configuration. Our team is actively working on a resolution and we will provide an update as soon as we have more information.
We apologize for any disruption this incident is causing.

We are still investigating the cause of the instance access issues in Frankfurt

We are aware of SSL errors in Frankfurt, we are investigating the issue.