Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Jun 25, 2026

  1. LovableElevated rates of build errors

    This incident has been resolved. The build errors affecting the preview and chat have been corrected, and normal behaviour has been restored. We apologise for any inconvenience caused. Should you have any questions, please contact our support team.

    Resolved

  2. MongoDB CloudMongoDB Atlas: Atlas UI loading issues

    From 2026-06-25 06:55 UTC to 2026-06-25 07:10 UTC, some users may have experienced intermittent Atlas UI loading failures. We identified elevated traffic to a number of endpoints that increased latency in the Atlas UI service. This caused internal health checks to fail and temporarily reduced healthy Atlas UI capacity. We restored healthy Atlas UI capacity and applied additional rate limiting to the affected traffic paths. We are continuing follow-up work to further  reduce the risk of recurrence.

    Resolved

  3. PostHogApplication: partial outage

    The service is running normally and users should not be seeing any further issues in relation to this. We're continuing to monitor and working to improve the service further.

    Resolved

  4. PaddleIntermittent Checkout Loading Issues

    The incident affecting Checkouts has been fully resolved. All services are now operating normally.  We apologize for any disruption this may have caused. If you have any questions or concerns, please contact our Customer Support team at sellers@paddle.com.

    Resolved

  5. SupabaseElevated errors on Postgres change subscriptions

    We have confirmed that the fix has been successfully applied and the issue affecting Postgres Change subscriptions has been resolved. We will continue to monitor the service, but all systems are operating normally at this time.

    Resolved

Jun 24, 2026

  1. PostHogSession Replay event ingestion: processing delays

    An offline batch job overloaded a cache that session recording ingestion pipeline relied on for processing. This resulted in some session recording ingestion delays. Moving the batch job off of hot path caches and ensuring the ingestion pipeline is more resilient to cache failures will keep this from happening again.

    Resolved

  2. Box[Medium] Issue with Multiple Box Services

    We recently addressed issues affecting Box Public API. We would like to take the opportunity to further explain these issues and the steps we have taken to keep them from happening in the future. Between 5:10 PM PDT and 6:40 PM PDT on June 10, 2026, some users may have experienced difficulties accessing or working within Box. During this period, there was a noticeable degradation affecting Public API request processing. This issue occurred as a result of a recent software change to our authentication infrastructure in our ongoing effort to improve performance and stability of Public API service. We were able to resolve the issue by scaling up the service, correcting its resource allocation, and rolling back the change. In addition, we are working to improve our resource provisioning to prevent similar issues from occurring in the future. **Analysis** We recently began rolling out an update to our authentication infrastructure designed to improve performance and stability of Public API service. Following the gradual rollout, an increase in resource utilization during peak traffic led to unexpected resource utilization on our authentication infrastructure. As a result, those servers became unresponsive, preventing them from processing Public API requests. We were able to resolve the issue by temporarily scaling up and adjusting the resource allocations of the authentication service. **Corrective Actions** Box has initiated the following corrective actions: * Rebalancing the resource allocations of the authentication service to accommodate higher traffic volumes * Tuning server timeouts across Public API components to ensure consistent, predictable API response times * Establishing processes and automation to reduce time to mitigation We are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.  Sincerely, The Box Team

    Resolved

  3. SnowflakeINC0159144

    Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC0159144](https://community.snowflake.com/s/article/INC0159144)

    Resolved

  4. HootsuiteBluesky authentication difficulties in Hootsuite

    We have resolved the issues related to connecting Bluesky accounts to Hootsuite. If you continue to experience difficulty connecting or reconnecting your Bluesky account, or see error notifications in Composer, please reach out to our customer support team.

    Resolved

  5. GitHubDisruption with some GitHub services

    On June 16, 2026, between 17:20 UTC and 18:15 UTC, the Opus 4.8 model experienced degraded availability in GitHub Copilot. During this window, some requests to Opus 4.8 failed or errored. Other Copilot models were not affected and remained available as alternatives. This was caused by an issue with an upstream model provider. The upstream provider resolved the issue, and we monitored Opus 4.8 until success rates returned to normal. The incident is fully resolved.

    Resolved

  6. LinodeService Issue - Debian Package Availability

    Our upstream third-party Debian repo failed to sync with their own upstream repo chain for an unknown reason. The InRelease files for Debian packages were left to expire starting at approximately 08:12 UTC on June 24, 2026, preventing any Debian packages from getting installed. We didn't have programmatic visibility at that time to know that these files were unable to download or if the expiration date in the InRelease files had been reached. We mitigated the issue at approximately 12:35 UTC on June 24, 2026, by updating which repo we are syncing Debian packages from and purging the stale InRelease files from our cache. We are working to integrate system visibility and alerting around expiration dates of these files in addition to switching to a more reliable upstream repo, i.e. Debian's official repos. This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing and any information herein is subject to change.

    Resolved

  7. LovableCredits not showing

    The issue with the credits not showing should now be resolved for all users. Thank you for your patience.

    Resolved

  8. DeepgramISP Network-Related Issue

    An upstream ISP issue may have caused intermittent WebSocket connection failures, handshake timeouts, and degraded streaming connectivity. Incident time: 01:10 - 01:52 UTC

    Resolved

  9. JamfJamf Protect for macOS - Degraded Performance

    This incident has been resolved. In the process we've reverted from version 8.16.0 to 8.15.0. Please refer to the Jamf Protect macOS Security Portal Release Notes for future updates.

    Resolved

  10. LambdaUS-SOUTH-2 Booting Failures of Newly Launched Instance

    Severity Level: High A fix has been implemented and we’re monitoring the results. To be automatically notified when the status of this incident changes, please click on the “Subscribe to updates” button. Thank you for your patience and understanding during this time.

    Resolved

  11. UpstashQStash EU Region — Degraded Performance

    ### **Summary** On June 23, 2026, QStash users in the EU-CENTRAL-1 region experienced elevated latency and degraded performance. The issue was caused by a regression introduced in a recent enhancement to Flow Control scheduling logic. The change increased resource consumption under load, leading to reduced performance on affected shards. The incident was resolved by rolling back to the previous stable version. ### **Impact** * Service: QStash \(EU-CENTRAL-1\) * Start: 2026-06-23 16:22 UTC * Resolved: 2026-06-23 17:14 UTC * Duration: ~52 minutes * Impact: Increased latency and degraded performance for workloads routed to the affected instance in the EU. Multiple customers in the region experienced slower request processing during the incident window. ### **Root Cause** We recently deployed an enhancement to our Flow Control feature, designed to improve fairness between independent flow controls when unused global parallelism capacity was available. Under production load, the new behavior introduced a regression that significantly increased resource utilization. The elevated resource consumption caused performance degradation on the affected QStash instamce, impacting all workloads sharing that instance. ### **Resolution** After identifying the regression as the source of the slowdown, we rolled back the deployment to the last known stable version. * Rollback completed: 2026-06-23 19:18:46.84 UTC Following the rollback, system performance returned to normal levels and service stability was restored. ### **Preventive Actions** To reduce the likelihood of similar incidents in the future, we are taking the following actions: * Expand performance and load testing coverage for Flow Control changes. * Add resource utilization regression checks to the deployment pipeline. * Improve monitoring and alerting for abnormal CPU and memory consumption patterns. * Introduce additional canary validation before wider production rollout of scheduler-related changes. We apologize for the disruption and appreciate our customers’ patience while we resolved the issue.

    Resolved

  12. Intercom - AUiOS users facing issues logging into Fin

    This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to team@intercom.io: mailto:team@intercom.io if you have any further questions or if you’re still seeing any unexpected behaviour

    Resolved

  13. Intercom - EUiOS users facing issues logging into Fin

    This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to team@intercom.io: mailto:team@intercom.io if you have any further questions or if you’re still seeing any unexpected behaviour

    Resolved

  14. Intercom - USiOS users facing issues logging into Fin

    This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to team@intercom.io: mailto:team@intercom.io if you have any further questions or if you’re still seeing any unexpected behaviour

    Resolved

Older incidents