- Level
- confirmed
- Worst impact
- Major outage
- Components
- Lasership
- Down Index
- 42of 100
What to do
Check whether you use Shippo Lasership. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2h 50m it lasted.
Anything that failed between 2026-08-13 13:47 UTC and 2026-08-13 16:37 UTC may need a replay.Subscribe to Shippo's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=shippo works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Shippo 3
- investigating
We have detected an elevated error rate from lasership Transaction API. Our team has contacted the carrier and we are monitoring the situation. During this time, Label generation will be unavailable please retry once the carrier's API is restored.
provider
- monitoring
Carrier confirmed its unplanned outage on their end and their IT team working on the fix , we started seeing the recovery so keeping this in a monitoring state
provider
- resolved
Issue has been fully resolved and service back to operational.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-9c1ad89c0f
Is Shippo still down?
No, this incident was resolved 2026-08-13 16:37 UTC. For Shippo's live state, see https://down.guide/shippo.
How long did it last?
2h 50m, from 2026-08-13 13:47 UTC to 2026-08-13 16:37 UTC, by the times Shippo posted.
What was affected?
Shippo named Lasership.
What caused it?
Shippo hasn't published a root cause. If it does, it shows here.
Where does this come from?
Shippo's official status page, https://status.goshippo.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.