NotionOperations such as duplicate a page or move a block
This incident has been resolved.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
This incident has been resolved.
Resolved
The issue has been resolved.
Resolved
Unfortunately, we determined that failed uploads from recordings cannot be recovered, and we recommend deleting these videos from your library, and re-recording the video. We apologize for the inconvenience.
Resolved
We've resolved the issue.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
A huge spike in client page traffic caused dashboard page latencies to increase due to the increased CPU load. We migrated client routes to a separate cluster to resolve this issue
Resolved
Between 5:20pm UTC to 5:35pm UTC, Notion was experiencing degraded performance but this is now resolved.
Resolved
Issue resolved. Customers can now upload assets through the web app as usual.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Between 16:00 UTC January 13th and 08:00 UTC January 14th our team was alerted to an issue causing long delays completing Salesforce syncs. The issue has now been resolved and we are continuing to monitor.
Resolved
We've experienced processing delays of up to 1h30min for sending emails to yahoo.com domain in the EU and US regions.
Resolved
The issue has now been resolved.
Resolved
This incident has been resolved.
Resolved
Anthropic has resolved the issue and we're no longer seeing issues on our end. Thank you for your patience.
Resolved
This incident is resolved. Our upstream AI provider has recovered and Content Agent and Canvas error rates have returned to normal.
Resolved
Incident Summary — Intermittent Voice API Failures (India Region) Incident Window: 12 January, 10:30 AM IST — 11:46 AM IST Impact: Intermittent failures were observed across multiple Voice APIs in the India region, including make call API requests returning HTTP 502 errors. The service was not continuously unavailable, but experienced periodic degradation during the incident window. Summary On 12th January between 10:30 AM and 11:46 AM IST, intermittent failures were observed in Voice APIs in the India region. The service remained available for most of the time, but experienced periodic spikes of failures. The incident was triggered by a spike in CPU utilization on Plivo’s CDR database, which reached 100%, driven by a high volume of list CDR API requests. To contain the database overload, the rate limit quota for list CDR APIs was reduced. During this containment window, some list CDR API requests returned 5xx responses intermittently. These 5xx responses interacted incorrectly with the API Gateway’s circuit breaker logic. The circuit breaker marked the upstream service as unhealthy but failed to route traffic to the configured failover upstream. This caused traffic to be dropped instead of being rerouted, resulting in intermittent 502 errors across a wider set of APIs, including the make call API.
Resolved
This incident has been resolved.
Resolved
This issue has now been resolved. A fix has been implemented and deployed with Sanity Studio version 5.3.1.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
We've confirmed that the elevated 5xx errors and high response times were isolated to the ap-southeast-1 region. Other regions remained healthy throughout the incident. Dashboards showed a sharp spike in 5xx errors and response times for ap-southeast-1, with metrics rapidly recovering after remediation steps. For more details, see the realtime-service combined dashboard. The incident was the result of a resource constraint. We have added the required resources and will take this into account in our future planning. We're continuing to monitor system health to confirm stability.
Resolved
The backlog of unpublished decision logs has been resolved and the system is operating normally.
Resolved
All impacted services have now fully recovered.
Resolved
We have identified and solved the issue at hand. Optimal query performance should not be restored.
Resolved
Between 4:05 PM and 4:58 PM ET, some SMS messages experienced a temporary delivery delay. The issue has been fully resolved. All delayed messages were safely queued and are now being delivered. No messages were lost. Our systems are operating normally, and our team is monitoring to ensure continued stability.
Resolved
This incident has been resolved. Please reach out to support@mintlify.com "support@mintlify.com": mailto:support@mintlify.com if you are experiencing issues with signup or login.
Resolved
This incident has been resolved. If you were affected by this behavior, please clear your browser's cache and refresh the page before trying to navigate across apps.
Resolved
On January 7th, 2026, between 17:16 and 19:33 UTC Copilot Pro and Copilot Business users were unable to use certain premium models, including Claude Opus 4.5 and GPT-5.2. This was due to a misconfiguration with Copilot models, inadvertently marking these premium models as inaccessible for users with Copilot Pro and Copilot Business licenses.<br /><br />We mitigated the incident by reverting the erroneous config change. We are improving our testing processes to reduce the risk of similar incidents in the future, and refining our model availability alerting to improve detection time.
Resolved
This incident has been resolved.
Resolved
The fix was successful, and the prompts endpoint latency is back to normal. We’re no longer seeing issues and will continue to monitor.
Resolved
This incident has been resolved.
Resolved
Issue resolved. Context: We experienced 5xx errors on POST /api/public/dataset-items due to a migration sequencing failure. • Root Cause: A column was dropped before the code deploy finished, while the Prisma ORM was still attempting to write to that deprecated field. • Status: Resolved; all containers are now running the updated code. • Prevention: We will strictly enforce "Expand and Contract" patterns for all future schema deletions.
Resolved
The issue related to transcription for EU residency server on the Agents platform has now been resolved.
Resolved
The incident is now resolved and the system is full operational.
Resolved
This incident has been resolved.
Resolved
The fix has been implemented and the issue has been resolved.
Resolved
Remediation measures have been fully rolled out, restoring failure rates to baseline. The root cause has been addressed, and the issue is now fully resolved.
Resolved
Between 03:39 PM (UTC -05:00) and 06:40 PM (UTC -05:00), a small number of customers in all affected regions experienced issues with marketing emails. This was caused by a database impairment. As of 06:40 PM (UTC -05:00), our marketing emails are working properly and the incident has been fully resolved. HubSpot conducts a thorough review after each incident to understand the cause and prevent it from happening again. Learn more about HubSpot's commitment to reliability at www.HubSpot.com/reliability. The information on this page reflects our understanding of the incident and impact at the time of the update.
Resolved