Is Better Stack down?

Last checked 6m ago
Current status
Better Stack is up

No incidents right now.

Official status page: https://status.betterstack.com · Polled every 5 minutes · 7 components tracked

Better Stack is operational right now. Last checked 6m ago; the most recent incident resolved 2d ago.

Real-time Better Stack status, recent outages, and incident history — pulled directly from Better Stack's official status page at https://status.betterstack.com every 5 minutes. Pingoru tracks 7 Better Stack services and has captured 8 incidents in the last 90 days (98.89% uptime). Get email, Slack, Discord, or webhook alerts the moment Better Stack reports a new incident — free for 5 monitors, no credit card.

Users who monitor Better Stack also follow these DevOps services: GitHub Confluence Circle CI OpsGenie JFrog Papertrail Airbrake Splunk OnCall Datadog EU RubyGems View all 6,000+ providers
Better Stack uptime 98.89% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 2d 5h
    Started Sep 04, 2026, 01:50 PM UTC · Resolved Sep 06, 2026, 07:13 PM UTC
    Telemetry
    Timeline · 2 updates
    • 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!

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

    Latest: 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 co…

  2. Resolved 9m
    Started Aug 20, 2026, 02:39 PM UTC · Resolved Aug 20, 2026, 02:48 PM UTC
    Telemetry
    Timeline · 2 updates
    • investigating · Aug 20, 2026, 02:39 PM UTC

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

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

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

  3. Resolved 2h 58m
    Started Jul 24, 2026, 09:01 PM UTC · Resolved Jul 24, 2026, 11:59 PM UTC
    Telemetry
    Timeline · 2 updates
    • 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.

    • resolved · Jul 24, 2026, 11:59 PM UTC

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

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

  4. Resolved 2h
    Started Jun 15, 2026, 10:25 AM UTC · Resolved Jun 15, 2026, 12:25 PM UTC
    Telemetry
    Timeline · 2 updates
    • 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.

    • resolved · Jun 15, 2026, 12:25 PM UTC

      The network issue causing this problem has been resolved.

    Latest: The network issue causing this problem has been resolved.

  5. Resolved 51m
    Started Jun 14, 2026, 10:49 AM UTC · Resolved Jun 14, 2026, 11:40 AM UTC
    Telemetry
    Timeline · 2 updates
    • 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.

    • resolved · Jun 14, 2026, 11:40 AM UTC

      The infrastructure issue has been resolved.

    Latest: The infrastructure issue has been resolved.

Outage history

Past 90 days · 5 incidents View full outage history →