Better Stack Outage History

Started Oct 21, 2026, 06:30 PM UTC· resolved Oct 21, 2026, 07:09 PM UTC

1. investigating Oct 21, 2026, 06:30 PM UTC

   An intermittent network issue between Tier 1 network providers one of our cloud provider relies on triggered incidents for customers relying on single-region uptime Monitors. We're sincerely sorry for the trouble. We think this is unacceptable and consider it a priority to make our incident detection even more robust to correctly detect partial intermittent backbone issues. To fully mitigate immediately, we recommend enabling more than 1-region for your monitors. Need help? Let us know at [email protected], we're here for you.

2. resolved Oct 21, 2026, 07:09 PM UTC

   The issue has been resolved. We apologize for the trouble Need help? Please let us know at [email protected]

Read the full incident report →

Started Sep 04, 2026, 01:50 PM UTC· resolved Sep 06, 2026, 07:13 PM UTC

1. investigating Sep 04, 2026, 01:50 PM UTC

   We're seeing delayed data processing for some sources located in the Europe region again. The team is looking into resolving as soon as possible. There has been no data loss, all incoming data is ingested and will become visible as the system catches up. If you have any questions, please reach out to [email protected]. Thank you for your patience!

2. investigating Sep 04, 2026, 07:53 PM UTC

   Processing of new data in the Europe region is starting to recover. Backfilling delayed data will take longer, so older timestamps may still be missing. No data has been lost.

3. investigating Sep 05, 2026, 03:23 PM UTC

   Live data is coming in. Historical data is backfilling at a steady rate, we expect several more hours until all data is processed. Thank you for your patience. Please reach out to [email protected] with any questions.

4. resolved Sep 06, 2026, 07:13 PM UTC

   This incident is now resolved. All sources in the Europe region are processing in real time and the delayed backlog has been processed in full. What happened: On September 3, we consolidated several EU Telemetry clusters onto new, higher-capacity infrastructure. The cutover multiplied concurrent write streams on the cluster, and the volume of concurrent inserts saturated per-host write throughput on I/O contention. Ingestion fell behind, and affected sources saw delays in Live tail, dashboards, alerts, and queries. Our initial fixes, tuning the write path and adding capacity, restored real-time ingestion within a day, but draining the backlog alongside live traffic re-created the contention. We then rebuilt the recovery pipeline and held live data with strict priority while separately replaying the backlog at a controlled rate. Replaying several days of data was the slowest part of the recovery by design, as we rate-limited the replay so that real-time ingestion wasn't put at risk. We know teams rely on this data to operate their own systems, and losing that visibility for days is serious. We are sorry, both for the disruption and for turning what we originally announced as 90-minute maintenance into a multi-day incident. The fixes we made here are permanent, and this kind of contention can't happen again. Thank you very much for your patience. Please reach out to [email protected] if you have any questions.

5. resolved Sep 06, 2026, 07:13 PM UTC

   This incident is now resolved. All sources in the Europe region are processing in real time and the delayed backlog has been processed in full. What happened: On September 3, we consolidated several EU Telemetry clusters onto new, higher-capacity infrastructure. The cutover multiplied concurrent write streams on the cluster, and the volume of concurrent inserts saturated per-host write throughput on I/O contention. Ingestion fell behind, and affected sources saw delays in Live tail, dashboards, alerts, and queries. Our initial fixes, tuning the write path and adding capacity, restored real-time ingestion within a day, but draining the backlog alongside live traffic re-created the contention. We then rebuilt the recovery pipeline and held live data with strict priority while separately replaying the backlog at a controlled rate. Replaying several days of data was the slowest part of the recovery by design, as we rate-limited the replay so that real-time ingestion wasn't put at risk. We know teams rely on this data to operate their own systems, and losing that visibility for days is serious. We are sorry, both for the disruption and for turning what we originally announced as 90-minute maintenance into a multi-day incident. The fixes we made here are permanent, and this kind of contention can't happen again. Thank you very much for your patience. Please reach out to [[email protected]](mailto:[email protected]) if you have any questions.

Read the full incident report →

Started Aug 20, 2026, 02:39 PM UTC· resolved Aug 20, 2026, 02:48 PM UTC

1. investigating Aug 20, 2026, 02:39 PM UTC

   Telemetry dashboard might be unavailable for some customers due to a database issue, we're investigating.

2. resolved Aug 20, 2026, 02:48 PM UTC

   The issue was resolved, we apologize for the incovenience, please let us know if we can help with anything at [email protected].

Read the full incident report →

Started Jul 24, 2026, 09:01 PM UTC· resolved Jul 24, 2026, 11:59 PM UTC

1. investigating Jul 24, 2026, 09:01 PM UTC

   We're currently experiencing some issues with Telemetry source configuration changes and creation of new sources. Queries and ingesting are unaffected. We are investigating.

2. resolved Jul 24, 2026, 11:59 PM UTC

   This issue has now been resolved, all source and configuration updates should now propagate as expected.

Read the full incident report →

Started Jun 15, 2026, 10:25 AM UTC· resolved Jun 15, 2026, 12:25 PM UTC

1. investigating Jun 15, 2026, 10:25 AM UTC

   We are currently experiencing an outage in our AWS Direct Connect forwarding infrastructure; this may introduce delays or failures to ingest data.

2. resolved Jun 15, 2026, 12:25 PM UTC

   The network issue causing this problem has been resolved.

Read the full incident report →

Started Jun 14, 2026, 10:49 AM UTC· resolved Jun 14, 2026, 11:40 AM UTC

1. investigating Jun 14, 2026, 10:49 AM UTC

   We're currently experiencing an infrastructure issue that is impacting some customer queries in our Europe region.

2. resolved Jun 14, 2026, 11:40 AM UTC

   The infrastructure issue has been resolved.

Read the full incident report →

Started May 21, 2026, 01:50 PM UTC· resolved May 21, 2026, 02:20 PM UTC

1. investigating May 21, 2026, 01:50 PM UTC

   We're currently investigating some transient errors which are affecting the performance of our Uptime platform. We're very sorry for the inconvenience.

2. resolved May 21, 2026, 02:20 PM UTC

   We've resolved the Uptime performance degradations.

Read the full incident report →

Started May 08, 2026, 07:24 PM UTC· resolved May 08, 2026, 08:05 PM UTC

1. investigating May 08, 2026, 07:24 PM UTC

   We're mitigating. Need help? Let us know at [email protected]

2. resolved May 08, 2026, 08:05 PM UTC

   The attack has been successfully mitigated by our DDoS protection. Sincere apologies for the inconvenience. Need help? Let us know at [email protected].

Read the full incident report →

Started Feb 13, 2026, 12:26 AM UTC· resolved Feb 13, 2026, 02:53 AM UTC

1. investigating Feb 13, 2026, 12:26 AM UTC

   Bunny CDN, one of our CDN providers, is experiencing a software bug on their UK-located PoP. We're in touch with them and the issue should be resolved within a few minutes. We apologize for the inconvenience. If you urgently need to use the dashboard, please, use a VPN to connect to any US location. Thank you.

2. resolved Feb 13, 2026, 02:53 AM UTC

   Bunny CDN resolved the issue. We apologize for the inconvenience.

Read the full incident report →

Started Jan 14, 2026, 03:05 PM UTC· resolved Jan 14, 2026, 06:35 PM UTC

1. investigating Jan 14, 2026, 03:05 PM UTC

   We’re currently seeing delayed data processing for some sources located in our US East cluster. The underlying root cause has been resolved; however, it may take some time for all historical data to fully appear in Live tail. Please note there's no data loss — all incoming data is ingested and will become visible as the system catches up. If you have any questions, feel free to reach out at [email protected].

2. resolved Jan 14, 2026, 06:35 PM UTC

   The earlier delay affecting some sources in our US East cluster has been fully resolved. All data has now been processed and is visible in Live tail, with no data loss. If you have any questions, please contact us at [email protected].

3. resolved Jan 14, 2026, 06:35 PM UTC

   The earlier delay affecting some sources in our US East cluster has been fully resolved. All data has now been processed and is visible in Live tail, with **no data loss**. If you have any questions, please contact us at **[[email protected]](mailto:[email protected])**.

Read the full incident report →

Started Nov 26, 2025, 01:20 PM UTC· resolved Nov 26, 2025, 01:55 PM UTC

1. investigating Nov 26, 2025, 01:20 PM UTC

   We’re currently seeing elevated query latency and temporary failures in our eu-nbg-2 cluster. Incoming data is being ingested, but processing might be delayed for some of the sources, and some queries might also fail or return incomplete results. Our engineering team is actively working on this and the backlog is already being reduced and we expect full recovery shortly. We’ll keep this page updated as soon as we have any more updates.

2. resolved Nov 26, 2025, 01:55 PM UTC

   Query issues in eu-nbg-2 are now mostly resolved. The ingesting lag has also fully caught up around the same time, and data is being processed as expected. We’re continuing to monitor the cluster closely and are reviewing the ingesting pipeline to ensure everything is stable and performing normally. Thanks a lot for your patience and let us know at [email protected] if anything!

3. resolved Nov 26, 2025, 01:55 PM UTC

   Query issues in eu-nbg-2 are now mostly resolved. The ingesting lag has also fully caught up around the same time, and data is being processed as expected. We’re continuing to monitor the cluster closely and are reviewing the ingesting pipeline to ensure everything is stable and performing normally. Thanks a lot for your patience and let us know at `[email protected]` if anything!

Read the full incident report →

Started Nov 18, 2025, 11:35 AM UTC· resolved Nov 18, 2025, 12:30 PM UTC

1. investigating Nov 18, 2025, 11:35 AM UTC

   We’re currently experiencing an issue where the Better Stack UI is temporarily inaccessible. Our backend services, monitoring infrastructure, APIs, and alerting are fully operational — however, Cloudflare is undergoing a global outage that is impacting routing and preventing our dashboard from loading. You can track the upstream incident here: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 We’re actively monitoring the situation and will restore full access as soon as Cloudflare resolves their routing issues. All core functionality — checks, heartbeats, alerts, log ingestion, and metrics — continues to function normally in the background. Thank you for your patience. 🙏

2. investigating Nov 18, 2025, 12:15 PM UTC

   The Better Stack UI is now mostly accessible again, and many users should be able to load the dashboard normally. Cloudflare’s global outage is still ongoing, and while their network has become more stable, intermittent routing issues may continue. This means you may still see occasional slow loading or elevated error rates as the situation fully recovers. We’re continuing to monitor the upstream incident and will share further updates as Cloudflare stabilizes their systems.

3. resolved Nov 18, 2025, 12:30 PM UTC

   Cloudflare has mostly resolved the underlying routing issues related to their global outage, and their systems are now operating normally. With their network stabilized, the Better Stack UI and all related services are fully accessible again. Everything on our side is now running as expected, and we are no longer seeing elevated error rates or degraded performance. We’ll continue to monitor the situation, but no further impact is expected. If you have any questions or notice anything unusual, please feel free to reach out to us at [email protected] — we’re happy to help. Thank you for your patience throughout the incident. 🙏

4. resolved Nov 18, 2025, 12:30 PM UTC

   Cloudflare has mostly resolved the underlying routing issues related to their global outage, and their systems are now operating normally. With their network stabilized, the Better Stack UI and all related services are fully accessible again. Everything on our side is now running as expected, and we are no longer seeing elevated error rates or degraded performance. We’ll continue to monitor the situation, but no further impact is expected. If you have any questions or notice anything unusual, please feel free to reach out to us at [email protected] — we’re happy to help. Thank you for your patience throughout the incident. 🙏

Read the full incident report →

Started Nov 16, 2025, 01:55 PM UTC· resolved Nov 16, 2025, 07:10 PM UTC

1. investigating Nov 16, 2025, 01:55 PM UTC

   We’re currently seeing intermittent timeout issues affecting some custom status pages. The first errors begin appearing around 1:55 PM UTC, with certain requests returning no response across multiple regions. We’re looking into this now and will share another update shortly.

2. investigating Nov 16, 2025, 02:15 PM UTC

   The timeout issues are now resolved. We apply mitigations around 2:15 PM UTC, and affected status pages begin responding normally again. Thanks a lot for your patience while we work through this.

3. investigating Nov 16, 2025, 02:45 PM UTC

   Following the earlier timeout issue, we’re seeing that a small subset of custom status pages did not fully recover after the initial fix at 2:15 PM UTC. Some of these pages are now encountering SSL-related errors, such as certificate validation failures or timeouts, due to an internal component not behaving correctly after the earlier disruption. We’re continuing to investigate and will share more updates as soon as we have them.

4. resolved Nov 16, 2025, 07:10 PM UTC

   We’ve resolved an issue that caused some custom status pages to fail to load or return timeout errors. The problem was related to certificate handling workflow, which temporarily prevented certain pages from obtaining or refreshing their SSL certificates. All affected pages are now loading normally again. Thank you very much for your patience and understanding. Please let us know at [email protected] if you'd have any further questions.

Read the full incident report →

Started Oct 20, 2025, 07:31 AM UTC· resolved Oct 20, 2025, 09:29 AM UTC

1. investigating Oct 20, 2025, 07:31 AM UTC

   We are seeing elevated error rates in our email delivery service due to an ongoing AWS outage. As a result, some notification emails may be delayed. Uptime monitoring and data processing are fully operational.

2. resolved Oct 20, 2025, 09:29 AM UTC

   Email deliveries are back to normal.

Read the full incident report →

Started Oct 01, 2025, 07:41 AM UTC· resolved Oct 01, 2025, 08:58 AM UTC

1. investigating Oct 01, 2025, 07:41 AM UTC

   We’re currently experiencing a network outage in our provider’s data centre that is impacting a portion of queries and causing delays in data ingestion. Our team is actively working with the provider to resolve the issue as quickly as possible. We’ll keep you updated as soon as we have any more details. Thank you for your patience while we work on bringing everything back to normal.

2. investigating Oct 01, 2025, 08:25 AM UTC

   Most of our network has now been restored; please bear with us as any delayed data is inserted, and full query functionality is restored.

3. resolved Oct 01, 2025, 08:58 AM UTC

   The issue has been resolved; all pending data has been ingested, and queries are fully operational.

Read the full incident report →

Started Aug 20, 2025, 11:17 AM UTC· resolved Aug 20, 2025, 08:42 PM UTC

1. investigating Aug 20, 2025, 11:17 AM UTC

   We’re currently investigating an issue where logs sent via RSyslog from Digital Ocean are not reaching our ingestion endpoint. This started after planned migration of the old Rsyslog sources to our new cloud infrastructure and only seems to be affecting Digital Ocean platform. We're currently cooperating with Digital Ocean team on a fix and we’ll provide updates as soon as possible.

2. investigating Aug 20, 2025, 04:58 PM UTC

   We’ve identified the root cause and it seems that Digital Ocean’s DNS records have not yet been updated to point to the new endpoints. This caused incompatibility and temporary unavailability of log ingestion. We’re actively working with the Digital Ocean team to resolve this. We’ll share more details shortly.

3. resolved Aug 20, 2025, 08:42 PM UTC

   We identified an issue with DNS resolution between Digital Ocean and Better Stack. This has now been resolved, and logs are now being processed normally.

Read the full incident report →

Started May 28, 2025, 02:50 PM UTC· resolved May 28, 2025, 03:55 PM UTC

1. investigating May 28, 2025, 02:50 PM UTC

   Some customers are experiencing delays in log ingestion and slower query performance once again. We sincerely apologize for the repeated disruption. Our team is actively working to identify the root cause and will provide further updates as soon as we have more information. Thank you for your patience and understanding.

2. resolved May 28, 2025, 03:55 PM UTC

   This issue has now been resolved. Log ingestion delays and query performance have returned to normal for all affected customers. We apologize for the repeated disruptions and appreciate your patience as we worked to restore service. Our team continues to monitor the situation closely to ensure ongoing stability. If you continue to experience any issues, please reach out to us right away.

Read the full incident report →

Started May 27, 2025, 12:50 PM UTC· resolved May 27, 2025, 03:00 PM UTC

1. investigating May 27, 2025, 12:50 PM UTC

   Some customers are once again experiencing delays in log ingestion and slower query performance. We apologize for the recurrence and understand how disruptive this can be. Our team is actively investigating the underlying cause, and we’ll share more details as soon as we have them. Thank you for your continued patience and understanding!

2. resolved May 27, 2025, 03:00 PM UTC

   This issue has now been resolved. Log ingestion and query performance is now stable. We apologize again for the disruption and appreciate your patience while we addressed this recurrence. If you notice any ongoing issues, please reach out to us right away.

Read the full incident report →

Started May 27, 2025, 08:05 AM UTC· resolved May 27, 2025, 10:30 AM UTC

1. investigating May 27, 2025, 08:05 AM UTC

   We’re currently investigating reports of sporadic log ingestion delays and reduced query performance impacting a subset of sources. Our engineering team is working diligently to identify the cause and return systems to normal speed as quickly as possible. We’ll share another update as soon as we have more information—thank you for bearing with us!

2. resolved May 27, 2025, 10:30 AM UTC

   This issue has been resolved. Log ingestion and query performance have returned to normal. Thank you for your patience while we worked to address this incident. If you continue to experience any issues, please don’t hesitate to reach out at "[email protected]".

Read the full incident report →

Started May 16, 2025, 09:33 AM UTC· resolved May 16, 2025, 12:10 PM UTC

1. investigating May 16, 2025, 09:33 AM UTC

   We’re aware of reports of intermittent delays in log ingestion and slower-than-normal query performance affecting some customers. Our engineering team is actively investigating the root cause and working to restore full performance as soon as possible. We’ll post another update once we have more details—thank you for your patience!

2. resolved May 16, 2025, 12:10 PM UTC

   We’ve identified and resolved the root cause of the issue. Log ingestion delays are cleared and query performance has returned to normal. Should you continue to experience any problems, please reach out to us at [email protected]. Thank you for your patience!

3. resolved May 16, 2025, 12:10 PM UTC

   We’ve identified and resolved the root cause of the issue. Log ingestion delays are cleared and query performance has returned to normal. Should you continue to experience any problems, please reach out to us at `[email protected]`. Thank you for your patience!

Read the full incident report →

Started May 08, 2025, 12:05 PM UTC· resolved May 08, 2025, 01:30 PM UTC

1. investigating May 08, 2025, 12:05 PM UTC

   We are currently investigating an issue causing intermittent delays in log ingestion and slower query performance for some customers. Our engineering team is working to restore full service as quickly as possible. We'll make sure to keep you posted once there are more details. Thanks a lot for your patience!

2. resolved May 08, 2025, 01:30 PM UTC

   Query performance is back to normal and all delayed logs are now being ingested; no data was lost. We’re continuing to monitor the system to ensure everything remains stable. Thank you for your patience and for bearing with us. If you observe any lingering issues, please let us know at [email protected].

3. resolved May 08, 2025, 01:30 PM UTC

   Query performance is back to normal and all delayed logs are now being ingested; no data was lost. We’re continuing to monitor the system to ensure everything remains stable. Thank you for your patience and for bearing with us. If you observe any lingering issues, please let us know at `[email protected]`.

Read the full incident report →

Started May 06, 2025, 02:34 PM UTC· resolved May 06, 2025, 02:48 PM UTC

1. investigating May 06, 2025, 02:34 PM UTC

   We're seeing degraded performance for the Uptime dashboard and Live tail loading times in some regions. Our engineers are looking into it. We apologize for the inconvenience.

2. resolved May 06, 2025, 02:48 PM UTC

   All services are back to normal. Sincere apologies for the inconvenience! Please message us at [email protected] if we can help with anything.

Read the full incident report →

Started Apr 25, 2025, 08:50 PM UTC· resolved Apr 26, 2025, 04:05 AM UTC

1. investigating Apr 25, 2025, 08:50 PM UTC

   We're currently experiencing an issue with log processing that may result in slower queries and delayed log ingestion for some users. We're actively investigating and working to resolve the issue as quickly as possible.

2. resolved Apr 26, 2025, 04:05 AM UTC

   All delayed ingestion has been cleared; logs and metrics should now be available as normal. Thank you for your patience.

Read the full incident report →

Started Apr 20, 2025, 08:29 PM UTC· resolved Apr 20, 2025, 08:41 PM UTC

1. investigating Apr 20, 2025, 08:29 PM UTC

   Uptime and status page performance is degraded in some regions. Our engineers are looking into it. We apologize for the inconvenience

2. resolved Apr 20, 2025, 08:41 PM UTC

   All services are back to normal. Sincere apologies for the inconvenience! Please message us at [email protected] if we can help with anything.

Read the full incident report →

Started Apr 02, 2025, 09:15 AM UTC· resolved Apr 02, 2025, 09:39 AM UTC

1. investigating Apr 02, 2025, 09:15 AM UTC

   We're currently experiencing an issue with log querying that may result in slower queries for some users. We're actively investigating and working to resolve the issue as quickly as possible.

2. resolved Apr 02, 2025, 09:39 AM UTC

   The issue has been resolved, all log querying is back to normal.

Read the full incident report →