Normalize
We turn a full link into a clean website name. For example, a video link on YouTube becomes youtube.com.
How it works · version 2
A clear answer, step by step.
We compare recent website checks by country and show the result in plain language.
How a lookup works
You enter a website and choose a 7, 30, or 90 day window. Our server cleans up the address, checks recent evidence, and returns one report.
Check
We group recorded website-connection tests by country and exact hostname. Known monitored sites include their explicitly listed main and www hosts; other subdomains remain separate. The displayed OK percentage is OK tests divided by all recorded tests, not the percentage of users with access.
Compare
Regional summaries add context. Different summaries and scheduled updates may reuse the same measurements; agreement does not establish independent confirmation.
Explain
The page gives a plain answer first, then lets you open the evidence, country rows, and optional technical failure details.
How the scanner overview works
The headline, map, rankings, and alerts pages read the same saved hourly update. Opening those pages does not start another round of checks.
Scan on schedule
A bounded watchlist is measured by the scheduled scanner. Each run records its start, finish, successes, failures, and evidence window.
Review repeated snapshots
Legacy incident history came from repeated score snapshots. A repeated snapshot may contain the same underlying checks, so this is not proof of independent networks or new measurements. New outcome-count reports do not confirm or resolve that legacy history; a rolling window can change without a new test.
Publish one update
The homepage, world map, rankings, and alerts use the same saved results, so their answers stay in sync.
Show the useful facts
Each headline includes its place, number of checks, and updated time.
Read the recorded outcomes
The default period is 30 completed UTC days: the start midnight is included and the end midnight is excluded. The fetch timestamp is when we retrieved the report, not when every test ran. Repeated tests may come from the same network.
Worldwide rates are weighted by test counts, never averaged country percentages. Tests without a recorded country stay in the worldwide total. Cross-site rates are withheld when host scopes overlap or source windows differ.
Every page uses one shared evidence policy. Repeatedly downloading the same data does not make it independent confirmation.
An unusual result is not proof of blocking
Current reports show separate OK, unconfirmed anomaly, confirmed-blocking test, failed-test and unknown counts. These categories sum to the total. Failures and unknowns remain in the OK-percentage denominator. Confirmed blocking refers only to those recorded tests, not a countrywide result. Older LONI reports used a 0–1 upper-tail interference score; it is not the percentage of failed checks and cannot be converted into an OK percentage.
Access was observed
An OK result means access was observed in that test. A country with a few OK tests and many anomalies is not classified as generally accessible: the rate, counts and majority-outcome description remain visible. We do not apply a confidence cutoff or infer population availability from a small, non-random sample.
Not enough data
Missing or outdated evidence cannot establish a current answer. A small sample is displayed as a small sample; even one OK test cannot establish general availability.
Mixed evidence stays mixed
Different networks, dates, and test methods can disagree. The page says so instead of averaging the conflict away.
Freshness and caching
Saved results keep popular reports quick and avoid repeating the same work.
Saved reports
Successful reports can be cached at the nearby edge for up to one hour, bounded by the remaining evidence lifetime. Every report shows when its evidence was checked; an outdated snapshot is not a current result.
Popular websites
A small list is refreshed every hour. Saved reports can be retained for up to 24 hours, but evidence older than 3 hours is shown as outdated or unknown. A fresh technical-detail check does not reuse an older result.
Map and alerts
The map, rankings, and alerts use the same saved hourly update and show when it was made.
Request limits
Normal checks and fresh technical checks have separate safety limits. If the service is busy, it asks you to wait one minute before trying again.
Known limits
Coverage and ordinary network failures can affect results.
Conditions can differ by network, place, and time. Reports describe
observed access, not who caused it or a nationwide policy.