Five of the 84 services StatusBird monitors recorded their most recent major or critical incident inside the last 30 days: Shippo, BigCommerce, Deliverr, Shopify, and Zapier. One of them, Shippo, accounts for 1,344 minutes of downtime over the trailing 90 days, nearly two and a half times the 546 minutes logged by the other four combined.
All figures below come from StatusBird's independent 2-minute monitoring over the 90 days ending September 18, 2026. The monthly counts come from the outage index, and the check and confirmation rules are written up in the methodology.
Which services had incidents in the last 30 days?
| Service | Category | Most recent incident | Incidents (90 days) | Downtime (90 days) | Avg incident | 90-day uptime |
|---|---|---|---|---|---|---|
| Shippo | Shipping | Sep 17, 2026 | 10 | 1,344 min | 134 min | 98.96% (C) |
| BigCommerce | E-commerce | Sep 16, 2026 | 2 | 180 min | 90 min | 99.86% (B+) |
| Zapier | Automation | Sep 9, 2026 | 2 | 118 min | 59 min | 99.91% (A) |
| Deliverr | Shipping | Aug 27, 2026 | 2 | 124 min | 62 min | 99.9% (A) |
| Shopify | E-commerce | Aug 27, 2026 | 2 | 124 min | 62 min | 99.9% (A) |
Three categories cover all five services: shipping, e-commerce, and automation. Nothing in payments, marketing, ads, reviews, loyalty, support, tax, returns, marketplaces, fulfillment, analytics, or infrastructure recorded a major or critical incident in the last 30 days. Across the full 90-day window, 15 of the 84 monitored services logged at least one major or critical incident, which means 69 stayed clean the whole quarter.
Shopify and Deliverr moved together
Shopify and Deliverr have identical incident counts, identical 90-day downtime totals of 124 minutes, identical 62-minute averages, and the same most recent incident date of August 27, 2026. The monitoring data records what went down and when, not why, so this does not prove a shared root cause. It does mean a store running Shopify with Deliverr fulfillment saw both sides of its order pipeline degrade on the same day, which is the practical thing to plan for.
Why does one vendor dominate the downtime total?
Shippo's 10 incidents in 90 days are five times the count of any other service on the recent list, and its 134-minute average incident is longer than every other recent offender except BigCommerce's 90 minutes. That combination, frequent and not short, is what drops it to 98.96% and a C grade while Shopify and Deliverr sit at 99.9% with an A.
First quotable conclusion: a grade A does not mean zero incidents. Shopify, Deliverr, Vercel, and Zapier all carry A grades and all had two major or critical incidents in 90 days. The grade reflects total minutes lost, not whether your Tuesday afternoon will be interrupted. If your runbook assumes A-grade vendors never fail, it has never been tested.
Second conclusion: your downtime exposure is usually concentrated in one or two vendors, not spread evenly. For a store running Shopify with Shippo labels, Shippo contributed 1,344 of the 1,468 combined minutes those two services lost over the quarter. Auditing every integration equally wastes time. Rank your dependencies by their own outage history and build a fallback for the top one first.
Does the absence of payments incidents mean payments are safe?
No. Plaid holds the lowest 90-day uptime of any monitored service at 98.8%, grade C, with 1,548 minutes of downtime across just four incidents. Its last incident was August 3, 2026, so it does not appear in the 30-day list at all.
That contrast is the third conclusion: there are two distinct failure shapes, and they need different responses. Shippo's pattern is high frequency with a 134-minute average. Plaid's pattern is low frequency with a 387-minute average, the longest average incident in the dataset. A vendor that fails often at two hours a time is a staffing and process problem: someone has to notice and fall back quickly, repeatedly. A vendor that fails rarely but for six and a half hours is a business continuity problem: you need a route that does not involve that vendor at all for the rest of the day.
Elsewhere in payments, Stripe, PayPal, Square, Adyen, Afterpay, Klarna, Braintree, and Authorize.net all recorded 100% uptime with zero major or critical incidents across the 90 days. Affirm logged one 22-minute incident on August 10, 2026, and Sezzle one 62-minute incident on July 5, 2026.
How does this month compare with the outage index history?
| Month | Major/critical incidents | Combined downtime | Services affected | Most affected |
|---|---|---|---|---|
| August 2026 | 16 | 40.4 hours | 9 | Plaid |
| July 2026 | 14 | 22.1 hours | 8 | Shippo |
| June 2026 | 8 | 37.0 hours | 8 | Squarespace |
| May 2026 | 4 | 21.9 hours | 4 | Square |
| April 2026 | 20 | 122.1 hours | 11 | AfterShip |
| March 2026 | 2 | 8.3 hours | 2 | Authorize.net |
Incident counts have climbed every month since May: 4, then 8, then 14, then 16. Combined downtime has not followed the same line. August's 16 incidents produced 40.4 hours, while April's 20 incidents produced 122.1 hours. Divide it out and April averaged just over six hours per incident against about two and a half hours in August and roughly an hour and a half in July.
The readable trend is more interruptions of shorter length. For store operations that shifts the burden from "survive a long outage" toward "detect and switch quickly, several times a month." August also touched nine distinct services, more than any month since April's eleven.
What should you change this week?
- Pick your single highest-risk vendor by history, not by feeling. Open the outage index and the reliability page for each integration you cannot ship or sell without. If a label provider like Shippo is on your list, that is the one to build around first.
- Configure a second label path before you need it. Keep credentials for an alternate provider saved and tested, and confirm which carrier accounts are attached to it, so switching is a settings change rather than a signup.
- Move batch label printing earlier in the day. With a 134-minute average incident on Shippo, a mid-afternoon failure can push a same-day cutoff. An earlier batch leaves recovery room inside the same shift.
- Audit your Zapier task history after every incident. Zapier lost 118 minutes across two incidents in 90 days, and the automations that quietly did not run during those windows include order tags, inventory syncs, and helpdesk ticket creation. Re-run failed tasks rather than assuming the queue drained itself.
- Put the storefront and the top three dependencies on the same alert channel. If Shopify and a fulfillment provider degrade the same day, as happened on August 27, 2026, you want both alerts in one place so you can see the overlap instead of triaging two unrelated-looking tickets.
- Check the live status pages before you open a support ticket. The current state for Shippo, BigCommerce, Shopify, Deliverr, and Zapier is all monitored independently on the same 2-minute cadence.
If you would rather find out from a notification than from a customer email, StatusBird checks these services every two minutes and can alert you by SMS, email, Slack, Teams, or Discord. You can set up monitoring for the services your store depends on and pick the channels that fit how you work.