Public benchmark
Public performance benchmarks
Metricanic publishes redirect latency results from a real public run so performance teams can judge speed claims against visible methodology, route assumptions, and sample size instead of vague marketing copy.
This page documents published redirect-latency measurements for a live Metricanic tracking URL. It does not claim identical latency for every route, geography, or campaign setup, and it complements, rather than replaces, the platform's routing, reporting, event, and postback workflow.
Free starts without a card. Paid plans include a 7-day trial.
Benchmark summary
The published run measured a live Metricanic tracking URL from the public internet and recorded the time until Metricanic issued the 302 redirect toward the landing page.
39 visible probe results, with p50 at 41 ms, p95 at 94 ms, p99 at 162 ms, and a minimum observed result of 19 ms.
Full location table
Each row shows one visible probe result from the published run. Every probe hit the same live Metricanic URL, waited for Metricanic to process the request, and measured the returned 302 redirect toward the landing page.
| Location | Result | Measured time | Class |
|---|---|---|---|
| Austria, Vienna | OK | 38 ms 0.038 s | Ultra Fast |
| Brazil, Sao Paulo | OK | 28 ms 0.028 s | Ultra Fast |
| Brazil, Sao Paulo | OK | 39 ms 0.039 s | Ultra Fast |
| Bulgaria, Sofia | OK | 31 ms 0.031 s | Ultra Fast |
| Canada, Vancouver | OK | 31 ms 0.031 s | Ultra Fast |
| Cyprus, Larnaca | OK | 36 ms 0.036 s | Ultra Fast |
| Czechia, Ceske Budejovice | OK | 19 ms 0.019 s | Ultra Fast |
| France, Roubaix | OK | 59 ms 0.059 s | Ultra Fast |
| Germany, Frankfurt | OK | 33 ms 0.033 s | Ultra Fast |
| Germany, Nuremberg | OK | 39 ms 0.039 s | Ultra Fast |
| Hungary, Nyiregyhaza | OK | 60 ms 0.060 s | Ultra Fast |
| India, Mumbai | OK | 41 ms 0.041 s | Ultra Fast |
| Israel, Netanya | OK | 29 ms 0.029 s | Ultra Fast |
| Italy, Milan | OK | 30 ms 0.030 s | Ultra Fast |
| Japan, Tokyo | OK | 45 ms 0.045 s | Ultra Fast |
| Moldova, Chisinau | OK | 58 ms 0.058 s | Ultra Fast |
| Netherlands, Amsterdam | OK | 35 ms 0.035 s | Ultra Fast |
| Netherlands, Meppel | OK | 35 ms 0.035 s | Ultra Fast |
| Poland, Poznan | OK | 81 ms 0.081 s | Ultra Fast |
| Poland, Warsaw | OK | 78 ms 0.078 s | Ultra Fast |
| Portugal, Viana | OK | 83 ms 0.083 s | Ultra Fast |
| Romania, Bucharest | OK | 36 ms 0.036 s | Ultra Fast |
| Russia, Moscow | OK | 90 ms 0.090 s | Ultra Fast |
| Serbia, Belgrade | OK | 20 ms 0.020 s | Ultra Fast |
| Singapore, Singapore | OK | 45 ms 0.045 s | Ultra Fast |
| Slovenia, Maribor | OK | 59 ms 0.059 s | Ultra Fast |
| Spain, Barcelona | OK | 53 ms 0.053 s | Ultra Fast |
| Spain, Madrid | OK | 39 ms 0.039 s | Ultra Fast |
| Sweden, Stockholm | OK | 42 ms 0.042 s | Ultra Fast |
| Sweden, Stockholm | OK | 28 ms 0.028 s | Ultra Fast |
| Switzerland, Zurich | OK | 32 ms 0.032 s | Ultra Fast |
| Turkey, Istanbul | OK | 133 ms 0.133 s | Fast |
| Turkey, Istanbul | OK | 179 ms 0.179 s | Fast |
| UK, Coventry | OK | 46 ms 0.046 s | Ultra Fast |
| Ukraine, Khmelnytskyi | OK | 80 ms 0.080 s | Ultra Fast |
| Ukraine, Kyiv | OK | 63 ms 0.063 s | Ultra Fast |
| Ukraine, Kyiv | OK | 45 ms 0.045 s | Ultra Fast |
| USA, Atlanta | OK | 32 ms 0.032 s | Ultra Fast |
| USA, Los Angeles | OK | 45 ms 0.045 s | Ultra Fast |
Methodology
What was measured: time from an external probe reaching a live Metricanic tracking link to Metricanic processing the request and issuing the 302 redirect toward the landing page.
How it was measured: an external multi-location HTTP checking service hit the same Metricanic URL from many public probe locations at roughly the same time.
Route assumptions: Single 302 redirect route, warm route, and https request over the public internet.
Limitations
- This page documents one published run, not every possible route or every geography at all times.
- Different routing rules, DNS paths, and landing-page geographies can change observed latency.
- Warm-route results are useful for steady-state operations but are not a cold-start benchmark.
- Throughput and uptime are intentionally omitted here until Metricanic publishes those measurements.
Ready to track faster with public proof?
Use Metricanic when your team wants low-latency routing, cleaner operational visibility, flexible reporting, event-based conversions, and a benchmark page you can actually point buyers to.
Get started free