Shiprocket Outage History

12 incidents recorded over the last 365 days, 12 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Shiprocket status81.18% uptime history

Every Recorded Shiprocket Incident

Shiprocket incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 4, 2026ShipRocket Serviceability is down765h 54mResolved
Sep 14, 2026ShipRocket M-Site, ShipRocket Support Api, and 2 other services are down386h 25mResolved
Sep 12, 2026ShipRocket Engage API is down1296h 55mResolved
Sep 11, 2026ShipRocket Engage Web is down1303h 9mResolved
Sep 9, 2026ShipRocket Engage API is down1366h 6mResolved
Sep 7, 2026ShipRocket Engage API is down1413h 39mResolved
Aug 27, 2026ShipRocket Engage API is down1563h 19mResolved
Aug 26, 2026ShipRocket Engage API is down1588h 3mResolved
Aug 8, 2026Shiprocket Tracking is down2027h 18mResolved
Jul 25, 2026ShipRocket Serviceability is down1622h 54mResolved
Jun 11, 2026Channel is down1955h 11mResolved
Jun 9, 2026ShipRocket UI is down2009h 47mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Shiprocket incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Shiprocket Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Shiprocket acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Shiprocket outage in this window ran 84d 11h, against a mean recovery of 60d 1h. If you depend on Shiprocket in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.