Better Uptime outage history

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

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

We'll be migrating some Telemetry sources to new, more robust infrastructure. Each source will be affected for no more than 90 minutes. During the migration there may be brief gaps in dashboard charts and delayed Live tail data. Queries through the SQL Connections API may briefly return an error rather than incomplete results. Please reach out to us at [email protected] if you have any questions.

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

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

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 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]](mailto:[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]](mailto:[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. 🙏

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.

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.

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.

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.

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.

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

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’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.

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.

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.

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.

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!

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.

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!

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]".

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!

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!

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!

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]`.