Skip to main content
Endicia logo

Is Endicia Down?

No — Endicia is up

Reachable from all 8 checked regions

Average response time: 771ms

Last checked · checks run every 6 hours

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

Endicia uptime

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

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

30-day history

30-day clean streak
Sep 13: 100.00% uptime, 32 checks
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 37 checks
Sep 23: 100.00% uptime, 31 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, 29 checks
Oct 1: 100.00% uptime, 32 checks
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, 31 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: no data
Sep 13 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.

ams
684ms
DNS 67ms TCP 2ms TLS 13ms TTFB 674ms
arn
849ms
DNS 26ms TCP 1ms TLS 168ms TTFB 846ms
cdg
713ms
DNS 151ms TCP 1ms TLS 58ms TTFB 710ms
ord
128ms
DNS 61ms TCP 2ms TLS 7ms TTFB 124ms
sin
1671ms
DNS 177ms TCP 219ms TLS 441ms TTFB 1278ms
sjc
276ms
DNS 123ms TCP 2ms TLS 10ms TTFB 272ms
syd
1610ms
DNS 761ms TCP 1ms TLS 201ms TTFB 1584ms
yyz
238ms
DNS 101ms TCP 12ms TLS 28ms TTFB 211ms

What Endicia does

Endicia sells USPS postage online and prints shipping labels for it, through a browser app, downloadable Windows and Mac software, the DAZzle desktop application and an API that e-commerce platforms call to buy labels programmatically. Online sellers and warehouses use it to buy postage, print labels and file refunds and SCAN forms without visiting a post office.

What an outage looks like

Labels fail to generate or print, so packages are packed and ready with nothing to put on them. Buying postage fails or the balance does not update. Integrations that call the Endicia API for labels return errors, which surfaces inside the seller's own store or shipping software rather than on an Endicia screen. Refund requests and SCAN form generation stop separately from label printing.

What to do about it

Read status.endicia.com and match your surface to the row. Endicia reports Endicia Online, Endicia Downloadable, DAZzle, Endicia for Mac, the Endicia API Label Server and Reporting Tools as separate components, so a colleague printing from a different client proves nothing about yours. If the API is the affected row and the desktop clients are not, printing by hand is a workable fallback for urgent packages.

Is it down for everyone, or just you?

If this page says Endicia 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

Endicia outage FAQ

The web app is down but my desktop software works. Is Endicia down?
Partly, and Endicia's own status page is built for exactly this question. Endicia Online, Endicia Downloadable, DAZzle and Endicia for Mac are four separate components, so the browser tool can fail while a Windows or Mac client keeps printing, or the reverse. Check the row that matches how you print rather than the headline, because a single all-clear at the top is not what governs your workflow.
My store's shipping integration stopped creating labels. Is that Endicia?
It may be, and the component to check is the Endicia API, which Endicia lists as the Label Server. Platforms and shipping software buy labels through that API, so when it fails the error appears inside your own store or shipping tool rather than anywhere on Endicia's site. That makes it easy to mistake for a bug in your platform. Check the API row before opening a ticket with them.
Will I be charged for postage on a label that failed to print?
Endicia does not publish a guarantee covering labels interrupted mid-purchase, so check rather than assume. Reporting Tools, which Endicia lists as covering history, refunds and SCAN forms, is where a printed-but-unused label is reconciled, and it is a separate component that can be unavailable while printing works. Avoid buying the same label repeatedly during an incident, because duplicates are harder to refund than a single stuck one.
Can I still ship while Endicia is down?
Yes, through routes that do not depend on it. Labels already printed are valid physical postage and can be handed over normally. For new packages, buying postage at a USPS retail counter does not involve Endicia at all, and any second postage provider you hold an account with is unaffected. What you lose is your Endicia rates and record-keeping, not the ability to ship.
Is Endicia down for everyone or just me?
Separate the service from your own client before deciding. The desktop applications need a working connection to Endicia, so a local firewall, a VPN or a proxy that blocks them produces symptoms identical to an outage on one machine while colleagues print normally. Try the browser app from a different network. The regional measurements on this page show what our probes saw from several locations at once.

How we measure this

  • We request Endicia'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 Endicia 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 Endicia 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