Looking Glass — Facturation Horaire à l’Usage
Testez la latence et la connectivité de notre réseau mondial. Utilisez les adresses IP ci-dessous pour effectuer des tests de ping et de traceroute depuis votre emplacement.
Europe
Allemagne
Nuremberg
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2a01:4f8:0:1::1e0:2Allemagne
Falkenstein
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2a01:4f8:0:a232::2Allemagne
Francfort
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2001:19f0:6c00:8082:5400:ff:fe08:638aEspagne
Madrid
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2a01:6400:2600:103:5400:3ff:fecda:9b7Finlande
Helsinki
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2a01:4f9:0:a010::20France
Paris
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2001:19f0:6800:8082:5400:ff:fe08:638aItalie
Milan
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2a05:f480:3800:10fb:5400:6ff:fe18:65c9Pays-Bas
Amsterdam
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2001:19f0:5000:8601:5400:ff:fe80:5366Pologne
Warsaw
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2a05:f480:2400:1011:5400:3ff:fec6:217bRoyaume-Uni
Londres
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2001:19f0:7400:8601:5400:ff:fe80:5357Royaume-Uni
Manchester
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2a05:f480:3400:2101:5400:4ff:fe6a:dc04Suède
Stockholm
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2a01:6458:3000:10b2:5400:3ff:fe92:ee9Turquie
Istanbul
Latence HTTPS
IPv4 de test
185.226.92.1| Pays | Ville | Latence HTTPS | IPv4 de test | IPv6 de test |
|---|---|---|---|---|
| Nuremberg | Chargement... | 2a01:4f8:0:1::1e0:2 | ||
| Falkenstein | Chargement... | 2a01:4f8:0:a232::2 | ||
| Francfort | Chargement... | 2001:19f0:6c00:8082:5400:ff:fe08:638a | ||
| Madrid | Chargement... | 2a01:6400:2600:103:5400:3ff:fecda:9b7 | ||
| Helsinki | Chargement... | 2a01:4f9:0:a010::20 | ||
| Paris | Chargement... | 2001:19f0:6800:8082:5400:ff:fe08:638a | ||
| Milan | Chargement... | 2a05:f480:3800:10fb:5400:6ff:fe18:65c9 | ||
| Amsterdam | Chargement... | 2001:19f0:5000:8601:5400:ff:fe80:5366 | ||
| Warsaw | Chargement... | 2a05:f480:2400:1011:5400:3ff:fec6:217b | ||
| Londres | Chargement... | 2001:19f0:7400:8601:5400:ff:fe80:5357 | ||
| Manchester | Chargement... | 2a05:f480:3400:2101:5400:4ff:fe6a:dc04 | ||
| Stockholm | Chargement... | 2a01:6458:3000:10b2:5400:3ff:fe92:ee9 | ||
| Istanbul | 185.226.92.1 |
Amérique
Brésil
Sao Paulo
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2001:19f0:b800:1083:5400:3ff:feb8:ea75Canada
Toronto
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2001:19f0:b001:11:5400:ff:fecb:8c50Chili
Santiago
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2001:19f0:c800:2025:5400:4ff:fe46:cfÉtats-Unis
New York
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
Chargement...
États-Unis
San Francisco
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
Chargement...
États-Unis
San Francisco
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
Chargement...
États-Unis
New Jersey
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2001:19f0:4800:405:5400:ff:fe08:5363États-Unis
Chicago
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2001:19f0:6c00:8401:5400:ff:fe80:6364États-Unis
Dallas
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2001:19f0:5400:8001:5400:ff:fe80:5362États-Unis
Seattle
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2001:19f0:8000:8001:5400:ff:fe80:5368États-Unis
Los Angeles
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2001:19f0:6000:9082:5400:ff:fe08:5365États-Unis
Atlanta
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2001:19f0:5400:8001:5400:ff:fe80:5368États-Unis
Richmond
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
Chargement...
États-Unis
Kansas City
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
Chargement...
États-Unis
Memphis
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
Chargement...
États-Unis
Miami
Latence HTTPS
IPv4 de test
104.156.244.232IPv6 de test
2001:19f0:b800:2001:5400:ff:fe01:3689États-Unis
Honolulu
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2001:19f0:c000:c06d:5400:3ff:feea:c1f8États-Unis
Silicon Valley
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2001:19f0:ac00:126:5400:ff:fe01:7cd4États-Unis
Fremont
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
Chargement...
Mexique
Mexico City
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2001:19f0:b400:101a:5400:3ff:fe99:2eb4| Pays | Ville | Latence HTTPS | IPv4 de test | IPv6 de test |
|---|---|---|---|---|
| Sao Paulo | Chargement... | 2001:19f0:b800:1083:5400:3ff:feb8:ea75 | ||
| Toronto | Chargement... | 2001:19f0:b001:11:5400:ff:fecb:8c50 | ||
| Santiago | Chargement... | 2001:19f0:c800:2025:5400:4ff:fe46:cf | ||
| New York | Chargement... | Chargement... | ||
| San Francisco | Chargement... | Chargement... | ||
| San Francisco | Chargement... | Chargement... | ||
| New Jersey | Chargement... | 2001:19f0:4800:405:5400:ff:fe08:5363 | ||
| Chicago | Chargement... | 2001:19f0:6c00:8401:5400:ff:fe80:6364 | ||
| Dallas | Chargement... | 2001:19f0:5400:8001:5400:ff:fe80:5362 | ||
| Seattle | Chargement... | 2001:19f0:8000:8001:5400:ff:fe80:5368 | ||
| Los Angeles | Chargement... | 2001:19f0:6000:9082:5400:ff:fe08:5365 | ||
| Atlanta | Chargement... | 2001:19f0:5400:8001:5400:ff:fe80:5368 | ||
| Richmond | Chargement... | Chargement... | ||
| Kansas City | Chargement... | Chargement... | ||
| Memphis | Chargement... | Chargement... | ||
| Miami | 104.156.244.232 | 2001:19f0:b800:2001:5400:ff:fe01:3689 | ||
| Honolulu | Chargement... | 2001:19f0:c000:c06d:5400:3ff:feea:c1f8 | ||
| Silicon Valley | Chargement... | 2001:19f0:ac00:126:5400:ff:fe01:7cd4 | ||
| Fremont | Chargement... | Chargement... | ||
| Mexico City | Chargement... | 2001:19f0:b400:101a:5400:3ff:fe99:2eb4 |
Asie et Océanie
Australie
Melbourne
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2401:c080:2000:1002:5400:3ff:fed8:1603Australie
Sydney
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2001:19f0:5800:8062:5400:ff:fe60:638cCorée du Sud
Seoul
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2401:c080:1c01:0:5400:2ff:febd:8065Inde
Delhi
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2401:c080:3400:290e:5400:4ff:fe9a:29aInde
Bangalore
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2401:c080:3000:2048:5400:4ff:fe1d:7185Inde
Chennai
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
Chargement...
Inde
Mumbai
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2401:c080:2600:1066:5400:3ff:fe19:3934Indonésie
Jakarta
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
Chargement...
Israël
Tel Aviv
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2a05:f480:2c00:10f7:5400:4ff:fe68:7f2bJapon
Osaka
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2401:c080:2600:2675:5400:4ff:fe48:82c7Japon
Tokyo
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2001:19f0:7001:3002:5400:ff:fe00:536dSingapour
Singapore
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2001:19f0:4400:4001:5400:ff:fe32:b7e5| Pays | Ville | Latence HTTPS | IPv4 de test | IPv6 de test |
|---|---|---|---|---|
| Melbourne | Chargement... | 2401:c080:2000:1002:5400:3ff:fed8:1603 | ||
| Sydney | Chargement... | 2001:19f0:5800:8062:5400:ff:fe60:638c | ||
| Seoul | Chargement... | 2401:c080:1c01:0:5400:2ff:febd:8065 | ||
| Delhi | Chargement... | 2401:c080:3400:290e:5400:4ff:fe9a:29a | ||
| Bangalore | Chargement... | 2401:c080:3000:2048:5400:4ff:fe1d:7185 | ||
| Chennai | Chargement... | Chargement... | ||
| Mumbai | Chargement... | 2401:c080:2600:1066:5400:3ff:fe19:3934 | ||
| Jakarta | Chargement... | Chargement... | ||
| Tel Aviv | Chargement... | 2a05:f480:2c00:10f7:5400:4ff:fe68:7f2b | ||
| Osaka | Chargement... | 2401:c080:2600:2675:5400:4ff:fe48:82c7 | ||
| Tokyo | Chargement... | 2001:19f0:7001:3002:5400:ff:fe00:536d | ||
| Singapore | Chargement... | 2001:19f0:4400:4001:5400:ff:fe32:b7e5 |
Afrique
Afrique du Sud
Johannesburg
Latence HTTPS
IPv4 de test
Chargement...
IPv6 de test
2c0f:f748:1000:2009:5400:4ff:fa3c:3ea9| Pays | Ville | Latence HTTPS | IPv4 de test | IPv6 de test |
|---|---|---|---|---|
| Johannesburg | Chargement... | 2c0f:f748:1000:2009:5400:4ff:fa3c:3ea9 |
Pourquoi les équipes choisissent cette offre Cloud VPS
Ces avis reflètent les principales raisons ici, notamment la facturation horaire, l'accès root, le stockage NVMe et le choix de la région.
Facturation horaire
Nous avons lancé la mise en scène uniquement lorsque cela était nécessaire, et la facturation horaire a rendu ce flux de travail facile à justifier.
JS
John Stinson
La configuration instantanée, l'accès root et le stockage NVMe se sont révélés pratiques dès le premier jour.
PN
Priya Nair
24 emplacements
Nous avons comparé les régions avant le lancement, et les prix ainsi que les emplacements étaient faciles à analyser.
MB
Marcus Bennett
Équipe multirégionale