Every quarter of an hour five of our servers — in Amsterdam, Frankfurt, Istanbul, Tokyo and Hong Kong — open 77 popular services and record the answer. Below is what came out over the last day: a green band means the service answered, red means it was silent.
These are our own measurements, not user complaints. What follows from that is under the table.
a day agonow
The band is one day, left to right, fifteen minutes per segment. The colour of a segment is how many of our points did not see the service at that moment.
| What you see | What it means |
|---|---|
| solid green | a day without a single refusal — the service answered all our points |
| yellow notches | one point got no answer. That is what both a regional obstruction and an ordinary network miss look like |
| a red stretch | the service was silent to several points at once — that looks like a real failure |
| grey stretches | we were not checking at that time: the sweep did not run, or the service was added recently |
| "will not let us in" | the service answers, but refuses our data-centre address. That is its rule, not a fault |
It does not know what is happening at your end. Our points sit in data centres in five countries, and their network is a different one: they do not see blocking at a particular provider, while they do catch refusals a live person never meets. If a service is silent for you and green here, it is almost certainly the road to it, and that is cured by changing the route. If it is red here, it is not you, and it is the service you have to wait for.
What is happening in your own network can be checked right in the browser. A daily snapshot from our nodes with status codes and latencies is on the page "what opens from where". Your own site from these same points — here.
Then it is the road to it that is broken, not the service. That is exactly what a VPN fixes — and we have a free plan for it.
Get a key →Was this useful?
One tap, no sign-up