Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie

ISP for gaming

  • 14-07-2005 11:23am
    #1
    TerrorFirmer
    Closed Accounts Posts: 29,930 ✭✭✭✭


    Right, I have one basic question : what is the best provider for gaming?

    I'm currently using Esat BT home, 512/128 (even though they said they give us 1000/128), and my ping is normally between 90-200. I'm always hearing of peoples pings being 20-50 on BF2 and other games, and quite frankly I need something like it.

    Thanks


Comments

  • #2
    -Al-
    Registered Users Posts: 705 ✭✭✭-Al-


    Im on BTs iolbb+ 2048/128 and I get pings of about 28-35 on irish BF2 servers. Ive never had problems in any other games either, UK servers I get about 40-50 but thats still playable.


  • #3
    CyberGhost
    Registered Users, Registered Users 2 Posts: 5,554 ✭✭✭CyberGhost


    IMHO eircom is the best


  • #4
    Sponge Bob
    Banned (with Prison Access) Posts: 25,234 ✭✭✭✭Sponge Bob


    Hows this 17Ms .
    C:\ping www.jolt.co.uk -t

Pinging www.jolt.co.uk [82.133.85.65] with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=17ms TTL=55
Reply from 82.133.85.65: bytes=32 time=17ms TTL=55
Reply from 82.133.85.65: bytes=32 time=17ms TTL=55
Reply from 82.133.85.65: bytes=32 time=17ms TTL=55
Reply from 82.133.85.65: bytes=32 time=17ms TTL=55
Reply from 82.133.85.65: bytes=32 time=17ms TTL=55
Reply from 82.133.85.65: bytes=32 time=18ms TTL=55
Reply from 82.133.85.65: bytes=32 time=17ms TTL=55
Reply from 82.133.85.65: bytes=32 time=17ms TTL=55
Reply from 82.133.85.65: bytes=32 time=17ms TTL=55
Reply from 82.133.85.65: bytes=32 time=17ms TTL=55
Reply from 82.133.85.65: bytes=32 time=17ms TTL=55
Reply from 82.133.85.65: bytes=32 time=17ms TTL=55
Reply from 82.133.85.65: bytes=32 time=17ms TTL=55
Reply from 82.133.85.65: bytes=32 time=17ms TTL=55
Reply from 82.133.85.65: bytes=32 time=17ms TTL=55
Reply from 82.133.85.65: bytes=32 time=17ms TTL=55
Reply from 82.133.85.65: bytes=32 time=17ms TTL=55
Reply from 82.133.85.65: bytes=32 time=17ms TTL=55
Reply from 82.133.85.65: bytes=32 time=17ms TTL=55
Reply from 82.133.85.65: bytes=32 time=17ms TTL=55
Reply from 82.133.85.65: bytes=32 time=25ms TTL=55
Reply from 82.133.85.65: bytes=32 time=17ms TTL=55
Reply from 82.133.85.65: bytes=32 time=17ms TTL=55
Reply from 82.133.85.65: bytes=32 time=17ms TTL=55
Reply from 82.133.85.65: bytes=32 time=17ms TTL=55
Reply from 82.133.85.65: bytes=32 time=17ms TTL=55
Reply from 82.133.85.65: bytes=32 time=20ms TTL=55
Reply from 82.133.85.65: bytes=32 time=17ms TTL=55

Ping statistics for 82.133.85.65:
	Packets: Sent = 29, Received = 29, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
	Minimum = 17ms, Maximum = 25ms, Average = 17ms


  • #5
    Cabaal
    Moderators, Technology & Internet Moderators, Regional South East Moderators Posts: 28,501 Mod ✭✭✭✭Cabaal


    Esat Business 1 MB

    ping www.jolt.co.uk
    Pinging www.jolt.co.uk [82.133.85.65] with 32 bytes of data:

    Reply from 82.133.85.65: bytes=32 time=24ms TTL=56
    Reply from 82.133.85.65: bytes=32 time=24ms TTL=56
    Reply from 82.133.85.65: bytes=32 time=24ms TTL=56
    Reply from 82.133.85.65: bytes=32 time=24ms TTL=56

    neh I'm happy enough with it ;)


  • #6
    jonski
    Registered Users, Registered Users 2 Posts: 6,394 ✭✭✭jonski


    I don't think the ISP matters that much beyond the big two , eircom and esat . Plus if you have any problems both will tell you that they don't support gaming . It's more to do with your line and distance from the exchange . If you never really got good speeds or pings on 56k , chances are you won't get them on anyones BB . If you did then it's a different story but still very hard , nigh impossible to get them to help you .


  • Advertisement
  • #7
    Gangsta
    Closed Accounts Posts: 1,603 ✭✭✭Gangsta


    I know this is a bit off topic but I tried pinging but I keep getting "request timed out". what's the deal? I can browse and everything no problem.


  • #8
    DemonOfTheFall
    Closed Accounts Posts: 2,279 ✭✭✭DemonOfTheFall


    Your modem/firewall is blocking ICMP traffic


  • #9
    TimTim
    Registered Users, Registered Users 2 Posts: 804 ✭✭✭TimTim


    Cabaal wrote:
    Esat Business 1 MB

    ping www.jolt.co.uk
    Pinging www.jolt.co.uk [82.133.85.65] with 32 bytes of data:

    Reply from 82.133.85.65: bytes=32 time=24ms TTL=56
    Reply from 82.133.85.65: bytes=32 time=24ms TTL=56
    Reply from 82.133.85.65: bytes=32 time=24ms TTL=56
    Reply from 82.133.85.65: bytes=32 time=24ms TTL=56

    neh I'm happy enough with it ;)

    I get the same on Esats Home 2Mb package. And since I'm not a hardcore gamer ping times aren't a major issue for me.

    I'd be interested in knowing who Sponge Bob is with though.


  • #10
    Sponge Bob
    Banned (with Prison Access) Posts: 25,234 ✭✭✭✭Sponge Bob


    TimTim wrote:
    I'd be interested in knowing who Sponge Bob is with though.
    Smart , over fibre .


  • #11
    the_syco
    Registered Users, Registered Users 2 Posts: 37,303 ✭✭✭✭the_syco 


    C:\>ping [url="http://www.jolt.co.uk"]www.jolt.co.uk[/url] -t

Pinging [url="http://www.jolt.co.uk"]www.jolt.co.uk[/url] [82.133.85.65] with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=17ms TTL=59
Reply from 82.133.85.65: bytes=32 time=20ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=17ms TTL=59
Reply from 82.133.85.65: bytes=32 time=20ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=17ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=17ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=20ms TTL=59
Reply from 82.133.85.65: bytes=32 time=20ms TTL=59
Reply from 82.133.85.65: bytes=32 time=20ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=20ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=20ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=17ms TTL=59
Reply from 82.133.85.65: bytes=32 time=17ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59

Ping statistics for 82.133.85.65:
	Packets: Sent = 52, Received = 52, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
	Minimum = 17ms, Maximum =  20ms, Average =  18ms
    I think I've a Eircom's 4meg Business line, or something. Dad pays for it.

    As for ping, I usually get between 10 and 15 on the IOL servers, so that does me nicely.


  • Advertisement
  • #12
    zuma
    Closed Accounts Posts: 1,685 ✭✭✭zuma


    the_syco wrote:
    C:\>ping [url="http://www.jolt.co.uk"]www.jolt.co.uk[/url] -t

Pinging [url="http://www.jolt.co.uk"]www.jolt.co.uk[/url] [82.133.85.65] with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=17ms TTL=59
Reply from 82.133.85.65: bytes=32 time=20ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=17ms TTL=59
Reply from 82.133.85.65: bytes=32 time=20ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=17ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=17ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=20ms TTL=59
Reply from 82.133.85.65: bytes=32 time=20ms TTL=59
Reply from 82.133.85.65: bytes=32 time=20ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=20ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=20ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=19ms TTL=59
Reply from 82.133.85.65: bytes=32 time=17ms TTL=59
Reply from 82.133.85.65: bytes=32 time=17ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59
Reply from 82.133.85.65: bytes=32 time=18ms TTL=59

Ping statistics for 82.133.85.65:
	Packets: Sent = 52, Received = 52, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
	Minimum = 17ms, Maximum =  20ms, Average =  18ms
    I think I've a Eircom's 4meg Business line, or something. Dad pays for it.

    As for ping, I usually get between 10 and 15 on the IOL servers, so that does me nicely.



    Daddy's good to you!


  • #13
    AdMMM
    Registered Users, Registered Users 2 Posts: 9,472 ✭✭✭AdMMM


    A ping of 90-200 is horrible for any type of broadband. You'd even expect to get ~50 with ISDN!

    It sounds like you are on the boundary for your exchange and the signal is already deteriorating by time it gets to you.


  • #14
    TerrorFirmer
    Closed Accounts Posts: 29,930 ✭✭✭✭TerrorFirmer


    |.Murderer.| wrote:
    A ping of 90-200 is horrible for any type of broadband. You'd even expect to get ~50 with ISDN!

    It sounds like you are on the boundary for your exchange and the signal is already deteriorating by time it gets to you.

    I am one mile from an exhange. My friend lives right on an exhange and still gets the same pings as me.


  • #15
    BlitzKrieg
    Registered Users, Registered Users 2 Posts: 14,698 ✭✭✭✭BlitzKrieg


    I am one mile from an exhange. My friend lives right on an exhange and still gets the same pings as me.


  • #16
    Gonzo
    Moderators, Science, Health & Environment Moderators Posts: 16,940 Mod ✭✭✭✭Gonzo


    Pinging www.jolt.co.uk [82.133.85.65] with 32 bytes of data:

    Reply from 82.133.85.65: bytes=32 time=28ms TTL=59
    Reply from 82.133.85.65: bytes=32 time=27ms TTL=59
    Reply from 82.133.85.65: bytes=32 time=35ms TTL=59
    Reply from 82.133.85.65: bytes=32 time=31ms TTL=59

    Ping statistics for 82.133.85.65:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 27ms, Maximum = 35ms, Average = 30ms

    im with eircom, there ok for gaming.


  • #17
    DrEvil
    Registered Users, Registered Users 2 Posts: 340 ✭✭DrEvil


    Pinging jolt.co.uk [82.133.85.65] with 32 bytes of data:

    Reply from 82.133.85.65: bytes=32 time=18ms TTL=57
    Reply from 82.133.85.65: bytes=32 time=15ms TTL=57
    Reply from 82.133.85.65: bytes=32 time=17ms TTL=57
    Reply from 82.133.85.65: bytes=32 time=17ms TTL=57
    Reply from 82.133.85.65: bytes=32 time=17ms TTL=57
    Reply from 82.133.85.65: bytes=32 time=16ms TTL=57
    Reply from 82.133.85.65: bytes=32 time=15ms TTL=57
    Reply from 82.133.85.65: bytes=32 time=16ms TTL=57
    Reply from 82.133.85.65: bytes=32 time=19ms TTL=57
    Reply from 82.133.85.65: bytes=32 time=15ms TTL=57
    Reply from 82.133.85.65: bytes=32 time=17ms TTL=57
    Reply from 82.133.85.65: bytes=32 time=21ms TTL=57
    Reply from 82.133.85.65: bytes=32 time=15ms TTL=57
    Reply from 82.133.85.65: bytes=32 time=16ms TTL=57
    Reply from 82.133.85.65: bytes=32 time=16ms TTL=57
    Reply from 82.133.85.65: bytes=32 time=18ms TTL=57
    Reply from 82.133.85.65: bytes=32 time=16ms TTL=57
    Reply from 82.133.85.65: bytes=32 time=20ms TTL=57
    Reply from 82.133.85.65: bytes=32 time=17ms TTL=57

    Ping statistics for 82.133.85.65:
    Packets: Sent = 19, Received = 19, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 15ms, Maximum = 21ms, Average = 16ms

    I'm using IBB :D


Advertisement