RadarElevated API Latencies
This incident has been resolved.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
This incident has been resolved.
Resolved
**Incident:** From June 5th, 2025 through June 17th we disabled <a href="https://developers.asana.com/docs/using-asanas-model-control-protocol-mcp-server">MCP</a> \(an opt-in API feature\) for maintenance to address a vulnerability. **Impact:** If your organization was using the MCP server and was impacted by this issue, we have already reached out to you directly with important details and next steps. **Moving forward:** We've fixed the the bug which was identified. As part of our remediation efforts, we reset all connections to the MCP server. This means you'll need to manually reconnect your Asana instance to the MCP server.
Resolved
The issue with the email/calendar integration checkboxes has been resolved. There should be no further impact at this time, but please reach out to us at Support if any additional assistance is needed: https://help.lever.co/hc/en-us/requests/new
Resolved
The issue has been fully resolved. All affected components are operating normally again.
Resolved
This incident has been resolved.
Resolved
At approximately Jun 17 22:10:46 UTC 2025, the Aspose add-on intermittent issue has been resolved. Customers should no longer experience issues with file-related conversions when calling the Aspose service.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved, and Jira Service Management and Opsgenie are back in operational mode.
Resolved
Edit with v3.0 was returning errors, the root cause has since been identified and resolved.
Resolved
Resolved: Llama-4-Maverick-17B-128E-Instruct partial outage is now resolved. Contact help@sambanova.ai if further details are required.
Resolved
**June 15, 2025 - Jamf SecureDNS Outage RCA** **Summary and Timeline** On June 15, 2025 \(00:00 UTC\), devices using SecureDNS lost internet access due to an outage affecting Web Threat Prevention and Content Filtering capabilities within Jamf Safe Internet, Jamf Protect, and Jamf Trust services.The root cause of the incident was an expired SSL certificate, leading to loss of security features or loss of internet connectivity for end user devices. Although the certificate in question was renewed on May 22nd, 2025, the process used to deploy this certificate had an error, which resulted in incomplete distribution across our global cloud environment.After receiving customer reports of the outage, we investigated, identified the issue and impacted services, and then manually deployed the new certificate to restore the service. We are currently conducting a thorough internal review of the outage and will work to improve the certificate management process to minimize the risk of a repeat occurrence. **Incident Timeline \(UTC\)** * June 15, 2025 at 00:00: The SSL certificate expires * June 15, 2025 at ~00:25 : Troubleshooting efforts begin * June 15, 2025 at 01:45: Root cause identified * June 15, 2025 at 02:30: Teams locate all services requiring updated certificate * June 15, 2025 at 04:15: New certificate is deployed to US regions * June 15, 2025 at 04:30: Jamf verifies that the issue has been resolved across all regions Service disruption duration: 270 minutes **Impact Assessment** Users Affected: All end user devices with Encrypted DNS Gateway configured, lost internet access. Services Impacted: SecureDNS **Remediation Items & Next Steps** We are currently conducting a thorough internal investigation of the events that led to the outage and identifying any gaps that we will need to address to minimize the risk of such occurrences. Our key areas of focus include: **1. Certificate management reviews –** Ensure certificate documentation is up to date and include explicit verification steps for each service component. Enhance existing certificate expiration monitoring. **2. Monitoring** – review and enhance monitoring and alerting of anomalies in traffic patterns. Add in synthetic monitoring. **3. Communications** – Refine internal and customer-facing workflows to ensure rapid response and clarity during incidents. 4\. Evaluate adding additional critical domains to **on-device content filtering safe list.** _For additional questions and needs, please reach out to your customer success manager or log a support ticket at_ [_support.jamf.com_](http://support.jamf.com/)_._
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved. These issues were confirmed as related to this incident on Google Cloud's status page: https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW
Resolved
Upload and video processing are performing normally.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
On June 13, Bitbucket Cloud experienced intermittent availability. The issue has now been resolved, and the service is operating normally for all affected users.
Resolved
This incident has been resolved.
Resolved
GCP experienced an outage which impacted our ability to access GCS object storage and GCR image repository services. This resulted in some Zilliz Cloud clusters to be unavailable in the GCP regions of gcp-us-east4, gcp-us-central1, and gcp-us-asia-southeast1. Cluster creation and edit operations were also impacted in those regions. As of now, GCP services have fully recovered, and our services have fully recovered as well.
Resolved
This incident has been resolved.
Resolved
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The issue has been identified and the incident has been resolved.
Resolved
While Google is still experiencing issues in some regions, Warp's services are healthy once again.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
All services have been returned to operational for users in all regions.
Resolved
Google Cloud has recovered from the issue that was impacting the Anyscale platform. Cluster launches, workspace snapshots, and certificate provisioning are all operating normally. We're continuing to monitor for stability. Thanks for your patience!
Resolved
This incident has been resolved.
Resolved
All systems are back to normal operation.
Resolved
All our products and modules are now operating normally. If you are still experiencing any related issues, please contact our Customer Support team for assistance.
Resolved
All Crusoe Cloud services have been restored and are fully operational. We will continue to monitor our platform. If you notice any issues please reach out to support@crusoecloud.com
Resolved
Google has reported that mitigations have been applied and services are now recovering.
Resolved
EU-01 is now fully recovered. Data Processing and Outbound Messaging backlogs have been fully processed. With that, Braze is fully operational.
Resolved
ReadMe services were not affected by the incidents at Cloudflare and Google Cloud, which are now reporting as fully operational.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved