LiveblocksElevated API Errors in Europe and APAC
This incident has been resolved.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
This incident has been resolved.
Resolved
On July 14, 2026, several packages in the @asyncapi npm namespace were compromised in a supply chain attack. An attacker exploited a misconfigured GitHub Actions workflow in the AsyncAPI generator repository to steal a publish token and release malicious versions of @asyncapi/specs (6.11.2, 6.11.2-alpha.1), @asyncapi/generator (3.3.1), @asyncapi/generator-components (0.7.1), and @asyncapi/generator-helpers (1.1.1). We reviewed our dependency tree and confirmed Mintlify is not affected: - We do not use @asyncapi/generator, @asyncapi/generator-helpers, or @asyncapi/generator-components anywhere in our codebase. - The only @asyncapi packages we depend on are @asyncapi/parser (not compromised) and @asyncapi/specs, which our lockfiles pin at 6.11.1 and 6.8.1 — both below the compromised 6.11.2. We will keep specs pinned below 6.11.2. - The malicious versions were never installed in our development, CI, or production environments, and we found no signs of impact. Mintlify's AsyncAPI documentation features continue to work normally and were never at risk. No action is required on your part.
Resolved
This incident has been resolved. A recent API Gateway deployment altered how certain special characters in S3 object key paths were encoded before reaching storage, causing signature verification failures (403) for affected requests. The change has been reverted and issue is now fixed.
Resolved
This incident has been resolved.
Resolved
Recent feature roll-outs added extra load to our databases, and a fix has been implemented. Thank you for your patience while we worked to resolve this.
Resolved
On July 14, 2026, at 10:57 UTC, Akamai identified an increase in 502 errors and latency affecting customers using the Linode API, CLI, and Cloud Manager. This disruption resulted in moderate service impact, with customers reporting elevated error rates. Our initial investigation traced the issue to latency with IAM services, which was resolved, but elevated errors persisted. Further analysis by relevant subject matter experts determined that the incident was triggered by a manual failback to the Cloud IAM primary load balancer from the secondary load balancer. This action was prompted by a warning alert indicating that the secondary load balancer was acting as the keepalived master. The manual process of starting and stopping services to initiate the failback differed from the automated process and led to a cascade of stale GRPC connections, causing increased latency and API errors. Restarting the API servers cleared the stale connections and restored normal operations. Customer impact was mitigated by approximately 13:10 UTC on July 14, 2026. To prevent recurrence, Akamai is investigating why the manual failback caused this behavior. The team is considering implementing a drain command to clear GRPC connections during failover and setting up alerts to detect stale connections for proactive intervention. However, the immediate focus remains on understanding the root cause, with alerting and automation planned for later phases. Several customers have confirmed resolution across their deployments. Akamai will continue to monitor system health and await additional customer feedback before declaring full recovery. This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing and any information herein is subject to change.
Resolved
Our Engineering team has confirmed that the underlying issue affecting Reserved IP routing in the TOR1 region has been fully resolved, and services are now operating normally. If you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.
Resolved
This incident has been resolved.
Resolved
We identified an issue with an upstream service provider. The issue is resolved now.
Resolved
This issue has been resolved and service is operating normally.
Resolved
This incident is now resolved.
Resolved
The issue affecting the availability of some Webflow MCP Server tools in the Claude Desktop app and claude.ai has now been resolved. All Webflow MCP tools should now be available in the Claude connector. If you previously experienced missing tools, restarting Claude Desktop or refreshing claude.ai may help ensure the latest tool list is displayed. We’re no longer seeing customer impact related to this issue. Thank you for your patience while we worked to resolve it.
Resolved
This incident has now been resolved and the service is now fully operational.
Resolved
All impacted services have now fully recovered.
Resolved
We have confirmed that error rates have returned to baseline.
Resolved
This incident has been resolved.
Resolved
We experienced a delay in webhook delivery for TEST sites during the window from July 19th 09:49 UTC to July 19th 12:12 UTC, and the services are functioning as expected. We apologize for any disruption this caused to your testing workflows.
Resolved
Amazon has resolved the CloudFront service outage, and our services are back to normal.
Resolved
Amazon has resolved the CloudFront service outage, and our services are back to normal.
Resolved
The issue impacting the AWS eu-central-1 region has now been resolved. All clusters are fully operational and healthy.
Resolved
This incident has been resolved.
Resolved
Throughput and latency have recovered and the system should be fully operational again. The core issue is related to the part of the system that persists run state. Some operations experienced and increase in errors and retries, causing a backlog in some parts of the system and some failed operations like checkpoints or signals. We are continuing a thorough post-mortem investigation to prevent reoccurrance.
Resolved
We experienced intermittent API request timeouts in the EU region during the window from 15-7-2026 21:56:00 UTC to 16-07-2026 01:23:55 UTC. The issue has since been resolved, and services are operating normally.
Resolved
We've resolved the issue with email delivery delays.
Resolved
This incident has been resolved.
Resolved
The mitigation work for this incident has been completed, and we have not observed any further impact following the restoration of affected projects. This incident is now resolved. If you continue to experience issues that you believe are related to this incident in eu-central-1 (Frankfurt), please open a support ticket and our team will investigate.
Resolved
We have confirmed that our change has returned stability to the service
Resolved
This incident is resolved
Resolved
All Granola services should be operational - we're sorry for any disruption. If you're still having problems, head to our help center at help.granola.ai "help.granola.ai": http://help.granola.ai.
Resolved
This incident has been resolved.
Resolved
The issue is resolved. SSO is working fine again.
Resolved
This incident has been resolved.
Resolved
Cybersource has mitigated the issue on their end, but monitoring. We are no longer seeing any issues with payment processing
Resolved
SSO and Google logins in the Plaid Dashboard are now performing as normal.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The missing Build CPU Minutes data has been backfilled. Users with missing Build CPU Minutes data will be able to see it on Usage pages in the Vercel Dashboard.
Resolved
Issue confirmed by our auth provider, waiting for root cause. A configuration update caused some legitimate authentication-related requests to be incorrectly blocked.
Resolved
We have reverted to an older configuration to avoid an AWS outage with Cloudfront.
Resolved
Partial outage due to http parsing errors. Problem was resolved couple minutes later. If problem continues, refreshing the DNS cache is recommended.
Resolved