ReplitFixed: Agent Messaging Degraded
We have resolved an earlier issue where some users were unable to send messages to the agent.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
We have resolved an earlier issue where some users were unable to send messages to the agent.
Resolved
We've resolved the issue. The Agent chat footer should be fully accessible.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
On July 29, 2026, from 14:51 UTC to 15:28 UTC, GitHub Actions experienced elevated REST API request timeouts and errors, failures registering runners, and delayed workflow run starts for customers whose traffic was served by a single infrastructure site. This was caused by an under-provisioned internal Actions service in that site: under increased load its instances ran out of memory and became unresponsive, and because Actions API requests wait synchronously on that service, requests routed through the affected site stalled and timed out. During the incident, approximately 2% of workflows were delayed. Requests served by other sites remained unaffected. Both standard and larger hosted runners routed through the affected site could see delayed job starts. <br /><br />The issue was mitigated by scaling out the runner-administration service in the affected site and increasing the replica count, which restored API availability and returned workflow run starts to normal. We are working to add horizontal autoscaling, memory-saturation alerting, and scaling-forecast monitoring for this service, along with responder playbooks, to reduce the likelihood of similar issues in the future.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
This incident has been resolved.
Resolved
The issue affecting Grafana IRM in the EU region has been resolved. The IRM UI, public API, and alert notification processing have been restored and are operating normally.
Resolved
For 97 minutes, GitHub events were not reaching Entire. Repository mirrors did not update, and pull request and check status could appear stale or out of date. The cause has been fixed and verified. We have replayed the affected events, so mirrors, pull requests, and branch activity from that window are now reflected in Entire.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
We recently addressed issues affecting Shuttle \(migration service\). We would like to take the opportunity to further explain these issues and the steps we have taken to keep them from happening in the future. Between 03/24/2026 08:00 PM PDT and 03/25/2026 11:40 AM PDT on Mar 24–25, 2026 — some users may have experienced difficulties while working in Box. During this time, users reported blank pages, timeouts, and failures when configuring or running migration jobs in the Shuttle interface. The issue occurred after a vendor-managed database maintenance update that included an operating system and security library change, which caused the affected database clusters to enter a read-only or degraded state and prevented normal job configuration and history access. We were able to resolve the issue after the vendor reverted the change on the affected clusters and our teams restarted the dependent services, after which we verified normal operation. In addition, we will take steps to reduce the likelihood of recurrence by improving coordination and testing for vendor-managed upgrades and strengthening our operational safeguards. # Analysis This incident highlighted risks in relying on vendor-managed platform updates without staged validation across environments, and showed gaps in how quickly we could detect and isolate read-only database states. Response required close vendor collaboration to identify and revert the change; internal mitigations \(service restarts and connection management\) were insufficient until the vendor rollback completed. We will improve pre-upgrade controls, monitoring for early signs of degraded database state, and runbook guidance for faster mitigation. # Corrective Actions Box has initiated the following corrective actions: * Require staged validation of vendor-managed platform upgrades \(dev → staging → production\) before production rollout. * Establish a coordinated upgrade/runbook with the vendor that defines pre-checks, rollback steps, and escalation pathways. * Enhance monitoring and alerts for read-only database states, failed elections, and connection saturation to detect similar issues earlier. We are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter. Sincerely, The Box Team
Resolved
We have resolved the issues related to creating/adding new topics in Lumen. If you continue to have issues creating/adding Topics in Lumen please reach out to our customer support team. Thank you for your patience.
Resolved
Our Engineering team has pulled v6.57.0 of the AWS provider from the registry and published a fixed v6.57.1.
Resolved
Between 06:39 and 18:11 UTC on July 20, 2026, the Copilot service experienced a degradation of the GPT 5.3 model due to an issue with our upstream provider. The upstream model provider returned intermittent errors for GPT 5.3 Codex requests, which caused some responses to fail. Auto mode requests that had selected GPT 5.3 Codex were also impacted. On average about 2% of GPT 5.3 Codex requests failed during this window. Copilot automatically routed eligible traffic away from the impacted provider to reduce customer impact. No other models were impacted.<br /><br />We worked with the upstream provider throughout the incident and confirmed sustained recovery before resolving.
Resolved
We recently addressed issues affecting Authentication, File Access, Notes, Uploads, and Public API. We would like to take the opportunity to further explain these issues and the steps we have taken to keep them from happening in the future. On June 3, 2026 between 10:53 PM and 10:58 PM PDT, some customers may have experienced issues when attempting to sign in to Box and when accessing files, notes, uploads, and our public API. The issue was caused by a temporary fluctuation in a database shard due to elevated disk activity, which led to connection saturation and service errors for a subset of users. Service returned to normal by 10:58 PM PDT and monitoring remains in place to watch for recurrence. # Analysis As part of our routine system maintenance, we deployed standard software updates to our infrastructure. Following these updates, a scheduled background system scan processed a larger-than-normal volume of files. This background activity led to temporary resource contention on the database tier, resulting in brief latency and connection saturation for a subset of users. While Box utilizes redundant database replicas to ensure high availability, our automated monitoring and failover systems did not immediately redirect traffic because the database remained partially responsive. # Corrective Actions Box has initiated the following corrective actions: * Implemented strict I/O resource limits on background maintenance processes to ensure they cannot impact active user traffic. * Upgraded our database monitoring and health checks to immediately detect and alert on localized resource contention, ensuring faster automated failover response. We are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter. Sincerely, The Box Team
Resolved
This incident has been resolved.
Resolved
We recently addressed issues affecting Box Relay. We would like to take the opportunity to further explain these issues and the steps we have taken to keep them from happening in the future. Between 1:10 AM and 11:33 PM PT on July 14, 2026, some users may have experienced difficulties while working in Box. During this time, some users may have experienced degradation of Box Relay workflows that include a task outcome. The issue occurred as a result of a recent code change intended to improve how task assignments are handled in workflows. We were able to resolve the issue by reverting that change and restoring the previous behavior. In addition, we are improving our automated testing, monitoring, and deployment safeguards to prevent similar issues from occurring in the future. **Analysis** A Box Relay workflow can include a task outcome, which assigns a task to one or more people. As part of that outcome, the workflow also attempts to give each assignee access to the relevant file. A recent change caused the entire task outcome to fail whenever that access-granting operation was rejected. Such a rejection is an expected condition in some configurations \(_e.g._, when the person who owns the workflow does not have sufficient permission to share the file, or when sharing restrictions are in place\) and it can occur even when the assignee already has access to the file. Previously these rejections were tolerated and the task was still created. After the change, they caused the task outcome to fail, so affected workflows stopped completing. **Corrective Actions** Box has initiated the following corrective actions: * Adding automated test coverage for this scenario to prevent similar regressions. * Adding monitoring and alerting for workflow-processing failures, so this class of issue is detected proactively rather than through customer reports. * Refining the task-assignment logic to avoid unnecessary access-granting operations when an assignee already has access to the file. We are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter. Sincerely, The Box Team
Resolved
Between July 24, 19:17 UTC and July 24, 20:02 UTC, users were unable to create pull requests due to a database schema change. In total, 113,930 pull request creation attempts were impacted across 50,904 users, with an average error rate of 1.75% and a maximum error rate of 2.25% for all requests to Pull Requests service. Existing pull requests and other GitHub functionality were not affected. The issue was resolved by reverting the change to the affected database, upon which pull request creation immediately resumed.<br /><br />The root cause was related to a backfill workflow into the Vitess keyspace hosting Pull Request data. The backfill Vitess command encountered errors and increased VReplication lag, and the workflow was canceled at 19:17 UTC. The cancellation executed a misunderstood Vitess codepath that dropped the backing table to the target keyspace, leaving a non-existent reference that resulted in errors creating Pull Requests. The mitigation was executing a command to drop the vschema reference to the dropped table, allowing Pull Request creation to resume.<br /><br />We are adding stronger pre-flight validation to our tooling to prevent similar issues and expanding lower-environment support to provide better test coverage end-to-end before promoting them to production. We're also fixing our backfill migration tooling to protect from this specific codepath.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The security updates have been applied across the Liquid Web fleet.
Resolved
This issue has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Normal service is recovering.
Resolved
This incident has been resolved.
Resolved
Packages have successfully resynced and package syncing is operating as expected
Resolved
On July 21, 2026, between 07:41 UTC and 11:57 UTC, the SSH Authentication service was degraded and some SSH connections failed to authenticate. On average, 12.2% of SSH authentication requests failed, peaking at 15.7%. Both user RSA keys and deploy keys were impacted. This was due to a change in how our SSH service handled one public-key authentication method that caused the affected authentication attempts to be rejected as invalid. <br /><br />We mitigated the incident by reverting the change, after which SSH authentication returned to normal. <br /><br />We are working to expand our automated test coverage for our SSH public-key authentication flows to catch more edge cases and to improve observability and alerting on SSH authentication failures, to reduce our time to detection and mitigation of issues like this one in the future.
Resolved
This incident has been resolved.
Resolved
Our team has successfully applied the appropriate mitigation to all impacted nodes, and the fix has been deployed to prevent future occurrences.
Resolved
We can confirm that the issue was mitigated at 14:21 UTC on 29 July 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700001LBrwDCAT, or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.
Resolved
Between 19:12 and 19:18 UTC on July 23, 2026, telemetry forwarded through Drains was not delivered. Traces and events forwarded via Drains during this window were dropped and are unrecoverable. Logs forwarded via Drains during this window were also not delivered, but remain accessible in the Logs UI dashboard, where they can also be exported. We have deployed a fix and are adding additional monitoring to detect and prevent this failure mode from happening in the future. We know how much you rely on this data, and we sincerely apologize for the disruption.
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
Issue has been resolved
Resolved
This incident has been resolved.
Resolved
Between 17:29 and 17:34 CEST on 22nd of July, scenarios on the EU1 zone failed at initialization with a "Failed to verify account" error, affecting connections across all apps. Approximately 200 scenarios were automatically deactivated as a result and have since been re-enabled. We are actively working to prevent recurrence.
Resolved
GPT-OSS-120B was having partial service disruption between 18:20 UTC to 18:45 UTC. This is resolved now.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The fix was verified and the breakage is now resolved.
Resolved