Baremetrics Outage History

Baremetrics is up right now

Baremetrics had 6 outages in the last 2 years totaling 32h 28m of downtime — averaging 0.2 incidents per month.

There were 6 Baremetrics outages since June 10, 2025 totaling 32h 28m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.baremetrics.com

Critical November 18, 2025

App is not accessible

Detected by Pingoru
Nov 18, 2025, 02:50 PM UTC
Resolved
Nov 18, 2025, 05:06 PM UTC
Duration
2h 15m
Affected: DashboardAPIReports and NotificationsRecoverCancellation InsightsMessaging
Timeline · 3 updates
  1. identified Nov 18, 2025, 02:50 PM UTC

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

  2. monitoring Nov 18, 2025, 03:37 PM UTC

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

  3. resolved Nov 18, 2025, 05:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 13, 2025

Delay in new customer metrics (Stripe only)

Detected by Pingoru
Nov 13, 2025, 02:54 PM UTC
Resolved
Nov 13, 2025, 06:26 PM UTC
Duration
3h 31m
Affected: DashboardReports and Notifications
Timeline · 4 updates
  1. investigating Nov 13, 2025, 02:54 PM UTC

    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.

  2. identified Nov 13, 2025, 02:54 PM UTC

    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.

  3. monitoring Nov 13, 2025, 04:25 PM UTC

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

  4. resolved Nov 13, 2025, 06:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 6, 2025

Accounts are behind

Detected by Pingoru
Oct 06, 2025, 10:25 PM UTC
Resolved
Oct 07, 2025, 11:52 AM UTC
Duration
13h 27m
Affected: Dashboard
Timeline · 2 updates
  1. monitoring Oct 06, 2025, 10:25 PM UTC

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

  2. resolved Oct 07, 2025, 11:52 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 30, 2025

Some accounts are behind

Detected by Pingoru
Sep 30, 2025, 06:26 PM UTC
Resolved
Sep 30, 2025, 10:10 PM UTC
Duration
3h 44m
Affected: Dashboard
Timeline · 3 updates
  1. investigating Sep 30, 2025, 06:26 PM UTC

    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!

  2. identified Sep 30, 2025, 06:28 PM UTC

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

  3. resolved Sep 30, 2025, 10:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 27, 2025

Some accounts' metrics are delayed

Detected by Pingoru
Jun 27, 2025, 02:04 PM UTC
Resolved
Jun 27, 2025, 08:08 PM UTC
Duration
6h 4m
Affected: DashboardAPIReports and NotificationsRecoverCancellation Insights
Timeline · 2 updates
  1. investigating Jun 27, 2025, 02:04 PM UTC

    We are currently investigating the issue.

  2. resolved Jun 27, 2025, 08:08 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 10, 2025

We’re making some behind-the-scenes updates. Some account data may be delayed while we pause syncing temporarily. Everything will be back to normal shortly!

Detected by Pingoru
Jun 10, 2025, 03:09 PM UTC
Resolved
Jun 10, 2025, 06:34 PM UTC
Duration
3h 25m
Affected: Dashboard
Timeline · 2 updates
  1. investigating Jun 10, 2025, 03:09 PM UTC

    We are currently investigating this issue.

  2. resolved Jun 10, 2025, 06:34 PM UTC

    This incident has been resolved.

Read the full incident report →