CloudsmithUpdate - Early Access - Policy Evaluation & Security Enrichment Delays:
The system is operational, and we've resolved the backfill operation and our additional performance enhancements.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
The system is operational, and we've resolved the backfill operation and our additional performance enhancements.
Resolved
Resolved
TikTok Trends IQ App in Talkwalker has been fully restored following TikTok's data infrastructure migration. Thanks for your patience while this was sorted out.
Resolved
This incident has now been resolved and the service is now fully operational.
Resolved
Our team has proactively reached out to all impacted organizations providing the below instructions to re-authorize their Microsoft mail server. If you are still experiencing this issue, please attempt to complete the re-authorization as advised below. If further issues still occur that you believe to be related to this incident, please reach out to Atlassian support for further assistance.
Resolved
This incident has been resolved, and service is operating normally again. Thanks for your patience.
Resolved
We have resolved the issue and transactions are now being synced correctly. In the vast majority of cases, previously missing transactions will show up automatically in the next 24 hours. In a few rare cases, additional action may be required and we will reach out directly. If you do not see expected transactions please monitor your inbox, or reach out to our support team for further assistance.
Resolved
An issue affecting PostHog Code tasks on Anthropic models and the installation Wizard has been resolved.
Resolved
All impacted services have now fully recovered.
Resolved
We recently addressed issues affecting Box Drive login and Single Sign-On \(SSO\) configuration. 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 10:56 PM PDT on May 21, 2026 and 2:07 AM PDT on May 22, 2026, some users may have experienced difficulties while working in Box. During this time, enterprise customers with Intune Mobile Application Management \(MAM\) enabled experienced SSO login failures when attempting to access Box Drive, and administrators were unable to view, update, or manage SSO configurations in the Admin Console. The issue occurred as a result of an unintended configuration change where our primary, active identity provider administration console region was inadvertently flipped to passive mode. We were able to resolve the issue by restoring the primary administration console region back to active status, which immediately restored normal API and login flows. In addition, we are making updates to improve monitoring and alerting for related operational workflows to prevent similar issues from occurring in the future. **Analysis** The active and standby regions were unintentionally reversed, causing the live production region to be switched into standby mode. As a result, the administrative API, which was used in for Intune MAM login flow, began rejecting requests for customers using Intune MAM-protected accounts and temporarily blocked certain SSO management actions in the Admin Console. End users affected by this saw login errors until the regions were restored to their correct state. We have since added safeguards to prevent unintended region switches and improved how our login flow handles this type of upstream failure. **Corrective Actions** Box has initiated the following corrective actions: * Add monitoring to catch certain configuration mismatches that could lead to unintended changes in service routing * Implement additional restrictions for administrative console region-flip 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
A subset of resources in us-east1-a experienced intermittent external connectivity disruption during a planned network maintenance window. Affected workloads may have observed elevated latency, connection timeouts, or failures reaching external destinations. Virtual machine availability was not affected. The change was rolled back to restore connectivity, which was confirmed stable following the revert.
Resolved
Sinch has resolved the issue impacting Australian customers not receiving auto super approval codes via SMS. We apologise for any inconvenience this has caused.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The issue has been resolved. If you are still having issues with Harmony container content not loading, please contact Customer Care.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Through our monitoring, we have determined that project upgrade behavior has returned to normal across the fleet. This incident is resolved.
Resolved
This incident has been resolved.
Resolved
On June 15, 2026, between 15:27 UTC and 16:23 UTC, GitHub webhook deliveries were delayed. During this window, webhook events were delivered later than normal, with average end-to-end delivery latency peaking at approximately 8.8 minutes. No webhook deliveries were lost — delayed events were queued and delivered once processing recovered.<br /><br />This was caused by a temporary throughput constraint in an internal event-processing system that moves webhook events through GitHub's delivery pipeline. The rate at which events were processed for delivery dropped below the incoming volume, creating a backlog. We restarted the affected pipeline service, after which throughput recovered and the backlog fully drained by approximately 16:29 UTC. Webhook delivery latency returned to normal, the incident was mitigated at 16:39 UTC, and fully resolved at 17:37 UTC.<br /><br />To reduce the likelihood and impact of similar incidents, we are working on improving the accuracy of the utilization metrics used to scale our delivery worker pools, reviewing connection and capacity headroom in the delivery pipeline.
Resolved
Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.
Resolved
Github has fixed the degradation. Updates should be restored to normal functionality.
Resolved
**What happened** An issue related to our speaker diarization service caused certain requests to hang until they timed out. This lead to a backlog of requests to our async API creating a processing queue across our US transcription pipeline, which slowed and timed out transcription requests more broadly, including requests that were not using speaker diarization. --- **When** Impact ran from approximately 15:00 to 16:25 UTC on June 25, 2026 \(about 1 hour 25 minutes\). The most severe disruption was in the first 45 minutes \(15:00–15:45 UTC\); remaining delays and timeouts cleared shortly after. Full recovery was confirmed by ≈16:40 UTC. --- **What services were affected** On our US async API endpoint transcription requests during this window saw processing delays and timeouts. Our EU async API endpoint was not affected and operated normally throughout.
Resolved
Transcribing and generating notes on iOS should be working as normal. If you've got a note that still appears to not be generated, tap it to open and then tap 'end' to retry, If you're still having issues, send us some logs from your device by tapping your profile picture to get to settings, then "contact support" and toggle "include diagnostics".
Resolved
This incident has been resolved.
Resolved
Our engineers were able to push a fix to resolve the failure to save when editing or creating Agent tools that include the Put, Patch, or Post methods in their configuration. We have validated that the tools are now able to be saved, and confirm full resolution.
Resolved
A small number of live streams were disconnected around 13:10 UTC, ending the corresponding Asset. Active live streams were able to reconnect and resume, and there is no long term impact to DVR or VOD content from affected live streams other than resuming on a new Asset ID. All systems are currently green.
Resolved
This incident has been resolved, we will publish RCA soon.
Resolved
Incident resolved
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The issue has been resolved. Terraform & Kubernetes operator users should no longer experience 400 errors when using aiven_pg_database. We apologize for any inconvenience caused.
Resolved
The incident has been resolved and systems are fully operational.
Resolved
This incident has been resolved.
Resolved
The issues affecting KRaft migrations during Kafka 3.8 to 3.9 upgrades have been resolved. Fixes have been deployed, migrations have been re-enabled, and services have remained stable during monitoring. If you are experiencing any issues, please contact support.
Resolved
This incident has been resolved. All previously submitted purge requests have been processed.
Resolved
This is now resolved
Resolved