- Service Status
- /
- Avery

Is Avery Down?
- Avery's status page
- Degraded · major outage of DEV-Avery Shopping Cart and STG-Avery Shopping Cart
- FlareWarden checks
- Website reachable · 8 of 8 regions · 130 ms
Right now
The verdict is the worse of these two. How we decide
Avery's status page
status.avery.com · read · checked every 3 minutes
| Component | Status |
|---|---|
| DEV-Avery Shopping Cart | Down |
| STG-Avery Shopping Cart | Down |
| Avery Blog | Operational |
| Avery Home Page | Operational |
| Avery Shopping Cart | Operational |
| Design & Print Online - Backend | Operational |
| Design & Print Online - Frontend | Operational |
| DEV-Design & Print Online - Backend | Operational |
| STG-Avery Home Page | Operational |
| STG-Design & Print Online - Backend | Operational |
FlareWarden checks
avery.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 130 ms
- Checked
By region
- Amsterdam reachable, 80 ms
- Dallas reachable, 128 ms
- Frankfurt reachable, 148 ms
- Newark reachable, 182 ms
- Paris reachable, 89 ms
- Stockholm reachable, 100 ms
- São Paulo reachable, 184 ms
- Toronto reachable, 129 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Amsterdam | 52 ms | 6 ms | 6 ms | 71 ms |
| Dallas | 114 ms | 1 ms | 3 ms | 124 ms |
| Frankfurt | 133 ms | 2 ms | 4 ms | 144 ms |
| Newark | 160 ms | 3 ms | 5 ms | 177 ms |
| Paris | 72 ms | 2 ms | 4 ms | 84 ms |
| Stockholm | 86 ms | 1 ms | 5 ms | 97 ms |
| São Paulo | 168 ms | 1 ms | 6 ms | 181 ms |
| Toronto | 81 ms | 8 ms | 12 ms | 113 ms |
History
Incidents Avery reported
Since Oct 27, 10 days · from status.avery.com
- Incidents
- 2
- Major or critical
- 0
- Median to resolve
- 2h
- Ongoing
Unrated ·
- lasted 2h
Unrated ·
Avery website availability
Measured by FlareWarden · avery.com
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 251ms
Last 30 days
55-day clean streakMeasured by FlareWarden's own checks of avery.com from multiple regions every 6 hours. Avery's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 55 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
What Avery does
Avery makes printable labels, cards, dividers and name badges, and sells them alongside online design tools that place artwork onto an Avery template before printing. Small businesses use it for shipping and product labels, offices for badges and filing. The site handles both the design step and ordering, so an outage can interrupt a print run or a purchase.
What an outage looks like
avery.com fails to load or returns a server error, and the online design tool will not open a template or save changes. A project that was already open may refuse to export or print, and ordering stops at the cart or at checkout. The page on screen can look normal while every action that needs Avery's servers quietly fails.
What to do about it
Read status.avery.com. It is Avery's own status page, but it reports avery.com as a single uptime figure with no per-component breakdown, so it will not tell you whether the problem is the design tool, the store or the whole site. Establish that yourself by trying one action from each: load a template, then load a product page. Save or export anything open before retrying.
Is it down for everyone, or just you?
If this page says Avery 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.
Related services
Avery outage FAQ
Avery's status page shows no updates. Does that mean nothing is wrong?
Will I lose a label design I was working on?
Can I still print labels while Avery is down?
Is Avery down for everyone or just me?
Does an Avery outage affect an order I already placed?
How we measure this
- We request Avery's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. Our checks only change their 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 Avery publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Avery itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.
Get alerted when Avery goes down
We check Avery every 6 hours, and again when you open this page if that was more than 30 minutes ago. 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

