Skip to main content
Shippo logo

Is Shippo Down?

No — Shippo is up

Reachable from all 8 checked regions

Average response time: 237ms

Last checked · checks run every 6 hours

Official status page: https://status.goshippo.com

Elevated error rate on Canada post Shipment API

major investigating

Hi Team, we are currently observing an elevated error rate on Canada Post's Shipment API. Rate quotes will be unavailable, and label generation may fail as a downstream impact. We have reached out to Canada Post and are actively monitoring the situation. We will provide a further update as soon as we receive one from the carrier..

Components the vendor reports as affected: Canada Post Partial Outage

A component listed here does not necessarily mean a full outage — large providers routinely report maintenance on individual locations. It only affects the verdict above when the vendor marks it major or critical and our own checks also saw Shippo fail from enough regions to rule out probe noise.

Shippo uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
312ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 22 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

22-day clean streak
Sep 14: no data
Sep 15: no data
Sep 16: no data
Sep 17: no data
Sep 18: no data
Sep 19: no data
Sep 20: no data
Sep 21: no data
Sep 22: 100.00% uptime, 16 checks
Sep 23: 100.00% uptime, 32 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 32 checks
Sep 30: 100.00% uptime, 32 checks
Oct 1: 100.00% uptime, 32 checks, 1 incident
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

cdg
228ms
DNS 29ms TCP 2ms TLS 11ms TTFB 220ms
dfw
274ms
DNS 28ms TCP 2ms TLS 9ms TTFB 270ms
ewr
82ms
DNS 14ms TCP 2ms TLS 14ms TTFB 79ms
fra
226ms
DNS 45ms TCP 2ms TLS 14ms TTFB 223ms
gru
386ms
DNS 128ms TCP 2ms TLS 13ms TTFB 378ms
iad
155ms
DNS 21ms TCP 14ms TLS 23ms TTFB 138ms
jnb
407ms
DNS 13ms TCP 0ms TLS 9ms TTFB 401ms
lax
140ms
DNS 14ms TCP 3ms TLS 10ms TTFB 133ms

What Shippo does

Shippo is multi-carrier shipping software for e-commerce businesses. Sellers use its web dashboard or its API to compare carrier rates, buy and print labels, verify addresses and track packages, and it connects to e-commerce platforms so orders flow in on their own. For many online stores it is the step between an order arriving and a parcel leaving, so an outage stops fulfilment rather than sales.

What an outage looks like

Label purchases fail or hang in the Shippo dashboard, rate quotes come back empty, and API calls from a store or warehouse system return errors. Often only one carrier is affected: Shippo lists each carrier's API as its own row, so USPS labels can fail while UPS and FedEx print normally. Tracking updates can also stop for one carrier while the others keep moving.

What to do about it

Open status.goshippo.com and read two places: the Shippo REST API, Platform API and Web Dashboard rows, and the Carrier API group, which has a row per carrier. If only your carrier is flagged, move the affected orders to another carrier for the day. Do not re-buy a label that appeared to fail until you have checked the label history, so the same shipment is not paid for twice.

Is it down for everyone, or just you?

If this page says Shippo is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Shippo outage FAQ

Is it Shippo or the carrier that is down?
Check the Carrier API group on status.goshippo.com. Shippo lists more than fifty carriers separately, from USPS, UPS and FedEx to Royal Mail, DHL Express and Canada Post, so a problem at one carrier shows on its own row while the Shippo API and dashboard stay green. If the core rows are healthy and only one carrier is flagged, the fix and the timeline belong to that carrier.
My label purchase failed. Was I charged?
Check before buying again. Open the label history in the Shippo dashboard once it loads and look for the shipment. If a label exists, the purchase went through even though the screen showed an error, and printing it is all you need to do. If none exists, buy it again or use another carrier. Buying twice on a guess is how duplicate labels happen.
Why does my store show shipping errors when the Shippo website works?
Because the website and the API are reported separately. Shippo lists its REST API and Platform API apart from its Web Dashboard, and store platforms that print labels through Shippo use the API. When the API is degraded, the error appears inside your store admin or shipping app and reads like a bug there. Check the API rows before reinstalling or reconnecting anything.
Is Shippo down for everyone or just me?
Compare the status page with this page's measurements from several regions. If both show Shippo healthy, the likely causes are local: an expired carrier account connection, a stale browser session, or a store integration whose credentials changed. Failures seen from several regions at once point to Shippo itself.

How we measure this

  • We request Shippo's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Shippo publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Shippo goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required