Logo of linkbreakers

Linkbreakers uptime: zero server errors

Over three months, Linkbreakers answered more than 900,000 requests to QR codes and short links without a single server error. Here is the data, and what it means for your QR codes and links.

Overview
2 min read
By Linkbreakers
Updated October 2, 2026

Short answer

Over three months, Linkbreakers answered more than 900,000 requests to QR codes and short links with zero server errors. Not a low error rate: none. Traffic grew over the period, and the error count stayed at zero every week.

The data

900K+
requests answered in 3 months
0
server errors
13 weeks
in a row without a server error
Requests per week and server errors per week over three months. Server errors were zero every week.020K40K60K80K100K120K51,232 requests (estimated from log volume), 0 server errorsJuly50,560 requests (estimated from log volume), 0 server errors92,242 requests (estimated from log volume), 0 server errors67,911 requests (estimated from log volume), 0 server errors50,771 requests (estimated from log volume), 0 server errors55,391 requests (estimated from log volume), 0 server errorsAugust77,045 requests (estimated from log volume), 0 server errors76,273 requests (estimated from log volume), 0 server errors70,299 requests (estimated from log volume), 0 server errors80,130 requests (estimated from log volume), 0 server errorsSeptember84,938 requests (estimated from log volume), 0 server errors111,404 requests (measured), 0 server errors77,780 requests (measured), 0 server errors
Requests per week, measuredRequests per week, estimatedServer errors per week: 0
Every request to Linkbreakers QR codes and short links, per week, over 13 weeks. The last two weeks are counted from request logs. Earlier weeks are estimated from log volume, using the requests per log line measured in those two weeks.

What this means for your QR codes

  • Your printed codes keep working. A QR code on a poster, a menu or a business card resolves every time it is scanned.
  • Improvements never interrupt scans. We ship updates often, and visitors never notice.
  • Problems fix themselves. If part of the service stops answering, traffic moves away from it automatically.

Limits and caveats

  • The last two weeks are counted from request logs. Earlier weeks are estimated from log volume, so those bars are approximate.
  • Uptime is about Linkbreakers answering. Whether the website a link sends people to is up is outside our control.

Frequently asked questions

Do scans fail while you ship updates?

No. A new version is ready and answering before the old one stops, so there is always a version answering.

What counts as a server error?

Any time our service fails to answer a request it should have answered. Requests for links that do not exist are answered with a "not found", which is the correct answer, not an error.

Sources

  • Linkbreakers request logs

About the Author

LS

Laurent Schaffner

Founder & Engineer at Linkbreakers

Passionate about building tools that help businesses track and optimize their digital marketing efforts. Laurent founded Linkbreakers to make QR code analytics accessible and actionable for companies of all sizes.

Related Articles

How fast is a Linkbreakers scan? Latency, and what happens in it

A Linkbreakers scan answers in a median of 65ms of server time while it runs a full workflow: conditions, bot and AI agent detection, visitor recognition, traces and webhooks. Here is how we measure it, why it is fast, and how it compares with link shorteners and QR code tools.

Are links and QR codes guaranteed to work?

Understanding Linkbreakers' reliability commitments, infrastructure redundancy, monitoring systems, and what guarantees exist for your QR codes and shortened links in mission-critical campaigns.

How QR code tracking works: from scan to analytics

See the scan to redirect to analytics flow, the difference between static and dynamic QR codes, plus real-world examples and FAQs.

Back to Help Center