CanvaUsers may experience a 503 error message when accessing canva.com.
This incident is now resolved. Thank you for your patience and understanding.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
This incident is now resolved. Thank you for your patience and understanding.
Resolved
All impacted services have now fully recovered.
Resolved
This incident has been resolved.
Resolved
All impacted services have now fully recovered.
Resolved
All impacted services have now fully recovered.
Resolved
The root cause was identified and the issue was resolved at 20:24:10 UTC.
Resolved
At approximately 10:30 AM CT, we identified an issue affecting stream processing within the AWS US-EAST-1 region. As of now, normal operations have resumed. We have initiated a full investigation to determine the root cause and prevent future recurrence.
Resolved
Our team has mitigated this issue and has been monitoring for stability. This incident is now resolved.
Resolved
Beginning March 1, 2026, a power outage caused by physical damage to AWS infrastructure affected multiple Availability Zones in the AWS me-central-1 (UAE) region, resulting in the unavailability of CockroachDB Cloud clusters in that region. A single Availability Zone in me-south-1 was also impacted, causing degraded performance for clusters in that region. While AWS has not yet fully restored power to all affected Availability Zones, Cockroach Labs has directly engaged all customers impacted by this incident, providing resolution guidance and hands-on remediation assistance, including cross-region data restoration where applicable. As remediation steps have been completed or provided to all directly impacted customers, we are resolving this incident from Cockroach Labs' perspective. Cluster creation in the affected regions remains restricted pending full AWS recovery. Customers with outstanding questions or concerns are encouraged to contact Cockroach Labs Support.
Resolved
Our team has been monitoring for stability and have taken additional steps to help reduce database saturation. This incident is now resolved. More details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21498
Resolved
This incident has been resolved.
Resolved
On March 5th, 2026, between approximately 00:26 and 00:44 UTC, the Copilot service experienced a degradation of the GPT 3.5 Codex model due to an issue with our upstream provider. Users encountered elevated error rates when using GPT 3.5 Codex, impacting approximately 30% of requests. No other models were impacted.<br /><br />The issue was resolved by a mitigation put in place by our provider.
Resolved
The revert has deployed and we are no longer observing 403 Forbidden responses when downloading packages. We are resolving this incident.
Resolved
We're seeing error levels back to a normal level with no spikes over the last 20 minutes. As such, this issue is now considered resolved. If you still see the error messages, we recommend clearing Copilot chat by selecting the Settings icon at the top of the Copilot chat window. If that does not work, clear your browser's cookies and cache and then log back into Zapier. For any other issues or questions, please reach out to our support team at https://zapier.com/app/get-help
Resolved
The issue causing increased error rates when creating new Lovable Cloud projects has been resolved. Our infrastructure vendor has implemented a fix and project creation has returned to normal across regions. We have monitored the system and confirmed that services are operating normally. We apologize for the disruption and appreciate your patience while we worked to resolve the issue.
Resolved
Project creation recovery has been confirmed across all regions. Regional dashboards show error rates returned to normal, and previously failing project creation operations are succeeding again.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
We identified a small subset of customers with missing documents and repaired those indices with a manual update. Please report any search issues you may be seeing to support@mintlify.com so we can address if there are further repairs needed.
Resolved
This incident has been resolved.
Resolved
We've resolved the issue with customers using Android SDK seeing increased failures in attachments to conversations. We've released a new Android SDK version that will resolve this, but we have also implemented fixes to ensure backwards compatibility with older Android SDK versions. The latest Android SDK is available here: https://github.com/intercom/intercom-android/releases/tag/17.4.7 Our Developer Docs have details on how to do so here: https://developers.intercom.com/installing-intercom/android/installation All services are now working as expected. 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
We've resolved the issue with customers using Android SDK seeing increased failures in attachments to conversations. We've released a new Android SDK version that will resolve this, but we have also implemented fixes to ensure backwards compatibility with older Android SDK versions. The latest Android SDK is available here: https://github.com/intercom/intercom-android/releases/tag/17.4.7 Our Developer Docs have details on how to do so here: https://developers.intercom.com/installing-intercom/android/installation All services are now working as expected. 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
We've resolved the issue with customers using Android SDK seeing increased failures in attachments to conversations. We've released a new Android SDK version that will resolve this, but we have also implemented fixes to ensure backwards compatibility with older Android SDK versions. The latest Android SDK is available here: https://github.com/intercom/intercom-android/releases/tag/17.4.7 Our Developer Docs have details on how to do so here: https://developers.intercom.com/installing-intercom/android/installation All services are now working as expected. 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
We've monitored the fix we implemented and sidebar apps are now loading. Thanks for your patience as we investigated and fixed this issue.
Resolved
All impacted services have now fully recovered.
Resolved
This incident has been resolved.
Resolved
The delays in SIM card management actions have been resolved. All operations are processing normally.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
After monitoring, it looks like sidebar apps are loading once more. It seems that the fix is working and we're going to close this one out!
Resolved
The issue with Start Page editor have been fully resolved, and it’s functioning as expected again. If you encounter any further problems, please don’t hesitate to reach out to our team.
Resolved
We scaled our systems and are able to process data in time. Single projects may still be delayed.
Resolved
The connectivity issues with Outlook have been successfully resolved. Please refresh your browser to access the platform. Thank you for your patience!
Resolved
The issue has been resolved - we're still investigating the root cause and will post more details once we have them.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Between 15:52 UTC March 10, 2026 and 11:00 UTC March 11, 2026, customers may have experienced failures when creating new Datadog and OTel collector integrations. Existing integrations remained unaffected. The issue has been fully resolved. All affected components are operating normally again.
Resolved
We scaled our systems. APIs should respond fast again.
Resolved
Users may have seen tools and integrations that rely on older MongoDB Atlas Admin API versions (for example, 2023-01-01 and 2023-02-01) start failing with HTTP 410 responses indicating that the requested version was no longer available. This affected workflows using the MongoDB Atlas Admin API through the Terraform provider, the Atlas CLI, and custom automation. This behavior was triggered by our planned retirement process for older API versions, but the resulting user impact was unintended because these versions were still in active use. We have extended the end-of-life date for the affected API versions to mid-2027 (tentative date 2027-07-01) and deployed a configuration change to restore compatibility for these workflows. All affected tools and integrations should now be operating normally & will be updated prior to the modified end-of-life-date. From 2026-03-01 00:00 UTC to 2026-03-02 12:01 UTC, users relying on these older API versions may have experienced failed requests and associated automation errors. No user action is required. Previously failed operations can be retried and should now succeed.
Resolved
This incident has been resolved.
Resolved