NotionHigh latency issue affecting login
This incident is now resolved.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
This incident is now resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
We're all set! PandaDoc is working properly and the incident has been fully resolved. If you continue to experience issues with this, please contact our Support team (https://support.pandadoc.com/en/articles/9715061-how-to-contact-pandadoc-support).
Resolved
This incident has been resolved.
Resolved
We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
Resolved
The fix has been properly released. Thank you for your patience and sorry for the inconvenience.
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
On April 23, 2026, between 16:03 UTC and 17:27 UTC, multiple GitHub services experienced elevated error rates and degraded performance due to DNS resolution failures originating from our DNS infrastructure in our VA3 datacenter. Approximately 5–7% of overall traffic was affected during the impact window: <br /><br />- Webhooks: ~0.35% of API requests returned 5xx (peak ~0.39%). ~0.88% of requests exceeded 3s latency; at peak, >3s responses represented ~10% of Webhooks API traffic. <br /><br />- Copilot Metrics: ~9% of Copilot Insights dashboard requests returned 5xx. <br /><br />- Copilot cloud agents: ~10% of cloud agent sessions were affected and failing. <br /><br />- Octoshift: 0.88% of active repo migrations failed and 79% saw elevated durations (avg. 5.2 min) during this period. <br /><br />- Git Operations: averaged 1.25% errors over the duration of the incident, with a peak of 2.07% errors. <br /><br />- Actions: Workflow run status updates experienced delays of up to ~8s over the duration of the incident window. <br /><br />Our DNS infrastructure in VA3 entered a degraded state and began intermittently returning NXDOMAIN responses and timing out on lookups for both internal service discovery and external endpoints. This caused a cascading impact across the dependent services listed above. <br /><br />We identified a specific load pattern under which our DNS resolvers began failing. The evidence points to a recently introduced traffic-balancing mechanism, rolled out progressively to support our growth, as the root cause. We have since reverted this change. <br /><br />We are immediately prioritizing investments in a more controlled rollout and validation process, including a dedicated environment to safely shadow production DNS traffic and detect these failure modes before they can affect production.
Resolved
With the configuration changes, we were able to process the backlog and jobs are being processed normally. More details can be found in the issue: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21936
Resolved
We are confident the issue is fully resolved.
Resolved
Between April 23 and April 29, some customers in experienced issues with publishing Instagram posts. This was caused by an integration issue. As of April 29 6:17 PM, our social publishing tools 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
The issue causing intermittent delays in our webhook delivery has been resolved. A fix was deployed to address a resource constraint in our systems. Our monitoring shows webhook delivery is now operating normally.
Resolved
Between 9:45 AM EDT (UTC -04:00) on Apr 30, 2026 and 10:30 AM EDT (UTC -04:00) on Apr 30, 2026, some customers experienced errors when creating or updating workflows. The root cause has been resolved, and no data was lost. We apologize for any inconvenience and appreciate your patience as we resolved the issue.
Resolved
The incident affecting Retain settings and Metrics in the dashboard has been fully resolved. All services are now operating normally. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact our Customer Support team at sellers@paddle.com.
Resolved
Between 12:07 UTC and 12:40 UTC April 30, 2026, customers may have experienced failures while creating or deleting branches, or projects. Existing database connectivity remained unaffected. The issue has been fully resolved. All affected components are operating normally again.
Resolved
This incident has been resolved.
Resolved
We've caught up on the streaming data export backlog.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The external provider has restored operations. All models are now available.
Resolved
This incident has been resolved, and [problem] should be functioning as expected.
Resolved
This incident has been resolved.
Resolved
This has been resolved.
Resolved
We have resolved the incident.
Resolved
Starting on **April 20th, 2026 at 10:00 AM PDT**, a combination of scaled-up background action jobs in the EU and a recent change to how date time trigger volume is managed overloaded the system that processes resource intensive background action jobs. This caused multi-hour delays in email and inbox notifications in the EU and prevented date time triggers from executing in all regions. Engineers were first alerted on **April 21st** by our monitoring systems, but did not recognize the full scope of the incident until **April 23rd**. On April 23rd, the change to manage date time trigger volume was reverted and the problematic background action jobs were isolated. All delayed notifications were sent by **April 24th, 11:30 AM PDT**, and all delayed date time triggers were executed by **April 27th, 4:00 AM PDT**.
Resolved
Starting on **April 20th, 2026 at 10:00 AM PDT**, a combination of scaled-up background action jobs in the EU and a recent change to how date time trigger volume is managed overloaded the system that processes resource intensive background action jobs. This caused multi-hour delays in email and inbox notifications in the EU and prevented date time triggers from executing in all regions. Engineers were first alerted on **April 21st** by our monitoring systems, but did not recognize the full scope of the incident until **April 23rd**. On April 23rd, the change to manage date time trigger volume was reverted and the problematic background action jobs were isolated. All delayed notifications were sent by **April 24th, 11:30 AM PDT**, and all delayed date time triggers were executed by **April 27th, 4:00 AM PDT**.
Resolved
We've identified an infrastructure issue that caused some 503 responses in feature flagging streaming client initialization on the US LaunchDarkly instance between 16:45 and 17:05 PT. SDKs should automatically retry initialization in most cases.
Resolved
This incident has been resolved.
Resolved
This incident is now resolved. Thank you for your patience and understanding.
Resolved
This incident has been resolved.
Resolved
All impacted services have now fully recovered.
Resolved
Our team has confirmed the full resolution of the issue affecting our EUROPE-1 Managed Object Storage in our FI-HEL2 data center. All affected services should now be functioning normally. If you continue to experience any further issues, please contact our Support team via Live Chat or email support@upcloud.com Thank you for your patience and we apologize for any inconvenience caused.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
We have confirmed that latency and error rates have returned to normal for impacted customers.
Resolved
We've addressed an issue that prevented warehouse data export from 12pm to 6pm PT on April 23. All missing data has been retroactively pushed to customer warehouses.
Resolved
https://www.heygenverse.com/a/f2f4f441-aa1a-4ada-9200-aa7d1a79e07f
Resolved
This incident has been resolved.
Resolved