You are connected via IPv4 from 185.104.194.44
To force the usage of IPv6, visit Speedtest6.Tele2.NET.
To force the usage of IPv4, visit Speedtest4.Tele2.NET.
The Tele2 Speedtest Service helps you test your Internet connection speed through various methods and is available not only to customers of Tele2 but anyone with an Internet connection. Test your connection using speedtest.net's tool, downloading a file via your web browser (HTTP) or downloading and uploading via FTP.
Speedtest is run on a number of fast servers in locations throughout Europe connected to Tele2's international IP core network with 10GE. The address http://speedtest.tele2.net is anycasted, meaning that you should automatically be served by the server closest (network wise) to your location. Read more about the technical details of this service.
You are currently being served by xxx-SPEEDTEST-1 located in City, Country.
We provide a variety of testfiles with different sizes, for your convenience.
1MB
10MB
100MB
1GB
10GB
50GB
100GB
1000GB
md5sum
sha1sum
These are sparsefiles and so although they appear to be on disk, they are not limited by disk speed but rather by CPU. The Speedtest servers are able to sustain close to 10 Gbps (~1GByte/s) of throughput. See the technical details to learn more about sparse files and the setup of the Tele2 Speedtest service.
To download on a Unix like system, try wget -O /dev/null http://speedtest.tele2.net/10GB.zip
After some requests we have also added the possibility to upload data using HTTP:
$ curl -T 20MB.zip http://speedtest.tele2.net/upload.php -O /dev/null
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 20.0M 0 192 100 20.0M 3941 410M --:--:-- --:--:-- --:--:-- 416MIn addition to the files offered here via HTTP, there is also an FTP server setup to serve files, you'll reach it at ftp://speedtest.tele2.net. You can upload files to /upload. Uploaded files will be automatically removed as soon as the upload is complete.
speedtest.net is an easy to use web-based (Flash) test to test both upload and download speeds as well as latency to any of a long list of servers around the world. Tele2 Speedtest servers runs a speedtest.net server. Go to speedtest.net to test your connection. This server (xxx-SPEEDTEST-1) will automatically be picked for you. After the test you can choose a another server and location to perform further testing.
The Tele2 Speedtest service is distributed over multiple machines spread across locations in Europe. By going to http://speedtest.tele2.net you will always end up on the closest location (network-wise) to you. You can specifically select another test node from the below list if you want to perform tests towards a particular location.
Once the user is connected, the next critical node is Do applications or desktops fail to enumerate (appear)? A "Yes" here forces a specific sub-flowchart: check that the user is assigned to the correct Delivery Group, verify that the Citrix Delivery Controller (DDC) services are running, and confirm that the Citrix Broker Service can communicate with the site database. Conversely, if enumeration succeeds but launching a specific resource fails, the flowchart must branch toward ICA (Independent Computing Architecture) file processing —checking the Citrix policy that governs client drive mapping, printer redirection, or clipboard access, as corrupted ICA files often contain invalid display settings.
In the modern enterprise, Citrix technologies serve as the backbone for remote access, virtual apps, and desktop delivery. However, the inherent complexity of a Citrix environment—spanning hypervisors, delivery controllers, gateways, and endpoint clients—means that when failures occur, they can be daunting to diagnose. Without a structured approach, administrators often fall into the trap of random configuration tweaks, leading to prolonged downtime. To combat this, a well-constructed Citrix Troubleshooting Flowchart is not merely a diagram; it is an essential cognitive tool that enforces logic, reduces mean time to resolution (MTTR), and transforms chaos into clarity. citrix troubleshooting flowchart
A Citrix troubleshooting flowchart is far more than a pretty diagram on a wall. It is a manifestation of expert heuristic knowledge, transformed into a repeatable, teachable process. By forcing the technician to follow the logical sequence of the user’s session—from network to authentication, enumeration, launch, and finally performance—the flowchart eliminates guesswork and reduces cognitive load. In a world where every minute of downtime costs revenue and reputation, deploying this structured methodology is not optional; it is the hallmark of a mature, resilient IT operations team. When the next "Citrix is down" alert arrives, reaching for the flowchart is the first—and most critical—step toward a swift resolution. Once the user is connected, the next critical
Perhaps the most common point of failure is the launch node: Does the VDA fail to register or time out? The flowchart here demands a decisive binary check. First, is the VDA powered on? If yes, then the next node asks: Can the DDC ping the VDA’s hostname? If DNS resolution fails, the flowchart loops to a DNS health check. If ping succeeds, the administrator is directed to verify the VDA registration port (port 80 for legacy or 443 for TLS) and the ListOfDDCs registry key on the VDA itself. This systematic elimination of possibilities—network, name resolution, then registration—exemplifies the flowchart’s power to prevent emotional, haphazard troubleshooting. In the modern enterprise, Citrix technologies serve as
If you are interested in performing more in-depth studies and high-performance measurements, please contact mnss.ems@tele2.com directly.