ping/pl :(
-
- Model
- Prispevkov: 271
- Pridružen: 20. Mar 2006 ob 14:50
- T-2: Še nimam
- Paket: 10/2
- Kraj: Jesenice
Re: ping/pl :(
Dragi Pinki, na 60%+ tujih serverjev imamo čez 50ms pinga (routing preko Azerbejđana), in na T-2 niso že par mesecev pomislili, da bi to "napako" odpravili, kaj šele, da bi jo probali odpravit. Tako, da se to neda znižat z nobenim menjanem profila.
- Malkec
- T-2jevec / Moderator
- Prispevkov: 3073
- Pridružen: 17. Mar 2006 ob 14:24
- T-2: Že imam
- Paket: T4 TERA 100/20 FTTH
- Kraj: Maribor
Re: ping/pl :(
Problem je v celotnem naboru 85.131 ipjev.
-
- Faca
- Prispevkov: 195
- Pridružen: 9. Jan 2008 ob 11:07
- T-2: Že imam
- Paket: FTTH 10/10 + 2 IPTV + 2 TEL
- Kraj: Lj - Fužine
Re: ping/pl :(
Fix it!!!
-
- Model
- Prispevkov: 271
- Pridružen: 20. Mar 2006 ob 14:50
- T-2: Še nimam
- Paket: 10/2
- Kraj: Jesenice
Re: ping/pl :(
62.75.218.159 powered by TheBigKMalkec napisal/-a:Problem je v celotnem naboru 85.131 ipjev.
85.114.153.4
78.143.13.24 Linemax.de
82.149.235.98 ckras
Ni problem samo v 85.131 (čeprav se večina nemških serverjev začne na ta IP) ampak tudi drugje. Bom sproti pisal IPje na katerih je visok ping, zdaj se mi neda iskat.
- Malkec
- T-2jevec / Moderator
- Prispevkov: 3073
- Pridružen: 17. Mar 2006 ob 14:24
- T-2: Že imam
- Paket: T4 TERA 100/20 FTTH
- Kraj: Maribor
Re: ping/pl :(
PING 62.75.218.159 (62.75.218.159) 56(84) bytes of data.
64 bytes from 62.75.218.159: icmp_seq=1 ttl=48 time=36.4 ms
64 bytes from 62.75.218.159: icmp_seq=2 ttl=48 time=36.3 ms
64 bytes from 62.75.218.159: icmp_seq=3 ttl=48 time=36.3 ms
PING 85.114.153.4 (85.114.153.4) 56(84) bytes of data.
64 bytes from 85.114.153.4: icmp_seq=1 ttl=54 time=27.2 ms
64 bytes from 85.114.153.4: icmp_seq=2 ttl=54 time=27.2 ms
64 bytes from 85.114.153.4: icmp_seq=3 ttl=54 time=27.1 ms
PING 78.143.13.24 (78.143.13.24) 56(84) bytes of data.
64 bytes from 78.143.13.24: icmp_seq=1 ttl=49 time=37.2 ms
64 bytes from 78.143.13.24: icmp_seq=2 ttl=49 time=37.3 ms
64 bytes from 78.143.13.24: icmp_seq=3 ttl=49 time=37.0 ms
PING 82.149.235.98 (82.149.235.98) 56(84) bytes of data.
64 bytes from 82.149.235.98: icmp_seq=3 ttl=55 time=22.5 ms
64 bytes from 82.149.235.98: icmp_seq=4 ttl=55 time=20.6 ms
64 bytes from 82.149.235.98: icmp_seq=5 ttl=55 time=19.9 ms
To je direkt iz omrežja.
64 bytes from 62.75.218.159: icmp_seq=1 ttl=48 time=36.4 ms
64 bytes from 62.75.218.159: icmp_seq=2 ttl=48 time=36.3 ms
64 bytes from 62.75.218.159: icmp_seq=3 ttl=48 time=36.3 ms
PING 85.114.153.4 (85.114.153.4) 56(84) bytes of data.
64 bytes from 85.114.153.4: icmp_seq=1 ttl=54 time=27.2 ms
64 bytes from 85.114.153.4: icmp_seq=2 ttl=54 time=27.2 ms
64 bytes from 85.114.153.4: icmp_seq=3 ttl=54 time=27.1 ms
PING 78.143.13.24 (78.143.13.24) 56(84) bytes of data.
64 bytes from 78.143.13.24: icmp_seq=1 ttl=49 time=37.2 ms
64 bytes from 78.143.13.24: icmp_seq=2 ttl=49 time=37.3 ms
64 bytes from 78.143.13.24: icmp_seq=3 ttl=49 time=37.0 ms
PING 82.149.235.98 (82.149.235.98) 56(84) bytes of data.
64 bytes from 82.149.235.98: icmp_seq=3 ttl=55 time=22.5 ms
64 bytes from 82.149.235.98: icmp_seq=4 ttl=55 time=20.6 ms
64 bytes from 82.149.235.98: icmp_seq=5 ttl=55 time=19.9 ms
To je direkt iz omrežja.
-
- Model
- Prispevkov: 271
- Pridružen: 20. Mar 2006 ob 14:50
- T-2: Še nimam
- Paket: 10/2
- Kraj: Jesenice
Re: ping/pl :(
Pinging 62.75.218.159 with 32 bytes of data:
Reply from 62.75.218.159: bytes=32 time=46ms TTL=46
Reply from 62.75.218.159: bytes=32 time=46ms TTL=46
Reply from 62.75.218.159: bytes=32 time=45ms TTL=46
Reply from 62.75.218.159: bytes=32 time=46ms TTL=46
Pinging 78.143.13.24 with 32 bytes of data:
Reply from 78.143.13.24: bytes=32 time=47ms TTL=47
Reply from 78.143.13.24: bytes=32 time=46ms TTL=47
Reply from 78.143.13.24: bytes=32 time=46ms TTL=47
Reply from 78.143.13.24: bytes=32 time=46ms TTL=47
Pinging 82.149.235.98 with 32 bytes of data:
Reply from 82.149.235.98: bytes=32 time=58ms TTL=52
Reply from 82.149.235.98: bytes=32 time=40ms TTL=52
Reply from 82.149.235.98: bytes=32 time=65ms TTL=52
Reply from 82.149.235.98: bytes=32 time=44ms TTL=52
To je direkt iz moje mašine, kar je važno. Prihaja zelo pomemben čas za slovenske gamerje in mislim, da si T-2 "nesme" privoščit tega sranja, kot ga gledamo zadnjih par mesecev. http://www.eswc.com/slovenia/main.php
Reply from 62.75.218.159: bytes=32 time=46ms TTL=46
Reply from 62.75.218.159: bytes=32 time=46ms TTL=46
Reply from 62.75.218.159: bytes=32 time=45ms TTL=46
Reply from 62.75.218.159: bytes=32 time=46ms TTL=46
Pinging 78.143.13.24 with 32 bytes of data:
Reply from 78.143.13.24: bytes=32 time=47ms TTL=47
Reply from 78.143.13.24: bytes=32 time=46ms TTL=47
Reply from 78.143.13.24: bytes=32 time=46ms TTL=47
Reply from 78.143.13.24: bytes=32 time=46ms TTL=47
Pinging 82.149.235.98 with 32 bytes of data:
Reply from 82.149.235.98: bytes=32 time=58ms TTL=52
Reply from 82.149.235.98: bytes=32 time=40ms TTL=52
Reply from 82.149.235.98: bytes=32 time=65ms TTL=52
Reply from 82.149.235.98: bytes=32 time=44ms TTL=52
To je direkt iz moje mašine, kar je važno. Prihaja zelo pomemben čas za slovenske gamerje in mislim, da si T-2 "nesme" privoščit tega sranja, kot ga gledamo zadnjih par mesecev. http://www.eswc.com/slovenia/main.php
-
- Faca
- Prispevkov: 195
- Pridružen: 9. Jan 2008 ob 11:07
- T-2: Že imam
- Paket: FTTH 10/10 + 2 IPTV + 2 TEL
- Kraj: Lj - Fužine
Re: ping/pl :(
Zmanjšal se mi je ping za 20ms. Nice, prej 60, zdaj 40. Le tako naprej.Malkec napisal/-a:Problem je v celotnem naboru 85.131 ipjev.
- iElectric
- Model
- Prispevkov: 214
- Pridružen: 3. Apr 2006 ob 22:39
- T-2: Že imam
- Paket: 20/20mbit
- Kraj: Ljubljana
- Kontakt:
Re: ping/pl :(
Se še komu zadnje par dni dogaja, da ima slovenija obupne pinga (tujina pa ne in ja, dejansko je mogoče)
Koda: Izberi vse
PING www.l.google.com (209.85.135.147) 56(84) bytes of data.
64 bytes from mu-in-f147.google.com (209.85.135.147): icmp_seq=1 ttl=238 time=58.0 ms
64 bytes from mu-in-f147.google.com (209.85.135.147): icmp_seq=2 ttl=238 time=57.0 ms
64 bytes from mu-in-f147.google.com (209.85.135.147): icmp_seq=3 ttl=238 time=54.2 ms
64 bytes from mu-in-f147.google.com (209.85.135.147): icmp_seq=4 ttl=238 time=56.5 ms
64 bytes from mu-in-f147.google.com (209.85.135.147): icmp_seq=5 ttl=238 time=55.4 ms
64 bytes from mu-in-f147.google.com (209.85.135.147): icmp_seq=6 ttl=238 time=53.9 ms
64 bytes from mu-in-f147.google.com (209.85.135.147): icmp_seq=7 ttl=238 time=54.6 ms
64 bytes from mu-in-f147.google.com (209.85.135.147): icmp_seq=8 ttl=238 time=55.4 ms
64 bytes from mu-in-f147.google.com (209.85.135.147): icmp_seq=9 ttl=238 time=60.6 ms
64 bytes from mu-in-f147.google.com (209.85.135.147): icmp_seq=10 ttl=238 time=55.2 ms
64 bytes from mu-in-f147.google.com (209.85.135.147): icmp_seq=11 ttl=238 time=66.3 ms
64 bytes from mu-in-f147.google.com (209.85.135.147): icmp_seq=12 ttl=238 time=54.8 ms
^C
--- www.l.google.com ping statistics ---
12 packets transmitted, 12 received, 0% packet loss, time 11004ms
rtt min/avg/max/mdev = 53.947/56.877/66.354/3.372 ms
Koda: Izberi vse
PING siol.net (89.143.249.33) 56(84) bytes of data.
64 bytes from 89.143.249.33: icmp_seq=1 ttl=121 time=15.4 ms
64 bytes from 89.143.249.33: icmp_seq=2 ttl=121 time=279 ms
64 bytes from 89.143.249.33: icmp_seq=3 ttl=121 time=268 ms
64 bytes from 89.143.249.33: icmp_seq=4 ttl=121 time=96.2 ms
64 bytes from 89.143.249.33: icmp_seq=5 ttl=121 time=15.7 ms
64 bytes from 89.143.249.33: icmp_seq=6 ttl=121 time=15.0 ms
64 bytes from 89.143.249.33: icmp_seq=7 ttl=121 time=15.3 ms
64 bytes from 89.143.249.33: icmp_seq=8 ttl=121 time=56.1 ms
64 bytes from 89.143.249.33: icmp_seq=9 ttl=121 time=22.5 ms
64 bytes from 89.143.249.33: icmp_seq=10 ttl=121 time=83.2 ms
64 bytes from 89.143.249.33: icmp_seq=11 ttl=121 time=15.2 ms
64 bytes from 89.143.249.33: icmp_seq=12 ttl=121 time=168 ms
64 bytes from 89.143.249.33: icmp_seq=13 ttl=121 time=28.1 ms
64 bytes from 89.143.249.33: icmp_seq=14 ttl=121 time=143 ms
64 bytes from 89.143.249.33: icmp_seq=15 ttl=121 time=51.6 ms
64 bytes from 89.143.249.33: icmp_seq=16 ttl=121 time=104 ms
64 bytes from 89.143.249.33: icmp_seq=17 ttl=121 time=91.0 ms
64 bytes from 89.143.249.33: icmp_seq=18 ttl=121 time=168 ms
64 bytes from 89.143.249.33: icmp_seq=19 ttl=121 time=16.2 ms
64 bytes from 89.143.249.33: icmp_seq=20 ttl=121 time=175 ms
64 bytes from 89.143.249.33: icmp_seq=21 ttl=121 time=26.9 ms
64 bytes from 89.143.249.33: icmp_seq=22 ttl=121 time=15.1 ms
64 bytes from 89.143.249.33: icmp_seq=23 ttl=121 time=99.2 ms
64 bytes from 89.143.249.33: icmp_seq=24 ttl=121 time=16.6 ms
64 bytes from 89.143.249.33: icmp_seq=25 ttl=121 time=15.0 ms
64 bytes from 89.143.249.33: icmp_seq=26 ttl=121 time=15.6 ms
64 bytes from 89.143.249.33: icmp_seq=27 ttl=121 time=15.1 ms
64 bytes from 89.143.249.33: icmp_seq=28 ttl=121 time=14.7 ms
64 bytes from 89.143.249.33: icmp_seq=29 ttl=121 time=14.5 ms
64 bytes from 89.143.249.33: icmp_seq=30 ttl=121 time=407 ms
64 bytes from 89.143.249.33: icmp_seq=31 ttl=121 time=15.3 ms
64 bytes from 89.143.249.33: icmp_seq=32 ttl=121 time=15.0 ms
64 bytes from 89.143.249.33: icmp_seq=34 ttl=121 time=35.6 ms
64 bytes from 89.143.249.33: icmp_seq=35 ttl=121 time=190 ms
64 bytes from 89.143.249.33: icmp_seq=36 ttl=121 time=16.9 ms
64 bytes from 89.143.249.33: icmp_seq=37 ttl=121 time=176 ms
64 bytes from 89.143.249.33: icmp_seq=38 ttl=121 time=53.4 ms
--- siol.net ping statistics ---
38 packets transmitted, 37 received, 2% packet loss, time 37000ms
rtt min/avg/max/mdev = 14.515/80.397/407.824/92.115 ms
Koda: Izberi vse
PING t-2.net (89.218.114.78) 56(84) bytes of data.
64 bytes from 89.218.114.78: icmp_seq=1 ttl=48 time=172 ms
64 bytes from 89.218.114.78: icmp_seq=2 ttl=48 time=254 ms
64 bytes from 89.218.114.78: icmp_seq=3 ttl=48 time=170 ms
64 bytes from 89.218.114.78: icmp_seq=4 ttl=48 time=197 ms
64 bytes from 89.218.114.78: icmp_seq=5 ttl=48 time=216 ms
64 bytes from 89.218.114.78: icmp_seq=6 ttl=48 time=478 ms
64 bytes from 89.218.114.78: icmp_seq=7 ttl=48 time=240 ms
64 bytes from 89.218.114.78: icmp_seq=8 ttl=48 time=296 ms
64 bytes from 89.218.114.78: icmp_seq=9 ttl=48 time=291 ms
64 bytes from 89.218.114.78: icmp_seq=10 ttl=48 time=557 ms
64 bytes from 89.218.114.78: icmp_seq=11 ttl=48 time=296 ms
64 bytes from 89.218.114.78: icmp_seq=12 ttl=48 time=180 ms
64 bytes from 89.218.114.78: icmp_seq=13 ttl=48 time=287 ms
64 bytes from 89.218.114.78: icmp_seq=14 ttl=48 time=524 ms
64 bytes from 89.218.114.78: icmp_seq=15 ttl=48 time=276 ms
64 bytes from 89.218.114.78: icmp_seq=16 ttl=48 time=279 ms
64 bytes from 89.218.114.78: icmp_seq=17 ttl=48 time=172 ms
64 bytes from 89.218.114.78: icmp_seq=18 ttl=48 time=194 ms
64 bytes from 89.218.114.78: icmp_seq=19 ttl=48 time=171 ms
64 bytes from 89.218.114.78: icmp_seq=20 ttl=48 time=171 ms
64 bytes from 89.218.114.78: icmp_seq=21 ttl=48 time=264 ms
64 bytes from 89.218.114.78: icmp_seq=22 ttl=48 time=193 ms
64 bytes from 89.218.114.78: icmp_seq=23 ttl=48 time=226 ms
^C
--- t-2.net ping statistics ---
24 packets transmitted, 23 received, 4% packet loss, time 23018ms
rtt min/avg/max/mdev = 170.312/265.859/557.414/108.752 ms
-
- Model
- Prispevkov: 271
- Pridružen: 20. Mar 2006 ob 14:50
- T-2: Še nimam
- Paket: 10/2
- Kraj: Jesenice
Re: ping/pl :(
Pri meni dela zadnji dni odlično! Nemogoče, a mogoče. Na vseh nemških imam -28ms, na slovenskih 6,7. In ja, po dolgem času so se malo zmrdali glede routinga.iElectric napisal/-a:Se še komu zadnje par dni dogaja, da ima slovenija obupne pinga (tujina pa ne in ja, dejansko je mogoče)
Re: ping/pl :(
Malo preglej računalnik za viruse in vohunske programe, namreč t-2.net ti resolva v IP 89.218.114.78, ki pripada "JSC Kazakhtelecom, Karaganda Affiliate, Kazakhstan".iElectric napisal/-a:Se še komu zadnje par dni dogaja, da ima slovenija obupne pinga (tujina pa ne in ja, dejansko je mogoče)
IP za "t-2.net" sicer v DNS-u ne obstaja, tako da moraš pingati naprimer "mail.t-2.net". In dodaj še traceroute, ker ping ne pove kar dosti o tem, kje so težave.
- Malkec
- T-2jevec / Moderator
- Prispevkov: 3073
- Pridružen: 17. Mar 2006 ob 14:24
- T-2: Že imam
- Paket: T4 TERA 100/20 FTTH
- Kraj: Maribor
Re: ping/pl :(
Prisežem da nisem mel nič pri tembLADEK napisal/-a:Pri meni dela zadnji dni odlično! Nemogoče, a mogoče. Na vseh nemških imam -28ms, na slovenskih 6,7. In ja, po dolgem času so se malo zmrdali glede routinga.iElectric napisal/-a:Se še komu zadnje par dni dogaja, da ima slovenija obupne pinga (tujina pa ne in ja, dejansko je mogoče)
- iElectric
- Model
- Prispevkov: 214
- Pridružen: 3. Apr 2006 ob 22:39
- T-2: Že imam
- Paket: 20/20mbit
- Kraj: Ljubljana
- Kontakt:
Re: ping/pl :(
Iz treh različnih mašin (z različnimi OS) je ping isti. NI noben problem v PCjih. Enostavno se paketki zgubijo nekje na polju. Dokler nisem bil odklopljen in še enkrat prikljopljen je vse delalo vredu Zdaj pa sem vrjetno na kakšnem crap-ass profilu:(
Koda: Izberi vse
[11:02:25]ielectric@irisis > ping mail.t-2.net
PING mail.t-2.net (84.255.209.71) 56(84) bytes of data.
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=1 ttl=251 time=409 ms
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=2 ttl=251 time=132 ms
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=3 ttl=251 time=215 ms
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=4 ttl=251 time=15.9 ms
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=5 ttl=251 time=15.8 ms
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=6 ttl=251 time=15.0 ms
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=7 ttl=251 time=15.2 ms
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=8 ttl=251 time=118 ms
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=9 ttl=251 time=15.6 ms
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=11 ttl=251 time=19.4 ms
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=12 ttl=251 time=14.8 ms
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=13 ttl=251 time=15.0 ms
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=14 ttl=251 time=15.3 ms
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=15 ttl=251 time=15.1 ms
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=16 ttl=251 time=15.1 ms
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=17 ttl=251 time=14.9 ms
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=18 ttl=251 time=17.6 ms
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=19 ttl=251 time=46.0 ms
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=20 ttl=251 time=16.0 ms
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=21 ttl=251 time=15.3 ms
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=22 ttl=251 time=15.3 ms
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=23 ttl=251 time=70.9 ms
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=24 ttl=251 time=15.2 ms
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=25 ttl=251 time=14.8 ms
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=26 ttl=251 time=15.0 ms
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=27 ttl=251 time=14.6 ms
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=28 ttl=251 time=15.1 ms
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=29 ttl=251 time=15.9 ms
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=30 ttl=251 time=28.1 ms
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=31 ttl=251 time=15.5 ms
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=32 ttl=251 time=15.1 ms
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=33 ttl=251 time=18.1 ms
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=34 ttl=251 time=16.3 ms
64 bytes from md2.t-2.net (84.255.209.71): icmp_seq=35 ttl=251 time=15.0 ms
^C
--- mail.t-2.net ping statistics ---
35 packets transmitted, 34 received, 2% packet loss, time 38041ms
rtt min/avg/max/mdev = 14.631/42.472/409.494/76.514 ms
Koda: Izberi vse
[11:03:11]ielectric@irisis > traceroute mail.t-2.net
traceroute to mail.t-2.net (84.255.209.71), 30 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 2.111 ms 2.620 ms 4.899 ms
2 89-212-0-1.gw.t-2.net (89.212.0.1) 18.298 ms 21.412 ms 22.549 ms
3 * * *
4 * * *
5 * * *
...
-
- Model
- Prispevkov: 271
- Pridružen: 20. Mar 2006 ob 14:50
- T-2: Še nimam
- Paket: 10/2
- Kraj: Jesenice
Re: ping/pl :(
Stavim svoja jajca, da imaš ti uklopljen kakšen utorrent ali katerkoli p2p program. Primer: liveTV programi (Sopcast, TVU, TVAnts,...) zabijajo bandwidth tudi ko nič ne gledaš. Moraš ga killat v taskmanagerju, da se popolnoma ustavi.
Malkec: lažeš?
Malkec: lažeš?
-
- Model
- Prispevkov: 271
- Pridružen: 20. Mar 2006 ob 14:50
- T-2: Še nimam
- Paket: 10/2
- Kraj: Jesenice
Re: ping/pl :(
Pinging ckras.de [82.149.232.51] with 32 bytes of data:
Reply from 82.149.232.51: bytes=32 time=74ms TTL=52
Reply from 82.149.232.51: bytes=32 time=76ms TTL=52
Reply from 82.149.232.51: bytes=32 time=76ms TTL=52
Reply from 82.149.232.51: bytes=32 time=27ms TTL=52
Reply from 82.149.232.51: bytes=32 time=27ms TTL=52
Reply from 82.149.232.51: bytes=32 time=72ms TTL=52
Reply from 82.149.232.51: bytes=32 time=26ms TTL=52
Reply from 82.149.232.51: bytes=32 time=36ms TTL=52
Reply from 82.149.232.51: bytes=32 time=36ms TTL=52
Reply from 82.149.232.51: bytes=32 time=38ms TTL=52
Reply from 82.149.232.51: bytes=32 time=80ms TTL=52
Reply from 82.149.232.51: bytes=32 time=33ms TTL=52
Reply from 82.149.232.51: bytes=32 time=75ms TTL=52
Ping statistics for 82.149.232.51:
Packets: Sent = 13, Received = 13, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 80ms, Average = 52ms
Pinging 77.111.225.139 with 32 bytes of data:
Reply from 77.111.225.139: bytes=32 time=44ms TTL=53
Reply from 77.111.225.139: bytes=32 time=63ms TTL=53
Reply from 77.111.225.139: bytes=32 time=37ms TTL=53
Reply from 77.111.225.139: bytes=32 time=35ms TTL=53
Ping statistics for 77.111.225.139:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 63ms, Average = 44ms
Reply from 82.149.232.51: bytes=32 time=74ms TTL=52
Reply from 82.149.232.51: bytes=32 time=76ms TTL=52
Reply from 82.149.232.51: bytes=32 time=76ms TTL=52
Reply from 82.149.232.51: bytes=32 time=27ms TTL=52
Reply from 82.149.232.51: bytes=32 time=27ms TTL=52
Reply from 82.149.232.51: bytes=32 time=72ms TTL=52
Reply from 82.149.232.51: bytes=32 time=26ms TTL=52
Reply from 82.149.232.51: bytes=32 time=36ms TTL=52
Reply from 82.149.232.51: bytes=32 time=36ms TTL=52
Reply from 82.149.232.51: bytes=32 time=38ms TTL=52
Reply from 82.149.232.51: bytes=32 time=80ms TTL=52
Reply from 82.149.232.51: bytes=32 time=33ms TTL=52
Reply from 82.149.232.51: bytes=32 time=75ms TTL=52
Ping statistics for 82.149.232.51:
Packets: Sent = 13, Received = 13, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 80ms, Average = 52ms
Pinging 77.111.225.139 with 32 bytes of data:
Reply from 77.111.225.139: bytes=32 time=44ms TTL=53
Reply from 77.111.225.139: bytes=32 time=63ms TTL=53
Reply from 77.111.225.139: bytes=32 time=37ms TTL=53
Reply from 77.111.225.139: bytes=32 time=35ms TTL=53
Ping statistics for 77.111.225.139:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 63ms, Average = 44ms