Gå til innhold
Trenger du hjelp med internett og nettverk? Still spørsmål her ×

valg av isp til gaming ?

bluemac

Av bluemac
i Internett og nettverk

Anbefalte innlegg

bluemac

bluemac

Skrevet
Skrevet (endret)

jeg er på utkikk etter ny isp som gir best ping for penge.

 

jeg bor midt i oslo gryta så jeg kan få fra de fleste isp her i byen men uten fiber gutta :cry:

 

 

jeg har hørt at bluecom har bra greier siden dem er gamle catch stemmer det?

 

så lurte på om noen av dere kunne pinge noen adresser for meg hadde vert :thumbup:

 

 

www.menara.ma

 

www.uscombine.com

 

www.vg.no

 

www.inet.co.th

 

takker for all hjelp

Endret av bluemac
Lenke til kommentar

Videoannonse

Videoannonse
Annonse
tor_bjarne

tor_bjarne

Skrevet
Skrevet (endret)

Hei, sitter på jobben så kan ikke ping'e de adressene nå (bak mange mange brannmurer)

 

 

Men hjemme har jeg da catch (bluecome ventelo) det er utmerket ping i alle spill virker det som. Counter Strike = Veldi bra ping, spesielt på catch gamer servere.

 

Word of Warcraft har god ping også :)

 

 

Så anbefaler nokk Bluecom/ventelo

Endret av tor_bjarne
Lenke til kommentar
2mmy

2mmy

Skrevet
Skrevet

Ventlo/Catch SDSL i Oslo:

 

PING www.menara.ma (212.217.121.30): 56 data bytes

64 bytes from 212.217.121.30: icmp_seq=0 ttl=113 time=72.235 ms

64 bytes from 212.217.121.30: icmp_seq=1 ttl=113 time=75.394 ms

64 bytes from 212.217.121.30: icmp_seq=2 ttl=113 time=75.207 ms

64 bytes from 212.217.121.30: icmp_seq=3 ttl=113 time=72.545 ms

64 bytes from 212.217.121.30: icmp_seq=4 ttl=113 time=72.333 ms

64 bytes from 212.217.121.30: icmp_seq=5 ttl=113 time=72.291 ms

64 bytes from 212.217.121.30: icmp_seq=6 ttl=113 time=76.349 ms

64 bytes from 212.217.121.30: icmp_seq=7 ttl=113 time=72.384 ms

64 bytes from 212.217.121.30: icmp_seq=8 ttl=113 time=75.359 ms

64 bytes from 212.217.121.30: icmp_seq=9 ttl=113 time=75.147 ms

--- www.menara.ma ping statistics ---

10 packets transmitted, 10 packets received, 0% packet loss

round-trip min/avg/max/stddev = 72.235/73.924/76.349/1.599 ms

 

PING www.uscombine.com (65.182.100.176): 56 data bytes

64 bytes from 65.182.100.176: icmp_seq=0 ttl=116 time=175.303 ms

64 bytes from 65.182.100.176: icmp_seq=1 ttl=116 time=175.264 ms

64 bytes from 65.182.100.176: icmp_seq=2 ttl=116 time=174.995 ms

64 bytes from 65.182.100.176: icmp_seq=3 ttl=116 time=174.868 ms

64 bytes from 65.182.100.176: icmp_seq=4 ttl=116 time=174.897 ms

64 bytes from 65.182.100.176: icmp_seq=5 ttl=116 time=174.930 ms

64 bytes from 65.182.100.176: icmp_seq=6 ttl=116 time=175.507 ms

64 bytes from 65.182.100.176: icmp_seq=7 ttl=116 time=174.713 ms

64 bytes from 65.182.100.176: icmp_seq=8 ttl=116 time=174.653 ms

64 bytes from 65.182.100.176: icmp_seq=9 ttl=116 time=174.721 ms

--- www.uscombine.com ping statistics ---

10 packets transmitted, 10 packets received, 0% packet loss

round-trip min/avg/max/stddev = 174.653/174.985/175.507/0.270 ms

 

PING www.vg.no (193.69.165.21): 56 data bytes

64 bytes from 193.69.165.21: icmp_seq=0 ttl=251 time=33.527 ms

64 bytes from 193.69.165.21: icmp_seq=1 ttl=251 time=5.337 ms

64 bytes from 193.69.165.21: icmp_seq=2 ttl=251 time=31.992 ms

64 bytes from 193.69.165.21: icmp_seq=3 ttl=251 time=3.408 ms

64 bytes from 193.69.165.21: icmp_seq=4 ttl=251 time=31.070 ms

64 bytes from 193.69.165.21: icmp_seq=5 ttl=251 time=1.142 ms

64 bytes from 193.69.165.21: icmp_seq=6 ttl=251 time=28.220 ms

64 bytes from 193.69.165.21: icmp_seq=7 ttl=251 time=0.818 ms

64 bytes from 193.69.165.21: icmp_seq=8 ttl=251 time=25.705 ms

64 bytes from 193.69.165.21: icmp_seq=9 ttl=251 time=0.900 ms

--- www.vg.no ping statistics ---

10 packets transmitted, 10 packets received, 0% packet loss

round-trip min/avg/max/stddev = 0.818/16.212/33.527/14.088 ms

 

PING www.inet.co.th (203.150.217.135): 56 data bytes

64 bytes from 203.150.217.135: icmp_seq=2 ttl=47 time=371.842 ms

64 bytes from 203.150.217.135: icmp_seq=3 ttl=47 time=366.748 ms

64 bytes from 203.150.217.135: icmp_seq=4 ttl=47 time=371.889 ms

64 bytes from 203.150.217.135: icmp_seq=5 ttl=47 time=372.166 ms

64 bytes from 203.150.217.135: icmp_seq=6 ttl=47 time=366.474 ms

64 bytes from 203.150.217.135: icmp_seq=8 ttl=47 time=374.044 ms

64 bytes from 203.150.217.135: icmp_seq=9 ttl=47 time=372.559 ms

--- www.inet.co.th ping statistics ---

10 packets transmitted, 7 packets received, 30% packet loss

round-trip min/avg/max/stddev = 366.474/370.817/374.044/2.749 ms

 

 

Tydeligvis noen problemer mot www.inet.co.th. Vær også obs på at ping mot www.vg.no ser ut til å treffe noe load-sharing-ting som gir variasjoner i ping-tiden. Ping mot ip-adressen går mye jevnere:

 

PING 193.69.165.21 (193.69.165.21): 56 data bytes

64 bytes from 193.69.165.21: icmp_seq=0 ttl=251 time=0.909 ms

64 bytes from 193.69.165.21: icmp_seq=1 ttl=251 time=0.699 ms

64 bytes from 193.69.165.21: icmp_seq=2 ttl=251 time=0.868 ms

64 bytes from 193.69.165.21: icmp_seq=3 ttl=251 time=0.905 ms

64 bytes from 193.69.165.21: icmp_seq=4 ttl=251 time=0.816 ms

64 bytes from 193.69.165.21: icmp_seq=5 ttl=251 time=0.858 ms

64 bytes from 193.69.165.21: icmp_seq=6 ttl=251 time=0.766 ms

64 bytes from 193.69.165.21: icmp_seq=7 ttl=251 time=0.950 ms

64 bytes from 193.69.165.21: icmp_seq=8 ttl=251 time=1.447 ms

64 bytes from 193.69.165.21: icmp_seq=9 ttl=251 time=0.908 ms

 

--- 193.69.165.21 ping statistics ---

10 packets transmitted, 10 packets received, 0% packet loss

round-trip min/avg/max/stddev = 0.699/0.913/1.447/0.192 ms

 

|2mmy|

Lenke til kommentar
Ligaya

Ligaya

Skrevet
Skrevet

Ville absolutt ikke valgt Ventelo Bluecom i disse dager. Ene skrekkhistorien etter den andre om udugelig kundeservice. De har ikke godt av å bli store. Det samme kan vel egentlig sies om NGT, ting funker normalt veldig bra, men kundeservicen er noe helt annet.Har selv NGT og synes ikke selv jeg har spesielt dårlig ping. Har ihvertfall aldri hatt noe problemer der. Dessuten er linja stabil og god, og jeg har hastigheten jeg betaler for. Skal du ha best mulig ping, så faller vel muligens valget på Telenor ? :hmm:

 

Pinging 212.217.121.30 with 32 bytes of data:

 

Reply from 212.217.121.30: bytes=32 time=81ms TTL=111

Reply from 212.217.121.30: bytes=32 time=80ms TTL=111

Reply from 212.217.121.30: bytes=32 time=79ms TTL=111

Reply from 212.217.121.30: bytes=32 time=83ms TTL=111

 

Ping statistics for 212.217.121.30:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 79ms, Maximum = 83ms, Average = 80ms

 

Pinging 65.182.100.176 with 32 bytes of data:

 

Reply from 65.182.100.176: bytes=32 time=172ms TTL=111

Reply from 65.182.100.176: bytes=32 time=167ms TTL=111

Reply from 65.182.100.176: bytes=32 time=167ms TTL=111

Reply from 65.182.100.176: bytes=32 time=167ms TTL=111

 

Ping statistics for 65.182.100.176:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 167ms, Maximum = 172ms, Average = 168ms

 

Pinging 193.69.165.21 with 32 bytes of data:

 

Reply from 193.69.165.21: bytes=32 time=7ms TTL=246

Reply from 193.69.165.21: bytes=32 time=9ms TTL=246

Reply from 193.69.165.21: bytes=32 time=9ms TTL=246

Reply from 193.69.165.21: bytes=32 time=9ms TTL=246

 

Ping statistics for 193.69.165.21:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 7ms, Maximum = 9ms, Average = 8ms

 

Den siste, www.inet.co.th fikk jeg packetloss på og over 400 i ping ... :ermm:

Lenke til kommentar
bluemac

bluemac

Skrevet
  • Forfatter
Skrevet
Ville absolutt ikke valgt Ventelo Bluecom i disse dager. Ene skrekkhistorien etter den andre om udugelig kundeservice. De har ikke godt av å bli store. Det samme kan vel egentlig sies om NGT, ting funker normalt veldig bra, men kundeservicen er noe helt annet.Har selv NGT og synes ikke selv jeg har spesielt dårlig ping. Har ihvertfall aldri hatt noe problemer der. Dessuten er linja stabil og god, og jeg har hastigheten jeg betaler for. Skal du ha best mulig ping, så faller vel muligens valget på Telenor ?  :hmm:

 

Pinging 212.217.121.30 with 32 bytes of data:

 

Reply from 212.217.121.30: bytes=32 time=81ms TTL=111

Reply from 212.217.121.30: bytes=32 time=80ms TTL=111

Reply from 212.217.121.30: bytes=32 time=79ms TTL=111

Reply from 212.217.121.30: bytes=32 time=83ms TTL=111

 

Ping statistics for 212.217.121.30:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 79ms, Maximum = 83ms, Average = 80ms

 

Pinging 65.182.100.176 with 32 bytes of data:

 

Reply from 65.182.100.176: bytes=32 time=172ms TTL=111

Reply from 65.182.100.176: bytes=32 time=167ms TTL=111

Reply from 65.182.100.176: bytes=32 time=167ms TTL=111

Reply from 65.182.100.176: bytes=32 time=167ms TTL=111

 

Ping statistics for 65.182.100.176:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 167ms, Maximum = 172ms, Average = 168ms

 

Pinging 193.69.165.21 with 32 bytes of data:

 

Reply from 193.69.165.21: bytes=32 time=7ms TTL=246

Reply from 193.69.165.21: bytes=32 time=9ms TTL=246

Reply from 193.69.165.21: bytes=32 time=9ms TTL=246

Reply from 193.69.165.21: bytes=32 time=9ms TTL=246

 

Ping statistics for 193.69.165.21:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 7ms, Maximum = 9ms, Average = 8ms

 

Den siste, www.inet.co.th fikk jeg packetloss på og over 400 i ping ... :ermm:

5960105[/snapback]

 

 

 

 

 

 

har du telenor? eller andre her som veit når telenor kommer med adsl++??

Lenke til kommentar

Opprett en konto eller logg inn for å kommentere

Du må være et medlem for å kunne skrive en kommentar

Opprett konto

Det er enkelt å melde seg inn for å starte en ny konto!

Start en konto

Logg inn

Har du allerede en konto? Logg inn her.

Logg inn nå
Gå til emneliste

  • Hvem er aktive   0 medlemmer

    • Ingen innloggede medlemmer aktive
×
×
  • Opprett ny...