Cargo experienced a major incident on August 6, 2026 affecting Current status by service (app.getcargo.io), lasting 2h 30m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- 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.