32ms from Germany

Is that good or bad for you? :)

40-43, compared to multiplay (35-36) or jolt (37-38) this is not really good.

Where are you located?

munich, germany - but it seems that some routing problem is going on atm

Can you provide a traceroute please? :)

1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Zeitüberschreitung der Anforderung.
3 12 ms 13 ms 12 ms 217.0.69.150
4 * 20 ms 20 ms f-ea5.F.DE.net.DTAG.DE [62.154.16.165]
5 20 ms 19 ms 24 ms so-3-2-2.fra10.ip.tiscali.net [213.200.64.105]
6 40 ms 39 ms 39 ms xe-2-0-0.lon20.ip.tiscali.net [89.149.186.85]
7 40 ms 43 ms 40 ms rapidswitch-gw1.ip.tiscali.net [213.200.79.210]

8 * * * Zeitüberschreitung der Anforderung.
9 * * * Zeitüberschreitung der Anforderung.
10 * * * Zeitüberschreitung der Anforderung.
11 42 ms 42 ms 41 ms playaten.com [87.117.200.175]

compared to multiplay:
1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Zeitüberschreitung der Anforderung.
3 13 ms 12 ms 12 ms 217.0.69.154
4 * * 20 ms f-ea5.F.DE.net.DTAG.DE [62.154.16.165]
5 88 ms 19 ms 20 ms so-3-2-2.fra10.ip.tiscali.net [213.200.64.105]
6 38 ms 40 ms 40 ms so-1-1-0.lon11.ip.tiscali.net [213.200.82.1]
7 41 ms 37 ms 35 ms multiplay-gw-1.ip.tiscali.net [213.200.78.82]
8 36 ms 35 ms 36 ms po0-1-650-cr1.ixnlon.as35028.net [85.236.110.6]

9 37 ms 36 ms 37 ms dedicated06.multiplay.co.uk [85.236.101.77]

16~18 about normal for uk

20 ms from France on both ips, 2ms lower than jolt :)
This is on an ISP that's very popular with q3ers and other kinds of allping players.

87.117.200.175 = 38 ms
78.129.160.3 = 38

Workable, could be worse and could be better but usable :D

23
31

Mine are never too good, cable is hopeless for gaming :P

Skickar signaler till 87.117.200.175 med 32 byte data:

Svar frċn 87.117.200.175: byte=32 tid=36ms TTL=53
Svar frċn 87.117.200.175: byte=32 tid=36ms TTL=53
Svar frċn 87.117.200.175: byte=32 tid=36ms TTL=53
Svar frċn 87.117.200.175: byte=32 tid=36ms TTL=53

Skickar signaler till 78.129.160.3 med 32 byte data:

Svar frċn 78.129.160.3: byte=32 tid=36ms TTL=53
Svar frċn 78.129.160.3: byte=32 tid=36ms TTL=53
Svar frċn 78.129.160.3: byte=32 tid=36ms TTL=53
Svar frċn 78.129.160.3: byte=32 tid=36ms TTL=53

I think its fine for gaming!

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

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

Is "$20.00 use up to 32 slots per month" a good price?

£10 a month that's bang on

what do you mean by 32 slots? up to 32 players? lazery charge just under $100 for that or over $100 if you decide to have it public

Yes, you can use up to 32 public slots if you wish. It's really about CPU / memory allocation.

Said this in the other thread:

A per slot pricing scheme does not cover the cost of a game server taking up resources. The idea behind the $20 per month, use up to 32 slots, is to cover the cost of CPU/mem use per process (bandwidth is not so much an issue), and allow the customer to use up to 32 slots. Often a server using 8 slots will use just as much CPU or memory resource as a server running 32 slots, depending on the game, mod, and/or configuration being used. The $20 per month covers the cost of any type of resource usage, whether a game server is full or idling empty.

This is why we only offer the '$20 and use up to 32 slots per month' plan, plus you can add 4 private client slots so you can utilize all 32 for public use and the 4 additional private client slots for friends and administration.

:)

both 25ms

cheater connection. :<

Huh?

rofl my routing is actually changing all the time, got >30ms to german servers in the evening sometimes :/ bad isp

;/

27ms from Sweden wich I would consider really good since it's UK :)

13 and 13

both very good for me

both 35ms from germany.

ok.


p.s.:
ping.eu is telling me 17ms but he's lying for sure.

Pinging 78.129.160.3 with 32 bytes of data:
Reply from 78.129.160.3: bytes=32 time=48ms TTL=53
Reply from 78.129.160.3: bytes=32 time=49ms TTL=53
Reply from 78.129.160.3: bytes=32 time=51ms TTL=53
Reply from 78.129.160.3: bytes=32 time=47ms TTL=53
Ping statistics for 78.129.160.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 51ms, Average = 48ms

Pinging 87.117.200.175 with 32 bytes of data:
Reply from 87.117.200.175: bytes=32 time=47ms TTL=53
Reply from 87.117.200.175: bytes=32 time=52ms TTL=53
Reply from 87.117.200.175: bytes=32 time=63ms TTL=53
Reply from 87.117.200.175: bytes=32 time=62ms TTL=53
Ping statistics for 87.117.200.175:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 63ms, Average = 56ms

78.129.160.3 works better here(Eastern Europe)

both 12ms

will test when i get home (i hope its good, O2 Broadband add way to much interlacing :( 50ping to Jolt :\ )

Pinging 87.117.200.175 with 32 bytes of data:
Reply from 87.117.200.175: bytes=32 time=54ms TTL=49
Reply from 87.117.200.175: bytes=32 time=49ms TTL=49
Reply from 87.117.200.175: bytes=32 time=54ms TTL=49
Reply from 87.117.200.175: bytes=32 time=54ms TTL=49
Ping statistics for 87.117.200.175:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 49ms, Maximum = 54ms, Average = 52ms

Pinging 78.129.160.3 with 32 bytes of data:
Reply from 78.129.160.3: bytes=32 time=54ms TTL=49
Reply from 78.129.160.3: bytes=32 time=49ms TTL=49
Reply from 78.129.160.3: bytes=32 time=50ms TTL=49
Reply from 78.129.160.3: bytes=32 time=53ms TTL=49
Ping statistics for 78.129.160.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 49ms, Maximum = 54ms, Average = 51ms

lithuania \m/

Both 24-25ms which is good for me!