Baremetrics Outage History
Baremetrics is up right nowPingoru has recorded 2 incidents for Baremetrics: 2 in the last 12 months and 0 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 524 (0%) |
Incidents, newest first
Critical November 18, 2025 App is not accessible 2h 15m Dashboard, API, Reports and Notifications, Recover and 2 more
Started Nov 18, 2025, 02:50 PM UTC· resolved Nov 18, 2025, 05:06 PM UTC
- identified Nov 18, 2025, 02:50 PM UTC
We have an issue with an external provider and are working to resolve it.
- monitoring Nov 18, 2025, 03:37 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Nov 18, 2025, 05:06 PM UTC
This incident has been resolved.
Notice November 13, 2025 Delay in new customer metrics (Stripe only) 3h 31m Dashboard, Reports and Notifications
Started Nov 13, 2025, 02:54 PM UTC· resolved Nov 13, 2025, 06:26 PM UTC
- 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.
- 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.
- 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.
- resolved Nov 13, 2025, 06:26 PM UTC
This incident has been resolved.