What to write about
- A result that looks wrong. Include the result link from the share button, your approximate plan speed, whether you were on Wi-Fi or Ethernet, and the browser you used.
- A bug. Tell us what you clicked, what you expected and what happened. A screenshot helps.
- A factual correction. If something on the site is inaccurate, say which page and what the correct information is. Sourced corrections are especially welcome.
- A privacy or data question. The privacy notice describes exactly what is stored and what is sent to the measurement endpoint. If something there is unclear, ask.
What to leave out
Please do not send passwords, account numbers, identity documents or anything else sensitive — nothing on this site needs it, and email is not a secure channel for those things.
You do not need to tell us your name or address. A browser and a description of the problem is usually enough to reproduce a bug.
What to expect
There is no support team, no ticket system and no guaranteed response time. Corrections, sourced factual fixes and reproducible bug reports are the most useful things to send.
The troubleshooting guide and the methodology page answer most questions about a slow or unstable connection faster than email can.
There is no paid tier, so nothing here is a support contract.