RunwayAleph 2.0 delayed generations
This incident has now been resolved.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
This incident has now been resolved.
Resolved
This incident has been resolved, and we apologize for the inconvenience this issue has caused. Please reach out to support@airtable.com if you have any further questions.
Resolved
Issues related to Airtable errors are resolved. Any missed triggers and/or actions are replayed. If you have any questions, you can always reach out to our support team here: https://zapier.com/app/get-help
Resolved
Edge function operations are normal.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This issue is now resolved.
Resolved
The Cloud Console is back up.
Resolved
Project creation has returned to normal. The issue is now resolved.
Resolved
API errors have been resolved. The Keeper Gateway and KSM client version is no longer returning an error.
Resolved
This incident has been resolved.
Resolved
The Webflow MCP Server is operating as expected, and this incident is now resolved. If any tools are still missing in the Claude apps, refresh the tool list by following these steps: 1. Go to Settings. 2. Select Connectors. 3. Click the Webflow connector. 4. Click the three-dot menu. 5. Select Refresh tool list. Thank you for your patience while we worked through this issue.
Resolved
This issue has been resolved.
Resolved
We experienced an increased error rate across multiple services between 17:04 UTC to 17:13 UTC on July 8th in the US region. We are investigating why this happened to prevent recurrence.
Resolved
This incident has been resolved.
Resolved
The fix has been completed in production. This incident is now resolve. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22470
Resolved
The incident is now resolved and the system is full operational.
Resolved
Our forensic investigation into the June 2026 Klue/Salesforce incident, conducted in partnership with Mandiant, is now complete. The investigation confirmed that the impact was limited to business CRM data. No evidence of impact to the Snyk platform, and any sensitive data within, was found. All impacted customers were notified directly and the data involved is consistent with what was disclosed in our June 22 blog post (https://snyk.io/blog/when-a-vendors-breach-becomes-yours-lessons-from-the-klue-incident/).
Resolved
The issue is now fully resolved and all users should be able to login as normal.
Resolved
We have new information regarding the incident that affected your service(s). Please find below an update on the situation: <b>Update :</b> PostGIS support for PostgreSQL 18 was introduced in a newer PostGIS version. However, an identified defect carries a risk of data corruption for geospatial data, so we have chosen not to enable it on our offer yet. We are waiting for a PostGIS release that fixes this issue before allowing PostGIS to be used on PostgreSQL 18. As a reminder, this only affects customers using the PostGIS extension. PostgreSQL instances that do not use PostGIS are not impacted. In the meantime, we still strongly recommend that PostGIS users postpone any upgrade to PostgreSQL 18 and remain on PostgreSQL 17, which is fully compatible with PostGIS. <b>Ongoing Actions :</b> The incident has been identified and corrected. It is being closely monitored to ensure long-term stability. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
Degraded
We haven’t observed any additional issues with the Cloud Pulse Metrics (ACLP Metrics) service, and will now consider this incident resolved. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.
Resolved
Between 06:22 and 08:23 UTC on July 8, requests to our US error reporting API (api.honeybadger.io) experienced a highly elevated failure rate. During this window, a majority of requests to submit errors, events, and check-ins received 5xx responses or timed out. Error reports sent by client libraries without retry logic during this period were not received and cannot be recovered. The Honeybadger web application, dashboards, uptime monitoring, and our EU region were not affected. What happened: Beginning at 06:18 UTC, we started receiving error reports at roughly triple our normal total API volume. The service tier that ingests this traffic was at its overnight capacity level and became saturated. Our autoscaling responded, but the metrics it relied on significantly under-measured the failed traffic, so capacity was added far too slowly — full recovery came at 08:23 UTC when scaling caught up and absorbed the load. Compounding the problem, PagerDuty alerts were not fired to wake up a human due to a misconfiguration. What we've done: We've fixed the underlying scaling weakness: API capacity now also scales directly on load-balancer error rates (previously we scaled only on request rates, and that scaling doesn't respond quickly enough), and we've doubled the maximum capacity of the ingestion tier. These changes are already deployed to both US and EU regions. We're also evaluating adding adaptive per-key rate limiting to the ingestion service. We're sorry for the disruption, and for any gaps this caused in your error data during the window.
Resolved
Accelerate is operating within normal tolerances.
Resolved
Error rates in the real-time update system have returned to normal.
Resolved
This incident has been resolved. The authentication failures were due to a service becoming unreachable, and we have worked to restore the service. Approximately 1 in 10 requests between 08:40 and 10:00 UTC were affected, and the issue in this period was intermittent.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Between 20:22 UTC on July 6 and 08:40 UTC on July 8, a small number of responsive image variants on some hosted sites returned 403 errors on some requests. This issue was limited to a very small subset of responsive image variants and did not affect all images or all hosted sites. If your site was impacted by this issue, you can restore access to the affected image variants by republishing your site. We sincerely apologize for any inconvenience that this issue caused, and appreciate your patience and understanding while we worked to resolve it.
Resolved
This incident has been resolved.
Resolved
The issue has been resolved.
Resolved
Between 7:22 UTC and 8:16 UTC on July 08, 2026, customers in ap-southeast-1 region may have experienced delays with creating branches or projects, and with starting computes for existing endpoints. A subset of customers may have observed delays in Console API operations. Running computes were not affected. The issue has been fully resolved, and all services are operating normally. We apologize for any inconvenience
Resolved
We identified an issue where a subset of stores may see unexpected Staff Action Log entries generated by an API-driven background process. These entries are display-only logging artifacts and do not reflect staff user activity or changes made to the store. Some entries may continue to appear while we complete remediation. Store functionality, data, and security are not impacted, and no action is required.
Resolved
Issue has been identified, a fix was set in place and service was confirmed to be restored.
Resolved
A fix has been deployed and we have confirmed no further failures since the rollout. Users signing up for a Teams trial from our pricing page should now receive a Teams trial with access to Teams features. This incident is resolved. If you're experiencing any other issues with your account, please contact Support at https://zapier.com/app/get-help.
Resolved
On July 2nd, 2026, between approximately 15:00 and 18:30 UTC, the GitHub Pages service experienced degraded deployment performance due to a surge in demand that exceeded available processing capacity. During this period, users publishing to GitHub Pages may have seen their deployments queued or taking substantially longer than usual to go live. No other GitHub services were impacted.<br /><br />We mitigated the incident by scaling up Pages deployment workers and provisioning additional storage capacity to clear the backlog.<br /><br />GitHub is reviewing capacity planning and autoscaling measures to reduce the likelihood of similar delays in the future.
Resolved
**What Happened:** Today, following a gradual rollout of a new feature, our platform experienced widespread cross-system performance degradation. While most features continued to work, a heavy load on our database impacted overall service availability, causing automations to run slowly and the automations store and agents to occasionally fail to load. **Please note that at no point was any data lost or compromised.** **Timeline:** * **US Region:** 15:30 – 17:10 UTC \(1 hour and 40 minutes of degradation\) **What caused it:** A new Dynamic Client Registration \(DCR\) feature for OAuth \(supporting MCP applications\) caused an unexpected chain reaction. Even with the limited rollout of this feature, frequent automated DCR requests triggered a continuous, global cache invalidation storm across our core caching infrastructure. With this shared cache repeatedly cleared, all traffic was directed straight to the database, causing a severe CPU spike. **How we responded:** Our engineering team identified the source and immediately performed a significant system scale-up to handle the extreme load. We then disabled the DCR endpoint in production. This stopped the cache invalidation loop, restoring database stability and returning system performance to normal. **What we're doing to prevent recurrence:** Moving forward, we plan to use a setup that will take the load off core caching systems. Because this was a limited gradual rollout, turning it off has zero impact on your current workflows or integrations. We sincerely apologize for any disruption this caused to your workflow. Thank you for your understanding as we work to continuously improve our platform's reliability. Your team at [**monday.com**](http://monday.com)
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
Incident has been resolved, default variant set to the correct one for the HIPAA framework.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved