QR Code Downtime: Causes, Fixes and How to Prevent It

QR code downtime is any period when someone scans your code and does not reach the right page. The code itself rarely fails. The cause is almost always one of four things further down the chain: the code’s redirect, the destination website, the scanner’s network, or the physical print. If you use dynamic codes that you control, you can find the failing layer in minutes, repoint the code without reprinting, and set things up so a billing problem never switches your codes off. We built QRlytics around that last point: codes created during an active subscription keep working, whatever happens to billing.
This guide is for marketers, business owners, retailers, hospitality teams and event organisers who have QR codes on paper, packaging, signage or screens. It explains what downtime looks like, how to diagnose it, what to do while it is happening and how to make it much less likely.
TL;DR
- QR code downtime means scans fail to reach the right page. It can happen at the code, the redirect, the destination site, the network or the print.
- Test in a fixed order: scan the code, open the destination URL directly, then try another phone and another network. That separates a broken code from a broken page.
- When a code fails, change the destination of a dynamic code instead of reprinting. A static code cannot be edited once printed.
- Free generators that switch codes off after a cancelled plan or failed payment are a downtime risk you can avoid. QRlytics keeps codes created during an active subscription working permanently.
- Plan fallbacks for events and shops: a short typed URL, offline check-in and a code printed large, with strong contrast, away from glare and moisture.
Table of Contents
- What QR code downtime actually means
- The five causes of QR code downtime
- How to tell where the fault is
- What to do when a QR code stops working
- How to prevent QR code downtime before you print
- Retail, hospitality and event scenarios
- Our perspective on QR code downtime
- Make your next print run reliable
- FAQ
- Sources
What QR code downtime actually means
A scan is a short journey, and any step can break it:
- The phone reads the code. The camera must find the square pattern and decode it. Poor print, glare, low light or a damaged surface stops this step.
- The code points to a URL. A static code holds the final web address inside the pattern. A dynamic code holds a short address on a redirect service, which then forwards the visitor to your destination. A redirect is simply a signpost: the scan goes to the signpost first, then on to the page.
- The redirect service responds. If it is switched off, slow or unreachable, the scan fails even though your own website is fine.
- Your destination loads. An expired page, a deleted landing page, a certificate error or a crashed server all look like “the QR code is broken” to the person holding the phone.
- The visitor’s connection works. Weak mobile signal or overloaded venue Wi-Fi stops the page loading however healthy everything else is.
That is why “is the QR code down?” is the wrong first question. The better question is “which step failed?” Our guide to what QR code uptime means and how to check it goes deeper on the redirect step.
Why it matters more for print
A website outage is fixed and forgotten. A broken QR code on a printed brochure, shelf talker, product box or poster stays broken in the real world for as long as that material is in circulation. Every scan that fails is a customer who walked away, and you often never see it, because nobody reports a code that quietly does nothing.

Real outages in 2026 show how widely QR-dependent services can be hit. On 22 August 2026 a system fault in Santiago, Chile, affected QR payment-code generation and validation on buses, the Metro and Tren Nos, and riders were told to use the bip! card instead. In payments, a third-party partner problem on 12 August 2026 caused a 53-minute disruption to QR-code services, which the provider handled by rerouting traffic to an alternate solution until the partner recovered. These are payment systems, not marketing codes, but the lesson transfers: the QR pattern is the easy part, and the chain behind it is where outages happen. The useful response in both cases was a ready alternative route.
The five causes of QR code downtime
| Layer | What goes wrong | What the scanner sees |
|---|---|---|
| Print and physical | Low contrast, small size, glare, smudging, moisture, creases, a logo covering too much of the pattern | Camera will not recognise the code, or reads it only sometimes |
| Code type | A static code points to a page that no longer exists | The code scans, then shows an error page |
| Redirect service | A generator deactivates codes after a plan lapses, a payment fails or its servers are down | The code scans, then shows a blocked, expired or upgrade page, or nothing loads |
| Destination | The landing page was moved, deleted, password-protected or is overloaded | A 404 error, timeout or certificate warning |
| Network | Weak signal, crowded venue Wi-Fi, no roaming data | A spinning page, then a timeout |
The third row is the one many businesses never think about when they print. Some free and low-cost generators tie a code’s life to your account. If the subscription ends or a card is declined, the code is deactivated and every printed copy goes with it. It is the most avoidable cause of downtime on this list, because it comes from the terms you choose, not from bad luck.
How to tell where the fault is
Work through the layers in this order. It takes a few minutes and needs only two phones.
Step 1: Scan the code with two phones
Use one iPhone and one Android phone if you can, with the default camera app. If neither phone recognises the code, the problem is physical: print quality, size, lighting or damage. If one phone reads it and the other does not, look at contrast and size first. Our guide on why codes fail in low light and how to fix it covers the usual causes.

Step 2: Look at where the scan lands
If the phone shows a link preview, read it before you tap. A short redirect address is expected for dynamic codes. If the preview shows an unfamiliar domain, a generator’s upgrade page or a “code deactivated” message, the redirect layer has failed.
Step 3: Open the destination directly
Type or paste the final destination URL into a browser. If the page fails here, the code and redirect are not the issue: your website is. Check that the page exists, that your hosting is up and that the security certificate has not expired.
Step 4: Switch networks
Turn off Wi-Fi and try on mobile data, then try the reverse. If the page loads on one and not the other, the cause is the network, which is common in basements, event halls and shopping centres.
Step 5: Check your scan analytics
If your platform records scans, compare the last few hours with a normal day. A sudden drop to zero at a time when people were scanning points to a code or redirect fault. A normal count with a complaint about the page points to the destination. This is one reason analytics is part of reliability and not a nice extra: it is the only way to notice failure in the field. Our guide to tracking scans through to conversions shows which metrics to watch.
What to do when a QR code stops working
The order of actions matters. Start with the one that stops the most lost scans.
- Confirm the layer using the steps above. Do not redesign or reprint until you know which layer failed.
- If the destination is broken, repoint the code. With a dynamic code you change the URL behind it to a working page, such as a temporary landing page, a simple contact form or the correct campaign page. Nothing printed has to change. With a static code this option does not exist, which is why static codes suit only permanent, stable addresses.
- If the redirect service is the problem, move the traffic. If your generator has deactivated the code or is down, you cannot fix it from outside. Your only route is to replace the printed code, which is the costly outcome permanent codes are designed to avoid.
- Add a visible fallback. A short typed web address or a phone number next to the code lets people reach you while you fix the cause. Many printed materials that carry only the code have no way for a customer to recover.
- Tell the people who handle the code. Brief store staff, front-of-house teams or event crew so they can answer a customer who says the code does not work.
- Record the incident. Note when it started, which layer failed, how many scans were lost and what changed. This is the evidence you need to choose a more reliable setup next time.
If the failure is an overload
A code printed on a national mailing or shown on a big screen can send thousands of people to one page within minutes. If your landing page slows down, the code looks broken. Lightweight pages that load fast on mobile data handle spikes better than image-heavy ones. Our guide to redirect stability for marketers explains how redirect speed and consistency affect the visitor experience.
How to prevent QR code downtime before you print
Most downtime is decided before the code reaches the printer. Use this checklist.
Choose the code type by the lifetime of the material
- Dynamic code for anything printed, shared or displayed for weeks or longer: menus, packaging, posters, brochures, trade-show banners, direct mail. The destination can be changed later, and scans can be counted.
- Static code only for something that will never change and does not need tracking, such as a Wi-Fi login on a sign you control.
A dynamic code gives you control, but only if the code outlives the account. This is the deciding question to ask any provider: what happens to my printed codes if I cancel, downgrade or miss a payment? At QRlytics the answer is that codes created during an active subscription stay functional permanently, regardless of billing status. Think of your print run as a long-term asset, and choose terms that match.
Print for the real environment
QR codes are physical objects. The conditions where people scan them matter as much as the software behind them. One company that builds cashless payment systems for events notes that QR codes become unusable in direct sunlight or when a printed code gets wet, and that QR payments need a network connection to be authorised. For printed items that people handle, such as merchandise and giveaways, size, placement and tracking choices on swag decide whether the code scans in a real hand.
A practical print checklist:
- Dark pattern on a light background, with strong contrast.
- Enough empty margin around the code so the camera can find its edges.
- A size that suits the scanning distance: bigger for posters and window displays, smaller for packaging.
- A matt finish or lamination where glare or moisture is likely.
- No creases, curves or seams cutting through the pattern.
- A test scan of the actual printed proof on several phones, in the venue’s lighting, before the full run.
The common QR code mistakes marketers make are mostly in this list.
Give every code a clear job and a call to action
A code with a short line of text above it, such as “Scan for the menu” or “Scan to book”, gets more scans and also tells people what to expect when it loads. Ways to boost scans include framing, placement and a clear offer.
Keep the destination healthy
- Never delete a page that a printed code points to. Redirect it or repoint the code.
- Keep security certificates and domain registrations renewed, and give them a named owner.
- Make the page fast on mobile data and readable without logging in.
- Plan campaign end dates. Lifecycle scheduling lets a code show a different destination or message after a campaign closes, so a late scan lands somewhere sensible and not on an error.
Retail, hospitality and event scenarios
Retail and packaging
Shelf labels and packaging stay in circulation long after a campaign ends. Use dynamic codes so you can update the page when a promotion finishes, a product changes or a range is retired. A permanent code means the printed packaging remains useful for its whole shelf life.
Restaurants, bars and hotels
Table menus and room cards are scanned by people who often have weak signal inside thick walls. Keep the destination light, and keep a printed fallback, such as a short URL, for guests who cannot load the page. If your menu changes weekly, a dynamic code lets you update it without reprinting the table cards.
Events and conferences
Venue Wi-Fi is the weak point. Networks that work at registration can struggle once hundreds of people connect at once. Plan for it:
- Put the code on the screen and on printed signs, so people can scan from several places.
- Make mobile data work: keep the destination page small and avoid forcing a login.
- Set up offline check-in for ticket codes so that entry does not depend on the venue network. Staff should also have a manual list.
- Assign someone to monitor scans and respond to problems during the event.
Publishers and agencies
A code in a magazine, catalogue or client campaign may be scanned months after you deliver it. Agencies need to know that the code will work after the contract ends and after the client changes platform. This is the case for permanent codes and for QR API integration that lets you manage campaigns without reprinting.
Our perspective on QR code downtime
Most QR code downtime is not a technology failure. It is a business-model failure. A code is printed once and scanned for years, but many services treat it as a rental: stop paying, miss a payment or cancel, and the code stops working. The printed materials, the packaging and the signage stay, and the code on them is dead.
We built QRlytics on the opposite principle. Every code created during an active subscription keeps working permanently, even after cancellation and regardless of billing status. You should be able to choose a plan based on the features you need, not out of fear of what happens to your print run.
Control matters as much as permanence. With dynamic URL updates you can change a destination when a page moves or a campaign ends, without touching the printed code. With real-time scan analytics, global heat maps and CSV export, you can see when scans fall away and where people scan from, with GDPR-compliant tracking. Lifecycle scheduling lets you plan what a code does after a campaign finishes.
A printed code should be a measurable, durable channel, not a risk you carry in a drawer of unsold posters.
*The
Make your next print run reliable
If your codes sit on materials you cannot easily replace, start with the part you control: how long the code lives and whether you can change where it goes. QRlytics offers dynamic and static codes with permanent functionality for codes created during an active subscription, editable destinations, real-time scan analytics, customisable branding, API access and cryptographic authentication certificates. You can begin on the Free plan, which costs $0 per year, without a credit card, and look at the dynamic QR code generator to see how editable destinations work. The Pro plan unlocks unlimited codes, advanced analytics and API access, and its details are on the pricing page.

When you are ready to add scan counts to your campaigns, QR codes with analytics shows what you can track.
FAQ
Is a QR code down, or is my website down?
Open the destination URL directly in a browser. If it fails, your website is the problem. If it loads, scan the code and watch where it lands: a redirect or error page before your site points to the code or its redirect service.
Can I fix a broken QR code without reprinting?
Only if it is a dynamic code. You change the destination URL behind the code, and every printed copy then goes to the new page. A static code stores the address itself, so a wrong or dead address means replacing the print.
Will my QR codes stop working if I cancel my subscription?
That depends on the provider, and it is worth checking before you print. With QRlytics, codes created during an active subscription remain functional permanently, regardless of billing status, including after cancellation.
How can I tell if people are failing to scan my code?
Watch your scan analytics. A sharp drop to zero at a busy time suggests a fault, while steady scans with few conversions suggest a problem on the destination page. Without analytics, you only find out when customers complain.
What should I do at an event if the Wi-Fi fails?
Switch to mobile data for the destination page, keep a printed short URL beside the code, and use offline check-in or a manual list for tickets. Test all three on site before doors open.
Sources
- Caída del sistema QR complica viajes en Santiago (ADN Radio, 22 August 2026)
- Paysafe Service Disruption - QR Code Partner, 12 August 2026 (IsDown)
- Hybrid Cashless Payment Systems: RFID, NFC, and QR for events (Billfold)
- QR Codes on Swag: Size, Placement and Tracking That Works