LangfuseElevated ingestion API latencies in US region
Ingestion API are back to normal
Resolved
Outages and recoveries from the services you depend on.
40 incidents
Ingestion API are back to normal
Resolved
Between 10:56 AM (UTC -04:00) and 11:30 AM (UTC -04:00), many customers in all affected regions experienced issues with generating quotes from deal records. As of 11:30 AM (UTC -04:00), quote generation is 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
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The connectivity issue which affected Zapier Agents during a 15 minute window is fully resolved. Agent executions are back to normal, and connectivity remains stable. If you have any questions, please reach out to our support team at: zapier.com/get-help.
Resolved
This incident has been resolved.
Resolved
The issue has been resolved.
Resolved
On April 9, 2026, between 09:05 UTC and 19:05 UTC, the Copilot coding agent service was degraded and users experienced significant delays starting new agent sessions. Approximately 84% of new agent session requests were delayed across four separate outage waves, with queue wait times peaking at 54 minutes compared to a normal baseline of 15–40 seconds. On average, the error rate was 83.9% and peaked at 97.5% of requests to the service. Approximately 22,700 workflow creations were delayed or failed during the incident.<br /><br />This was due to a bug in our rate limiting logic that incorrectly applied a rate limit globally across all users, rather than scoping it to the individual installation that triggered the limit. A contributing factor was a surge in API traffic from a client update that increased requests to an internal endpoint by 3–4x, which accelerated rate limit exhaustion.<br /><br />We mitigated the incident by disabling the faulty rate limit caching mechanism via feature flag and updating our service to use per-installation credentials for API calls, ensuring rate limits are correctly scoped to individual installations.<br /><br />We have since added automated monitoring and alerting to detect this failure mode proactively, deployed fixes to reduce unnecessary API traffic through caching improvements, and are continuing work to further isolate rate limit scoping across client types to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/2rqwxl8y7m0j
Resolved
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue, with wait times peaking at 54 minutes compared to the normal 15–40 seconds. On average, approximately 84% of requests to start agent sessions failed, peaking at 97.5% during the worst period.<br /><br />This was due to an internal service exceeding API rate limits, compounded by a caching bug that persisted the rate-limited state beyond the actual rate limit window, causing recurring outage waves rather than a single recovery.<br /><br />We mitigated the incident by deploying a configuration change to bypass the affected cache and shifting API traffic to an alternative authentication path that reduced rate limit exposure. We have since added automated monitoring and alerting for this failure mode, deployed per-endpoint rate limit controls, and added caching for high-traffic API calls to reduce overall load. We are also working on longer-term improvements to rate limit isolation and traffic management to prevent similar issues in the future.<br /><br />This incident shared the same underlying root causes with an incident declared in the time frame https://www.githubstatus.com/incidents/zn1t56bfxdzg
Resolved
This incident has been resolved.
Resolved
An issue has been identified, we’re looking into it There’s currently an issue with some SumUp services. Our engineering team is working to fix it right now. You can find up-to-date information here on our status page "status page": https://status.sumup.com.
Resolved
This incident has been resolved.
Resolved
All issues have been resolved and there should be no further delays in ALIAS record resolution.
Resolved
We’ve traced the email delivery failures to hard bounces and automatic suppressions affecting specific recipient addresses. We're resolving this incident.
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
The incident has now been resolved. The system is now operational.
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
This incident has been resolved.
Resolved
We have identified the source of the intermittent resolution issues and resolved it. If you're still experiencing this kind of issues, please email support@dnsimple.com with traceroutes and dig trace queries if you can.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved, and we are not seeing further routing issues. If you have any issues reach out at support@dnsimple.com
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
This incident has been fully resolved and we have not seen any further errors. If you see any problems please reach out at support@dnsimple.com
Resolved
We are not seeing any more latency or issues in San Jose. if you are seeing any more issues please let us know at support@dnsimple.com
Resolved
This incident has been resolved.
Resolved
This network issue has been resolved fully. If you have any further issues please let us know by emailing support@dnsimple.com
Resolved
This incident has been resolved.
Resolved
The update has finished and all assets are now being served correctly.
Resolved
The issue has been fully resolved. Services are back to normal.
Resolved