Historique des pannes de Baremetrics

We have an issue with an external provider and are working to resolve it.

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

This incident has been resolved.

We are seeing a delay in calculating metrics for new customers on Stripe accounts. New customer data from Stripe is coming in correctly (subscriptions, start dates, customer details), but the step that calculates their metrics is running behind. This causes some new Stripe customers to be missing from your metrics temporarily. The current delay is about 24 to 48 hours.

We have identified the issue and are rolling out the fix now. The calculation backlog is large, so it will take some time for the system to catch up fully. You may continue to see delayed new customer metrics while this process is ongoing.

The fix has been implemented and solves the delay. You may continue to see delayed new customer metrics while our system fully catches up.

This incident has been resolved.

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

This incident has been resolved.

Some accounts are currently behind. The issue is resolved, and we are monitoring progress as accounts begin to catch up. It may take a bit of time for all accounts to fully update. Thanks for your patience!

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

This incident has been resolved.

We are currently investigating the issue.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

Some accounts are currently behind. We're investigating the issue and monitoring progress as accounts begin to catch up. It may take a bit of time for all accounts to fully update—thanks for your patience!

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

This incident has been resolved.

We're experiencing some delays in account updates due to a backlog in our system processes. Things are recovering, but updates may take a little longer than usual.

This incident has been resolved.

We are currently investing elevated error rates in our app.

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

This incident has been resolved.

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

This incident has been resolved.

We have identified the issue and are implementing a solution.

A fix has been implemented and we're monitoring the results.

This incident has been resolved.

We have reported the issue to Apple and are waiting for resolution.

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 the issue.

This incident has been resolved.

We are currently working on resolving some issues with dashboards not loading. We will work on getting your data back up and running as quickly as possible.

A fix has been implemented and we're monitoring the results.

This incident has been resolved.

We are currently investigating this issue.

Thank you for your patience as we addressed intermittent problems. If you're still encountering errors, please contact our Customer Success team.

This incident has been resolved.

We're having some issues. We're working on it! 🔨

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.

Looking to resolve

We are continuing to investigate this issue.

This incident has been resolved.

Some customers have reported seeing 500 error code on their dashboards. The impact for those customers is 'Major', while other customers do have have issues.

We are currently investigating why some accounts are experiencing timeouts and slow updates.

We identified the issue and accounts should be back to updating normally.

Our Elasticsearch servers are having some trouble keeping up. This affects some Customers and Segmentation. Other parts of the app will keep working as usual.

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

This incident has been resolved.