BubbleRealtime updates slower than usual
The root cause has been identified and fixed.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
The root cause has been identified and fixed.
Resolved
The issue causing some Vibe Code Web sessions to terminate unexpectedly has been resolved.
Resolved
The earlier issue affecting slow loading of notes on macOS and Windows was only affecting a very small number of customers, so shouldn't be causing any problems beyond this. If you're still having problems, get in touch at hey@granola.so.
Resolved
This incident has been resolved.
Resolved
Between 13:16 and 13:24 UTC some requests to sites that use Edge Functions experienced increased latency and an elevated rate of 502 errors. This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The issue is resolved. The Jobs API v1alpha1 was not available during incident and clients may have experienced PermissionDenied errors. The Jobs API v1alpha2 was available but job runs were stuck in transient states (validated, queued or running) after start. The Jobs are being executed progressively. Some job runs can take some time to be executed.
Resolved
This incident has been resolved.
Resolved
The database recovery has been completed successfully, and Xray services in the Azure US East region have been fully restored. All affected services are operating normally, and the issue is now resolved.
Resolved
This incident has been resolved.
Resolved
We're no longer observing delays affecting the Issues API V3 service. The Snyk Incident Response has been stood down.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
We're investigating an issue affecting Qdrant Cloud clusters in the Azure Germany West Central region. Some clusters are currently unavailable, and others are running with fewer replicas than usual. Our engineers are investigating the issue. You don't need to take any action. Please avoid deleting or recreating your cluster while we work on this. We'll post the next update asap.
Resolved
This incident has been resolved. Incident Start Time: 2026-10-08 09:03 UTC Incident End Time: 2026-10-08 09:41 UTC Impact: Delayed MT's/Delayed MO's/Missing delivery receipts/Late delivery receipts
Resolved
Creating new projects from workspace chats is working normally again following a fix. Building and editing existing projects was not affected. This issue is now resolved.
Resolved
Twilio Verify and Programmable SMS delivery have fully recovered, and all impacted services are back to normal performance. This incident is now resolved. Thank you for your patience!
Resolved
Twilio Verify and Programmable SMS delivery have fully recovered, and all impacted services are back to normal performance. This incident is now resolved. Thank you for your patience!
Resolved
After further monitoring, this incident is now considered resolved. Box services have been restored to full functionality. Please contact Box Support at https://support.box.com/ if you continue to experience any issues.
Resolved
This incident has been resolved.
Resolved
Vonage services have been fully restored following today's service degradation on Video API Media Session, which began at Oct 8th, 02:17:38 UTC. Full resolution has been confirmed effective 02:20:38 UTC. Thank you for your patience and understanding as we worked to restore services as quickly as possible. If you have any questions, please contact api.support.vonage.com.
Resolved
The incident has been resolved.
Resolved
Music had reduced availability after a latent infrastructure configuration issue was triggered by routine automated maintenance. This stopped new instances from starting and prevented automated recovery, and service was restored by manual intervention. The service is now fully operational again.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
We had an incident on Storage offer which has now been resolved. Here are some supplementary details : <b>Start time :</b> 07/10/2026 12:36 UTC <b>End time :</b> 07/10/2026 13:20 UTC <b>Impacted Service(s) :</b> For these regions, you might had issues to access your Cold Archive services. <b>Customers Impact :</b> Customers were temporarily facing 503/500 errors when trying to access their Cold Archive. <b>Root Cause :</b> This is related to this incident : https://public-cloud.status-ovhcloud.com/incidents/kdqq2smzfd4t We thank you for your understanding and patience throughout this incident.
Resolved
From 07:08 to 07:43 UTC on October 8, 2026, the LLM Gateway (gateway.smith.langchain.com: http://gateway.smith.langchain.com) returned high 502 error rates. It was due to an incorrect infrastructure configuration change that stopped traffic from reaching the gateway. We fully restored the service at 07:43 UTC, and no other LangSmith services were affected. We're sorry for the disruption.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved
Resolved
All impacted services have now fully recovered.
Resolved
Resolved
After further monitoring, this incident is now considered resolved. Event-based reports and Insights in the Admin Console, results from the Enterprise Events API, and Box AI unit usage have been restored to full functionality and are showing up-to-date information. If you continue to experience any issues, please contact Support at https://support.box.com.
Resolved
This incident has been resolved.
Resolved
We are pleased to inform you that the incident affecting our Containers & Orchestration offering has been resolved. <b>Start time :</b> 26/08/2026 15:00 UTC <b>End time :</b> 06/10/2026 07:00 UTC <b>Root Cause :</b> This incident was caused by a network equipment issue. We apologize for any inconvenience caused and appreciate your understanding.
Resolved
Capacity remained stable in the last hour. Incident resolved.
Resolved
We have identified and resolved the connectors platform latency issue.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved