Incidents and maintenance reported on status page for Cargo https://status.getcargo.ai/ https://d1lppblt9t2x15.cloudfront.net/logos/9c7ff61aa740062d7faea6d4d02a7012.png https://status.getcargo.ai/ en https://status.getcargo.ai/incident/1109040 Fri, 30 Oct 2026 19:23:21 -0000 https://status.getcargo.ai/incident/1109040#22eed348ce93b6b594904c198b05151672b56222cb1f557ebe7caee9bb6c1ec8 Incident Sign-in, the app and the API are fully restored and have been stable since 19:18 UTC. We are now gradually resuming workflow and AI agent processing. Queued runs will catch up over the next while, so you may see some delay before they complete. We'll resolve this incident once background processing is fully back to normal. https://status.getcargo.ai/incident/1109040 Fri, 30 Oct 2026 19:13:00 -0000 https://status.getcargo.ai/incident/1109040#91fc20585ee71496ee790ad417f5e73369e068536972ccf1b87701f8534ba872 Incident A fix has been applied and database performance is back to normal. Sign-in and the app should be working again. Workflow runs and AI agent runs are temporarily paused while we safely restore background processing; queued work will resume shortly and nothing has been lost. Some AI agent runs that started during the incident may have failed and can be re-run. We're monitoring and will post another update once background processing is fully restored. https://status.getcargo.ai/incident/1109040 Fri, 30 Oct 2026 19:00:15 -0000 https://status.getcargo.ai/incident/1109040#da1e61871a5215b412e5165953f0e1f21e062d0edb8936e94333fdaa735f30a5 Incident Since 18:05 UTC, users have been unable to sign in to Cargo, and parts of the app and API have been slow or unresponsive. We have identified the cause: a sudden surge in AI agent activity triggered an inefficient database query, which overloaded our primary database. Sign-in depends on that database, so logins timed out. Our authentication provider is not affected. We are applying a database fix now and have a permanent code fix ready to deploy. We'll post another update once sign-in is restored. https://status.getcargo.ai/incident/1106057 Tue, 27 Oct 2026 23:47:28 -0000 https://status.getcargo.ai/incident/1106057#1fc31e68285bacb07c9bfe24a1da8e1bbb8d692547aef42256aa1ce78b268f66 Incident The 503s have stopped. A request that failed earlier can be retried. Runs that get through continue to complete. https://status.getcargo.ai/incident/1106057 Tue, 27 Oct 2026 21:46:52 -0000 https://status.getcargo.ai/incident/1106057#1f1047d021421c606cff2a0fa48dbd6ce6bf08d9bee60c3d944a831d0bf9fa8f Incident A stalled API process was being restarted, and those restarts are what returned the 503. We've stopped restarting a stalled process. A request that hits one can still fail, and then succeed on retry. Runs that get through still complete. We're still looking for what causes the stall. https://status.getcargo.ai/incident/1106057 Tue, 27 Oct 2026 21:21:06 -0000 https://status.getcargo.ai/incident/1106057#1f79172f084b48dd1d92482eca4fa1c7536292ee748b84cfc0a157dc01d247e0 Incident The API is intermittently returning 503s. A request can fail and then succeed on retry. Runs that get through still complete. We're investigating. https://status.getcargo.ai/incident/1106045 Tue, 27 Oct 2026 18:32:00 -0000 https://status.getcargo.ai/incident/1106045#106d84ad80f0f828e13aa61b96773b5dbe711f2e7c26d6e86673e464898ffddb Incident Resolved. DNS lookups from production were slow between 18:10 and 18:32 UTC, and requests that needed those lookups timed out. Workflow runs and batches were delayed, and some failed to save. Data syncs to connected systems failed during the same window. Most of those writes retried successfully once DNS recovered. A smaller set that used up its retries may still be missing; we're checking those. No action needed on your side unless a run or sync from that window looks incomplete. Sorry for the interruption. https://status.getcargo.ai/incident/998872 Thu, 06 Aug 2026 15:30:00 -0000 https://status.getcargo.ai/incident/998872#cc572962b9a8ead0f5fdddd7090ff083ec648949b995b34d112858c2b682537a Incident Resolved. Errors stopped at 15:30 UTC. A large export could consume enough memory to take an instance down with it, which is what drove the restarts. Impact was intermittent rather than total: requests that landed on a healthy instance went through, and no data was lost. Instances settled fully over the evening. We're changing exports to stream to storage rather than build the whole file in memory, which removes this failure mode. Sorry for the errors you hit. https://status.getcargo.ai/incident/998872 Thu, 06 Aug 2026 13:00:00 -0000 https://status.getcargo.ai/incident/998872#e4acd7021af83bb0fc631807b07597ec4e206278b7430b72202391fbdb3ba5b0 Incident The API is returning intermittent errors and timeouts as instances restart. Requests may fail and then succeed on retry. We're investigating. https://status.getcargo.ai/incident/998871 Tue, 04 Aug 2026 13:00:00 -0000 https://status.getcargo.ai/incident/998871#f187b401314e2880f622ec8f9201a798c06c0b9a22cb9cc2d1072590922f81be Incident Resolved. Throughput returned to normal at 13:00 UTC. Sales Navigator is now metered per workspace, so one job can no longer drain the allowance for everyone. The default is 1,000 requests per 24 hours, counted separately for people search, company search and company enrichment. If your volumes need more than that, tell us the number and we'll raise it. Worth saying plainly: LinkedIn keeps tightening what Sales Navigator allows, and that trend isn't ours to reverse. If roster pulls are critical to you, it's worth having a second source behind them. Sorry for the runs you lost during that window. https://status.getcargo.ai/incident/998871 Mon, 03 Aug 2026 15:30:00 -0000 https://status.getcargo.ai/incident/998871#ca12078aa5eda9535ad9ab0d0077e7edf743780bb271a0804ca9fce4716d3dea Incident Sales Navigator people search, company search and company enrichment are returning daily-limit errors. Runs using those steps are failing or coming back empty. LinkedIn has been steadily tightening how much any Sales Navigator account can pull in a day, and a single unusually large job has consumed most of the remaining shared allowance.