Testing internet speed before you commit to a stay

Test the connection where you will actually work, at the hours you will actually work, before you depend on it. A speed figure in a listing may have been measured at another time or in another part of the building, and it says little about how the connection behaves when several devices are online at once. Most of the useful checking takes a few minutes of testing and a couple of direct questions to the host.

The aim is to answer three questions: whether the connection is fast enough for your work, whether it stays steady through the day, and what you will do when it fails.

Measure the connection where and when you will work

The most reliable test is one run inside the apartment, from the exact spot where you plan to sit. If you can arrange it before you travel, ask the host to run an online speed test from that spot and send you a screenshot of the download speed, upload speed and latency, or to join a short video call from there. If that is not possible, run the test on your first morning and keep the result. Record the download speed, the upload speed and the latency that the test reports.

Repeat the test at a time when the building is likely to be busy, such as early evening, because shared connections often slow down together. Run it several times and look at the pattern. A connection that is steadily moderate usually serves you better than one that jumps between very fast and very slow.

Latency matters as much as raw speed for video calls and remote desktop sessions. High or erratic latency shows up as delayed audio, frozen video and lag when typing into a remote session. If the numbers swing widely from one test to the next, treat that as a warning sign rather than an average to accept.

Ask the questions a test cannot answer

Some details only the host can provide. Ask which internet provider is used, what the contracted speed is, whether the connection is shared with other households or a building network, and whether there is a data cap or fair-use limit and what happens when it is reached. Ask where the router is located and whether there is a wired port near the desk, because a cable is usually more stable than Wi-Fi over distance and through walls. Also ask who to contact if the connection fails, and how quickly they usually respond.

Ask whether there have been outages and how they were resolved. A host who explains the connection clearly is usually easier to work with than one who avoids the question, and the answers will show you how much support to expect once the stay starts.

Plan a fallback for when the connection fails

Every long stay needs a plan for when the fixed connection goes down. A mobile data plan, a local SIM or an eSIM can cover email, messaging and document work for a while, and many phones can share their connection with a laptop through a hotspot. Check the signal at the spot where you will work rather than only at the front door, because thick walls and upper floors can weaken coverage.

Mobile data is usually expensive for heavy use and video calls, and allowances differ from one plan to another. Estimate how much data a typical working day uses, confirm that hotspot sharing is allowed, and read the terms of any plan before you arrive. Plan options also differ by country, so check the details with the provider rather than assuming a plan from home will work.

Match the speed to the work

Different kinds of work need different things from a connection. Email and documents need only a small fraction of what a video call uses. An HD video call typically needs roughly 1.5 to 4 Mbps in each direction for each person in the household who is on a call at the same time. Check the published requirements of the video tool you use, since they vary, and multiply the figure by the number of people who will be on calls at the same time. Video calls depend on upload speed as well as download speed, and several people in one household on calls at once can strain a weak connection. Large file transfers, such as uploading video or large datasets, depend heavily on upload speed. Remote desktop sessions and cloud development tools depend more on low latency than on peak throughput. Round-trip latency of roughly 100 to 150 milliseconds or less generally keeps calls and remote desktops responsive.

A connection that only just meets the minimum for your work will struggle as soon as someone else in the building starts a large download. Plan for a margin, and treat any connection that cannot hold a steady upload while other traffic is running as a risk for video-heavy work.

Write down the test results, the host's answers and your backup plan before you commit. If the connection fails the test or the answers stay vague, it is reasonable to look for a different place or to budget for a coworking space as a fallback. Choosing a stay because the internet looks adequate on paper is a common mistake, and a few minutes of checking avoids it.