Contact

Contact and prepare a useful support request

Published by InternetSpeedGeo · Reviewed

Choose the address that matches your request

×

General support, editorial corrections and questions about the project go to hello@internetspeedgeo.com. Questions about processing, consent or a stored contribution go to privacy@internetspeedgeo.com. There is no guaranteed response time. These addresses are published contact channels for InternetSpeedGeo, not the billing or network support desks of the providers shown in the directory. If your concern is a service outage, contract or bill, contact your internet provider through its own verified channel as well.

A clear first message explains what you were trying to do, what happened and what outcome you want. You do not need to write a technical diagnosis. A plain description such as a test stopping during upload is more useful than guessing that an unspecified server is broken. Identify the page and language, because the same tool can appear with different wording. If several separate issues occurred, give each its own short description so their evidence does not become mixed. The suggestions on this page are aids for communicating; they are not mandatory forms or a promise that every message will receive a particular resolution. Send the relevant context you have and omit information that does not help explain the request.

Start with a concise, reproducible account

×

A good support report separates the action, expected behavior and observed behavior. State the page URL, the control you used and the point at which the outcome differed from what you expected. Add the approximate date and time with a timezone if timing matters. Record the browser and device type, plus whether the connection was Wi-Fi, Ethernet or mobile data. A VPN or managed network can change the path, so mention its presence without disclosing credentials or confidential network details.

An adaptable message could read: I opened the named page in this browser, selected this action and saw this exact message. I expected this next screen. The issue occurred under this connection condition and repeated when I tried the same action again. Replace each description with your own observation rather than copying an example as if it happened. If you changed conditions during troubleshooting, describe the changes in order. A report that says one browser worked and another failed is more useful when both were tried on the same connection. Do not repeat a bandwidth consuming test many times solely to make a support message longer. One clear failure description and a limited comparison can establish the issue.

When the full speed test does not complete

×

For a failed speed test, record whether it stopped during latency, download or upload, and copy the exact visible error if possible. Explain whether ordinary pages loaded at the same time and whether the connection stayed active. Keep partial readings identified as partial. The test requires valid measurements from its required phases, so an earlier number on the screen is not necessarily a completed result that should appear in history.

Before sending the report, a safe check is to reload the page once and ensure the browser remains visible and the device awake during a new attempt, if your data allowance permits. If the network belongs to an employer, school or venue, a measurement endpoint may be restricted by its policy. Ask the appropriate administrator rather than bypassing required controls. A useful hypothetical report would say that the latency phase completed but the upload phase showed an error in a particular browser on a managed connection. It would not claim a provider wide outage without further evidence. Include whether the same device can complete the test on another authorized connection if you already know that; there is no requirement to purchase access or alter protected settings to produce a support ticket.

When a completed result seems unexpectedly low

×

An unexpectedly low number is a measurement question as well as a possible interface question. Include the completed download, upload and ping values, available jitter, the measurement time and the connection used. State the plan's advertised rate only if you know its units and relevant direction. A download plan figure cannot establish an expected upload result, and a Wi-Fi link label is not the same as an internet throughput guarantee.

Describe the symptom that matters: slow file transfers, calls that pause, delayed interaction or another task. If a comparable Ethernet observation is available, include it alongside the Wi-Fi observation and explain the conditions. If not, say so rather than assuming a wired baseline. A short hypothetical message might explain that a laptop repeatedly measured lower in one room than near the router, while the browser and service remained the same. That supports a coverage investigation more clearly than attaching a large unlabelled collection of screenshots. InternetSpeedGeo cannot remotely certify a plan or repair a provider's network, but a well described comparison can help distinguish an expected limitation from a display problem or misunderstanding. The methodology and relevant guide may answer the unit or destination question immediately.

When ping readings disagree

×

Tell us which ping readings you are comparing. The dedicated Ping Test page times HTTP requests to this website, while the full speed test gets latency summaries from Cloudflare measurements. A game, command line tool or router diagnostic can use another protocol and destination. Include the named tool and destination when available. A difference between those readings alone does not establish that one is wrong.

For the dedicated ping tool, mention whether all twelve samples completed and whether the chart showed a single unusual response or repeated variation. Quote the average, median and jitter separately instead of calling them all ping. If the concern is a calculation, provide the relevant sample values as shown or a readable chart screenshot, while recognizing that rounded display values can differ from underlying precision. A hypothetical issue report could explain that a displayed median appears inconsistent with the visible sample order after sorting. That is a specific calculation question. A broader statement that a game has more delay than the website needs application context and belongs partly with that game's support or network administrator. Keep observed behavior distinct from conclusions about packet loss, because this ping tool does not measure a packet loss percentage.

When jitter is missing or a label is unclear

×

A missing jitter field can be a legitimate absence of measurement. The interface should not invent zero to fill it. If you think a missing field is being described incorrectly, send the page, language and wording around the field. Explain whether the problem is the absence itself, a misleading score, an export mismatch or a translation. These possibilities involve different parts of the site, and naming the one you saw makes a correction easier to investigate.

For other unclear labels, quote the exact phrase and describe what you understood it to mean. For example, a visitor may interpret a country provider average as a measurement for the point selected on the map. The report should identify the label or arrangement that created that impression. A screenshot can help when several nearby elements contribute to confusion, but a short text description is enough when the wording itself is the issue. Suggestions for clearer phrasing are useful when grounded in the actual behavior. Do not replace an uncertain measurement concept with an absolute guarantee merely to make a label shorter. The goal of an editorial correction is to make the measured scope more understandable, including the circumstances where information remains unavailable.

When the provider name appears wrong

×

Include the country, displayed provider name and the broad connection context. Public network organization names and consumer brands can differ, particularly with wholesale service, mobile infrastructure, corporate routing and VPN exits. State whether a VPN or other intermediary was active. If an official provider or network source supports a different identity, include the link and explain which part of the displayed label it contradicts.

Do not send a router password, subscriber account number or identity document to establish a naming issue. A carefully limited extract from the IP tool or a cropped screenshot is usually more relevant. If you need to share the public IP privately for a particular lookup question, consider its purpose and avoid placing it in a public comment or widely shared document. A hypothetical report might say that the tool shows an infrastructure organization while the purchased service uses a different brand, and ask whether the directory can recognize that relationship. That does not necessarily mean the speed value belongs to a different connection. Provider identification, country lookup and measured throughput should be checked as separate questions so a label correction does not become an unsupported claim that the numerical measurement was fabricated.

When a map or IP location is inaccurate

×

First distinguish the location source. My IP and the home page can show an approximate location from an IP database. The map's location button can separately request device location through the browser. A typed place search uses a search service. Tell us which of these produced the unexpected result, because a wrong IP city, denied device permission and an ambiguous place name are different issues.

Include the displayed city or region and a broad expected region if that is enough to demonstrate the mismatch. You do not need to send a precise home address or live coordinates. For a place search problem, provide the search phrase and the selected result; names shared by multiple places may need a country or region qualifier. If location permission failed, describe whether the browser showed a prompt and whether the network tool continued to work. A hypothetical report could explain that the IP estimate points to another city while manual map search finds the intended place. That illustrates database uncertainty rather than proof that the device has moved. InternetSpeedGeo cannot promise immediate changes to an external IP database or map dataset, but identifying the source allows the discrepancy to be understood and directed appropriately.

When Reports or Statistics appears empty

×

Reports and Statistics read local browser history. An empty page can result from using another browser or profile, clearing site data, private browsing, storage restrictions or having no completed valid measurements in that context. Tell us whether a completed result was previously visible in the same browser profile and whether anything changed before the history disappeared. There is no account synchronization promised across devices, so a new device is not expected to retrieve the old device's local table automatically.

If a newly completed result is visible on the home page but not retained after a reload, say that specifically. It can help distinguish successful measurement from unsuccessful local storage. Avoid clearing data as a first troubleshooting step when you are trying to preserve evidence; export existing reports first if possible. A message can state which page showed the result, whether the date was correct and what happened after reopening the site. If you have already cleared local data, say so. The project does not promise recovery of deleted browser history. A server contribution is a separate flow and is not a backup from which the Reports page automatically restores your personal sequence. That distinction is particularly important when explaining a missing record.

When an export needs investigation

×

For a CSV problem, explain whether the download failed, the file opened incorrectly, a field was blank or the content differed from the on screen record. Name the program used to open the file and its locale if separators or decimal formatting are involved. Spreadsheet programs can interpret dates and numbers according to their own settings. A file that looks odd in one program may still contain the expected text, so describe the display rather than immediately assuming the export lost information.

Share a minimal excerpt when possible. An export can contain dates, connection labels and server information from several sessions, and unrelated rows rarely help explain a single missing column. If you edit the excerpt to remove personal details, state that it has been redacted and preserve the structure relevant to the issue. A hypothetical support note might say that the jitter field is blank for a record whose on screen value was also unavailable, then ask whether that is expected. In that case, preserving a missing value can be correct behavior. Another note might identify a date that a spreadsheet interpreted in the wrong order. Distinguishing raw exported text from the receiving application's interpretation makes the report more actionable.

When installation or the app window behaves differently

×

The App page describes installing the website through a supporting browser. Include the operating system, browser and the installation route you tried. State whether a prompt appeared, whether a home screen icon was created and what happened when opening it. An unavailable install prompt can reflect browser or platform behavior; it does not mean you need an unverified store download. The website remains usable in an ordinary tab when installation is not offered.

If the installed window shows different history from a normal tab, report both contexts and whether they use the same browser profile. Do not assume that every platform shares storage in the same way. If a live test fails while disconnected, remember that installation does not make remote speed measurement an offline operation. A useful hypothetical report could explain that the home screen icon opens the site but a particular link exits into the browser. Identify the link and what you expected. That is more specific than saying the app is not native enough. Screenshots of menu labels can be useful after redacting notifications and account details. There is no need to uninstall or erase site storage before describing the behavior you already observed.

How to propose an editorial or translation correction

×

Send the page URL, selected language and exact disputed passage. Explain the factual issue or ambiguity, suggest a correction if you have one and link to a relevant primary source where available. For a translation issue, describe the meaning a native reader would infer and how that differs from the tool's actual behavior. A term can be grammatically correct yet misleading when used for a measurement with a narrow definition.

A correction request should preserve the distinction between a concept and the implemented feature. For example, an article may discuss packet loss as a cause of application problems while the current test does not measure it. If the wording makes the latter unclear, point to that connection directly. Likewise, a timing explanation should not imply continuous transfers throughout the entire visual countdown when the requests are finite. A hypothetical editorial report might quote a sentence suggesting a city average and explain that the table actually groups by country. These are concrete changes that can be assessed against the implementation. There is no requirement to rewrite a whole article or provide a personal biography. The most useful evidence is the smallest passage and source that clearly establish the correction.

How to ask about consent or personal information

×

Use privacy@internetspeedgeo.com for these requests. State the action involved, approximate date, tool URL and what you want to understand or change. If you are asking about a server contribution, include a result identifier if available and distinguish it from local browser history. If you are asking about a consent option, describe the choice and the interface behavior. Different processing activities have different controls, so a specific request helps avoid misunderstandings.

Do not send identity documents, passwords, full payment details or unrelated browsing history preemptively. Proportionate verification may be needed for some requests, but introducing sensitive information before it is relevant can create an unnecessary new privacy issue. The service has no required user account, which can limit how reliably a stored record can be associated with the person writing. A useful hypothetical message might say that you cleared Reports and now want to ask separately about retention of a contribution. Another might ask why the consent interface makes a Google request before an optional advertising choice. The privacy policy explains those flows, and a report can identify where its explanation did not answer your specific question. Applicable rights depend on the relevant law and circumstances.

Prepare screenshots and attachments carefully

×

Review an attachment before sending it. Browser screenshots can reveal other tabs, bookmarks, account names, notifications, location details or a full public IP address. Crop to the portion necessary to demonstrate the issue and remove unrelated information. Keep the relevant error, units, labels and timestamp readable. If a crop would hide the layout problem itself, explain the surrounding arrangement in text instead of exposing more of your screen than necessary.

For repeated observations, a compact table with named conditions is usually easier to assess than a large image archive. Label each record as a completed measurement or a failed attempt, and indicate any changes in device, connection or time. Preserve original data privately if you need it for your own records, but send only the extract relevant to the question. Do not include access tokens, saved passwords, router administration pages or confidential work documents in an attachment. If a diagnostic log contains information you do not understand, ask what limited detail is needed before sharing the entire file. The published email addresses are not a promise of a specialized secure upload process, and ordinary support should not require you to reveal secrets to describe a visible website problem.

Know which organization can act on the issue

×

InternetSpeedGeo can receive reports about its tools, explanations and data handling. Your internet provider controls its subscription, network service and billing processes. The owner of a managed network controls its rules and equipment. An application provider controls its own service behavior. External map and IP data services control their source datasets. Identifying that boundary helps you avoid waiting on the wrong contact for a change they cannot make.

You can still use a measurement report as evidence in the appropriate conversation. For a hypothetical provider request, describe repeated observations from an authorized wired connection, the relevant times and the application impact, while avoiding a claim that a browser test alone proves a contractual breach. For a workplace issue, describe the affected task and let the administrator decide which diagnostics are allowed. For an IP location discrepancy, preserve the lookup source and broad region. These examples show how evidence travels with its limitations. They do not create a guarantee that another organization will accept a particular test or resolve the issue. Ask the responsible service what information it requires and retain enough context to explain how your observations were obtained.

A final review before sending

×

Check that any link points to the page you actually used and that an attachment opens before sending it. If you quote an error translated from another language, include the original wording as well when practical. Small details like these can prevent an avoidable misunderstanding during investigation.

Read the message once as if the recipient had never seen your screen. It should name the relevant page, explain the action and outcome, identify the conditions that matter and state the requested help. Remove repeated descriptions that do not add evidence. Keep hypotheses separate from observations. If the issue no longer occurs, say that and describe what changed; an intermittent problem can still be useful to report when its limits are clear.

A complete adaptable structure is: purpose of the message; page and language; device and browser; connection context; steps taken; observed result; expected result; limited evidence; and requested outcome. These are headings you can adapt, not a required form. For a simple typo, the page and sentence may be enough. For a measurement failure, the stage and exact error matter more. For a privacy question, the data flow and desired action matter most. Send general requests to hello@internetspeedgeo.com and privacy requests to privacy@internetspeedgeo.com. There is no response time guarantee, and repeated messages containing the same information do not add diagnostic value. If new evidence becomes available, keep it connected to the original issue so the changing conditions remain understandable.

Overview

Give your question useful context

  1. Describe the issue
  2. Note time and setup
  3. Contact support
Include the affected activity and test reference if available. Never send passwords or publish your full IP address unnecessarily.

Use hello@internetspeedgeo.com for support, project questions and factual corrections. Use privacy@internetspeedgeo.com for personal data questions. The guidance below helps you describe an issue with enough context and without unnecessary sensitive information.

ContactMethodologyWiki

Useful, at a glance

Relevant next steps to help you put this page into practice.