---
title: "Scans now answered at the edge, near your visitor"
description: "Most QR code scans and short links on linkbreak.ing are now answered close to the visitor, on a global edge network. In Europe a scan check went from 164 ms to 34 ms, and each scan answered there is still recorded in your analytics."
canonical: "https://linkbreakers.com/help/article/scans-answered-at-the-edge"
last-updated: 2026-11-17
---

# Scans now answered at the edge, near your visitor

> Most QR code scans and short links on linkbreak.ing are now answered close to the visitor, on a global edge network. In Europe a scan check went from 164 ms to 34 ms, and each scan answered there is still recorded in your analytics.

## Short answer

Most QR code scans and short links on `linkbreak.ing` are now answered at the edge: close to the person scanning, instead of travelling all the way to our servers and back. That covers the links that send a visitor straight to a destination, about 94 in 100 scans. It has been live on all of `linkbreak.ing` since 16 November 2026, 23:47 UTC.

In Europe, our status page check of a scan went from a median 164 ms to 34 ms. In Asia, from 145 ms to 50 ms. Each of those scans is still recorded in full in your analytics.

## What we shipped

### Most scans answered near the visitor

When someone scans a code that sends them straight to a page, the answer now comes from a point of our global edge network near them. Before, a scan on a poster in Paris or Seoul made the full trip to our servers and back before the phone got anything. Now that trip stays in the visitor's region.

Our status page checks a scan every minute from three places. Here is the median time before and after, with the 90th percentile after (9 checks in 10 are at least this fast):

| Where the check runs | Before (median) | Now (median) | Now (90th percentile) |
|---|---|---|---|
| Europe (Amsterdam) | 164 ms | 34 ms | 57 ms |
| US East (Atlanta) | 70 ms | 44 ms | 63 ms |
| Asia (Seoul) | 145 ms | 50 ms | 61 ms |

**Median time to answer a scan, status page checks**

- **164 → 34 ms** Europe
- **145 → 50 ms** Asia

| Where the check runs | Before | Now |
|---|---|---|
| Europe (Amsterdam) | 164 ms | 34 ms |
| US East (Atlanta) | 70 ms | 44 ms |
| Asia (Seoul) | 145 ms | 50 ms |

Median of the status page's scan checks, before and after the edge went live on all of linkbreak.ing (16 November 2026, 23:47 UTC). Source: status.linkbreakers.com.

Before this work we also measured the full time of a scan, until the first byte reached the phone, from public test points: a median 377 ms in Europe and 402 ms in Asia. That is the wait the edge removes for most scans.

You can watch the live response times on [status.linkbreakers.com](https://status.linkbreakers.com).

### Your analytics are unchanged

A scan answered at the edge is recorded like any other: the visit appears in your analytics with the same details as before. We checked the records field by field against scans answered by our servers and found 0 mismatches. The visitor simply does not wait for it.

### Changes reach the edge in seconds

When you delete a link, it stops working at the edge in about 2 seconds. A link you remove does not keep answering from somewhere far away.

### The API, live updates and MCP got faster too

The same work made the rest of Linkbreakers quicker to answer: the API, the live updates you see in the app, and the MCP server that AI agents use.

| Region | API, live updates and MCP |
|---|---|
| Paris (90th percentile) | 680 ms before, about 225 ms now |
| Europe and Asia | about 165 to 185 ms |
| US East | about 80 ms |
| US West | about 50 ms |

## Why it matters

A QR code on a poster, a table or a pack is often scanned once, by someone standing in front of it with a few seconds to spare. If the page takes a moment to open, some of them put the phone away. When the code is how you meet a customer, the first second decides whether there is anything to capture at all.

Answering near the visitor means a code printed in Amsterdam or Seoul opens about as quickly as a code printed next to our servers. Your campaign depends less on where your audience happens to live.

## Limits: what is not at the edge yet

Some scans still go to our servers, as before:

- **Custom domains.** Links on your own domain are next; that work is in progress.
- **Forms, pages and the Chat bot.** These steps show a page built for the visitor.
- **Links with conditions or a Traffic split.** Their workflow decides where each visitor goes, and that decision runs on our servers.

So it is most scans, not every scan. A link that goes straight to a destination on `linkbreak.ing` gets the edge today.

For what happens inside a scan and how we measure its server time, see [How fast is a Linkbreakers scan?](/help/article/how-fast-is-a-linkbreakers-scan). For uptime, see [Linkbreakers uptime: zero server errors](/help/article/linkbreakers-uptime-zero-server-errors).

## Frequently asked questions

### Do I need to change anything?

No. Links on `linkbreak.ing` that go straight to a destination are answered at the edge already, including QR codes you printed long ago.

### Are scans answered at the edge still counted?

Yes. Each one is recorded in your analytics, with the same details as before.

### If I delete a link, does it keep working somewhere?

No. A deleted link stops working at the edge in about 2 seconds.

### What about my custom domain?

Custom domains are not at the edge yet. We are working on it, and this article will say so when they are.

### Why are links with conditions not at the edge?

A link with conditions or a Traffic split looks at each visitor before deciding where they go. That decision runs on our servers today, so those scans answer as they did before.

### Where can I see the speed myself?

On [status.linkbreakers.com](https://status.linkbreakers.com), which shows the response time of our checks from Europe, US East and Asia.
