We're pleased to provide you with our internal networking tools and download files; so that you can measure download speeds, check routing and latency speeds.
- 10 MB, 100 MB and 1000MB download test files for speed test
- IPv4 and IPv6 test-IP-addresses for every location
- traceroute, ping and mtr tools
- all tools available for IPv4 and IPv6
https://ae.edis.at/ :: United Arab Emirates (UAE), Dubai
https://atgrz.edis.at/ :: Graz, Austria
https://at.edis.at/ :: Vienna, Austria
https://au.edis.at/ :: Sydney, Australia
https://be.edis.at/ :: Oostkamp (Bruge), Belgium
https://bg.edis.at/ :: Sofia, Bulgaria
https://ca.edis.at/ :: Montréal, Canada
https://ch.edis.at/ :: Zurich, Switzerland
https://cl.edis.at/ :: Viña del Mar (Valparaiso) Chile
https://cz.edis.at/ :: Prague, Czech Republic
https://de.edis.at/ :: Frankfurt, Germany
https://dk.edis.at/ :: Copenhagen, Denmark
https://es.edis.at/ :: Seville, Spain
https://fr.edis.at/ :: Paris, France
https://gr.edis.at/ :: Thessaloniki, Greece
https://im.edis.at/ :: Douglas, Isle of Man
https://hk.edis.at/ :: Kwai Chung, Hong Kong
https://hr.edis.at/ :: Zagreb, Croatia
https://hu.edis.at/ :: Budapest, Hungary
https://il.edis.at/:: Tel Aviv, Israel
https://is.edis.at/:: Hafnarfjordur, Iceland
https://it.edis.at/ :: Milan, Italy
https://itpa.edis.at/ :: Palermo, Sicily (Italia)
https://jp.edis.at/:: Tokyo, Japan
https://lt.edis.at/ :: Vilnius, Lithuania
https://lv.edis.at/ :: Riga, Latvia
https://md.edis.at/ :: Chisinau, Moldova
https://mk.edis.at/ :: Skopje, North Macedonia
https://nl.edis.at/ :: Schiphol Rijk / Amsterdam, Netherlands
https://no.edis.at/ :: Oslo, Norway
https://pl.edis.at/ :: Warsaw, Poland
https://rs.edis.at/ :: Belgrade, Serbia
https://ro.edis.at/ :: Bucharest, Romania
https://ru.edis.at/ :: Moscow, Russian Federation
https://rusp.edis.at/ :: St. Petersburg, Russian Federation
https://se.edis.at/ :: Stockholm, Sweden
https://sg.edis.at/ :: Singapore, Singapore
https://si.edis.at/ :: Ljubljana, Slovenia
https://uk.edis.at/ :: London, United Kingdom
https://us.edis.at/ :: New York, USA
We regularly check our IP ranges against the MaxMind GeoIP databases. You can check our IP ranges at any time using MaxMind GeoIP for correct assignment to the physical address of the data center. EDIS is in regular contact with MaxMind to ensure the correct capture of newly routed IP networks. Updates are published by MaxMind on Tuesdays.
The WHOIS service from RIPE is also available for review under the address RIPE NCC lookup. Please note that free databases mostly work with orphaned data sets and therefore it is not recommended to use them. MaxMind GeoIP services, as well as the WHOIS databases of the IP address registries (AfriNIC, APNIC, ARIN, LACNIC and RIPE NCC) are therefore to be regarded as authoritative.
traceroute tracks the route packets take across an IP network on their way to a given host. It utilizes the IP protocol’s time to live (TTL) field and attempts to elicit an ICMP TIME_EXCEEDED response from each gateway along the path to the host.
IPv4 - ping
ping uses the ICMP protocol’s mandatory ECHO_REQUEST datagram to elicit an ICMP ECHO_RESPONSE from a host or gateway. ECHO_REQUEST datagrams (‘‘pings’’) have an IP and ICMP header, followed by a struct timeval and then an arbitrary number of ‘‘pad’’ bytes used to fill out the packet.
IPv6 - traceroute6
traceroute6 tracks the route packets take across an IP network on their way to a given host. It utilizes the IP protocol’s time to live (TTL) field and attempts to elicit an ICMP TIME_EXCEEDED response from each gateway along the path to the host.
ping6 uses the ICMP protocol’s mandatory ECHO_REQUEST datagram to elicit an ICMP ECHO_RESPONSE from a host or gateway. ECHO_REQUEST datagrams (‘‘pings’’) have an IP and ICMP header, followed by a struct timeval and then an arbitrary number of ‘‘pad’’ bytes used to fill out the packet.
IPv4 mtr / IPv6 mtr6
mtr / mtr6 combines the functionality of the traceroute/traceroute6 and ping/ping6 programs in a single network diagnostic tool. As mtr / mtr6 starts, it investigates the network connection between the host mtr / mtr6 runs on and the HOSTNAME by sending packets with purposly low TTLs. It continues to send packets with low TTL, noting the response time of the intervening routers. This allows mtr / mtr6 to print the response percentage and response times of the internet route to HOSTNAME. A sudden increase in packetloss or response time is often an indication of a bad (or simply overloaded) link.