Mezmo Status

Resolved: This incident has been resolved.

Monitoring: At this time services are restored. Mezmo continues to perform diagnosis to identify and address the root causes or triggers for degradations in service, with engineering staying on high alert for any recurrences. We sincerely apologize for the impacts this incident may have had to your services.

Identified: We are continuing to work on a fix for this issue.

Identified: Apologies Mezmo customers as we are again experiencing problems with our Search Engine and live tail. We have identified the problem and are actively working to fix it now.

Resolved: Mezmo has made a backend change that we believe should mitigate this issue in the future. Mezmo will continue to proactively monitor the platform for any signs of recurrence. Please reach out through our normal support channels if you are still experiencing issues at this time or need further information about this incident. We apologize for the impacts this incident may have had to your services.

Monitoring: Impacts from this issue are currently mitigated. Mezmo engineering continues to investigate the underlying causes of this issue and will leave this ticket in a monitoring state for now.

Investigating: Mezmo has identified an issue with our search engine which is preventing events from being displayed in live tail. We are actively working on the problem and expect to have it resolved shortly. Please subscribe to this page for updates on this issue.

Resolved: This incident has been resolved.

Monitoring: At this time services are restored. Mezmo continues to perform diagnosis to identify and address the root causes or triggers for degradations in service, with engineering staying on high alert for any recurrences. We sincerely apologize for the impacts this incident may have had to your services.

Identified: We are continuing to work on a fix for this issue.

Identified: Apologies Mezmo customers as we are again experiencing problems with our Search Engine and live tail. We have identified the problem and are actively working to fix it now.