Cargo Outage History
Cargo degraded · 1 active incident View live status →Pingoru has recorded 5 incidents for Cargo: 5 in the last 12 months and 4 in the last 90 days.
Incidents, newest first
Minor October 27, 2026 Intermittent API errors 2h 26m Current status by service (app.getcargo.io)
Started Oct 27, 2026, 09:21 PM UTC· resolved Oct 27, 2026, 11:47 PM UTC
- investigating Oct 27, 2026, 09:21 PM UTC
The API is intermittently returning 503s. A request can fail and then succeed on retry. Runs that get through still complete. We're investigating.
- investigating Oct 27, 2026, 09:46 PM UTC
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.
- resolved Oct 27, 2026, 11:47 PM UTC
The 503s have stopped. A request that failed earlier can be retried. Runs that get through continue to complete.
Minor October 27, 2026 Workflow runs and data syncs delayed – Current status by service (app.getcargo.io)
Started Oct 27, 2026, 06:32 PM UTC· resolved Oct 27, 2026, 06:32 PM UTC
- resolved Oct 27, 2026, 06:32 PM UTC
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.
Major August 6, 2026 Intermittent API errors and timeouts 2h 30m Current status by service (app.getcargo.io)
Started Aug 06, 2026, 01:00 PM UTC· resolved Aug 06, 2026, 03:30 PM UTC
- investigating Aug 06, 2026, 01:00 PM UTC
The API is returning intermittent errors and timeouts as instances restart. Requests may fail and then succeed on retry. We're investigating.
- resolved Aug 06, 2026, 03:30 PM UTC
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.
Minor August 3, 2026 Sales Navigator searches failing with daily limit errors 21h 30m Current status by service (app.getcargo.io)
Started Aug 03, 2026, 03:30 PM UTC· resolved Aug 04, 2026, 01:00 PM UTC
- investigating Aug 03, 2026, 03:30 PM UTC
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.
- resolved Aug 04, 2026, 01:00 PM UTC
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.