Better Stack had 12 outages in the last 2 years totaling 29h 24m of downtime — averaging 0.5 incidents per month.
There were 12 Better Stack outages since August 20, 2025 totaling 29h 24m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently experiencing an outage in our AWS Direct Connect forwarding infrastructure; this may introduce delays or failures to ingest data.
The network issue causing this problem has been resolved.
We're currently experiencing an infrastructure issue that is impacting some customer queries in our Europe region.
The infrastructure issue has been resolved.
We're currently investigating some transient errors which are affecting the performance of our Uptime platform. We're very sorry for the inconvenience.
We've resolved the uptime performance degradations.
We're currently investigating some transient errors which are affecting the performance of our Uptime platform. We're very sorry for the inconvenience.
We're mitigating. Need help? Let us know at [email protected]
The attack has been successfully mitigated by our DDoS protection. Sincere apologies for the inconvenience. Need help? Let us know at [email protected].
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.
Bunny CDN resolved the issue. We apologize for the inconvenience.
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].
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].
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.
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!
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. 🙏
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. 🙏
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.
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.
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.
Email deliveries are back to normal.
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.
The issue has been resolved; all pending data has been ingested, and queries are fully operational.
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.
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.