SPS Commerce status history

Current state: operational — “All Systems Operational” per https://status.spscommerce.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

1incidents, last 30 days

4incidents, last 90 days

6incidents on record

Incidents per week, last 12 weeks:

Get SPS Commerce alerts in your Slack — free template RSS for SPS Commerce

How long do SPS Commerce incidents last?

66 minmedian incident duration6 measured

89 min90th percentile1 in 10 ran longer

2.5 hmedian, major/critical only2 incidents

From 6 incidents with a vendor-posted start and resolve time. Longest on record: Document Processing Delay — 4.1 h (2026-07-06 20:25 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (6)

Started	Incident	Status	Impact	Duration
2026-08-18 16:08 UTC	AS2 Communications	resolved	none	6 min
2026-07-25 12:00 UTC	Document Processing Delay	resolved	minor	8 min
2026-07-06 20:25 UTC	Document Processing Delay	resolved	critical	4 h 08 min
2026-07-06 18:44 UTC	Document Processing Delay for Web customers	resolved	major	50 min
2026-06-18 08:02 UTC	Document Processing Delay	resolved	minor	1 h 22 min
2026-04-10 20:37 UTC	NetSuite Integrations - Investigating	resolved	minor	1 h 29 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch SPS Commerce with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "sps-commerce"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}