« previous next »
Pages: 1 ... 6 7 8 [9] 10 11 12 ... 16   Go Down

Author Topic: How is the Main Arena connection for you?  (Read 7170 times)

Offline ThunderEGG

  • Copper Member
  • **
  • Posts: 129
How is the Main Arena connection for you?
« Reply #120 on: March 02, 2006, 09:55:45 AM »
Quote
Originally posted by Skuzzy
feem is quite right.

One thing I did forget to ask about, and that is who your ISP is, and what region of the world are you located in?  Thank you all again for the help.

Also, when you say 'worse', 'better', or 'same', is that based on game play or other information?


ISP is CMC.net.  Location off the beaten path in Eastern Oregon 60 miles NW of Boise, Idaho.
Logged

Offline gatt

  • Gold Member
  • *****
  • Posts: 2441
How is the Main Arena connection for you?
« Reply #121 on: March 02, 2006, 10:30:02 AM »
ISP: Telecom Italia, Milan, Italy
ADSL
Before: 171ms, After: 171ms
Logged
"And one of the finest aircraft I ever flew was the Macchi C.205. Oh, beautiful. And here you had the perfect combination of italian styling and german engineering .... it really was a delight to fly ... and we did tests on it and were most impressed." - Captain Eric Brown

Offline FiLtH

  • Platinum Member
  • ******
  • Posts: 6448
How is the Main Arena connection for you?
« Reply #122 on: March 02, 2006, 10:32:19 AM »
Im not sure what bearing this has on anything, but normally when I logged into the arena, the ping for it would be at 70-80. Now its down to 65.
Logged

~AoM~

Offline Fury

  • Copper Member
  • **
  • Posts: 261
      • http://n/a
How is the Main Arena connection for you?
« Reply #123 on: March 02, 2006, 10:59:29 AM »
Based on PingPlotter alone, new connection is slightly worse - old=44ms, new=57ms.  Concerned about hop 10 on the new connection, 100% packet loss.  2 more hops to new connection.  Have not tried in-game yet.

Stats from PingPlotter on 3-2-06, Gand Haven MI using Charter Cable:

OLD:
Host Information
1, -------------- ,                                                  10.65.240.1
2,   66-227-153-170.static.bycy.mi.charter.com,66.227.153.170
3,   24-231-244-229.static.aldl.mi.charter.com, 24.231.244.229
4, -------------- ,                                                  12.124.15.61
5,   gbr2-p70.dtrmi.ip.att.net,                           12.123.139.26
6,   tbr1-p012601.dtrmi.ip.att.net,                    12.122.12.173
7,   tbr1-cl28.sl9mo.ip.att.net,                          12.122.12.186
8,   tbr2-cl6.dlstx.ip.att.net,                              12.122.10.90
9,   gbr1-p70.dlstx.ip.att.net,                           12.122.12.78
10,  gar1-p360.dlstx.ip.att.net,                        12.123.16.233
11,  mdf1-gsr12-2-pos-7-0.dal1.attens.net,     12.122.255.170
12,  mdf1-bi8k-2-eth-1-1.dal1.attens.net,        63.241.192.246
13, -------------- ,                                               206.16.60.38

AVG 44
5 minute sample 11:39amEST-11:44amEST

============================================

NEW:
Host Information
1, -------------- ,                                                 10.65.240.1
2,  66-227-153-170.static.bycy.mi.charter.com,66.227.153.170
3,  24-231-244-229.static.aldl.mi.charter.com, 24.231.244.229
4, -------------- ,                                                 12.124.15.61
5,  gbr2-p70.dtrmi.ip.att.net,                           12.123.139.26
6,  tbr1-p012601.dtrmi.ip.att.net,                    12.122.12.173
7,  tbr1-cl28.sl9mo.ip.att.net,                          12.122.12.186
8,  tbr2-cl6.dlstx.ip.att.net,                              12.122.10.90
9, -------------- ,                                                 12.122.82.45
10,,-
11,  border4.ge4-1-bbnet2.ext1.dal.pnap.net,  216.52.191.94
12,  colo4dallas-3.border4.ext1.dal.pnap.net, 216.52.189.10
13, -------------- ,                                              206.123.64.38
14, -------------- ,                                              206.123.64.98
15,  argon.gamerslobby.net,                          206.123.111.42

AVG 57
5 minute sample 11:48amEST - 11:53amEST
Logged

Offline Skuzzy

  • Support Member
  • Administrator
  • *****
  • Posts: 31462
      • HiTech Creations Home Page
How is the Main Arena connection for you?
« Reply #124 on: March 02, 2006, 11:06:12 AM »
Do not be concerned about that hop.  There is a router in the path which has blocked ICMP ECHO requests so it will always show up like that.
Logged
Roy "Skuzzy" Neese
support@hitechcreations.com

Offline daMIG

  • Copper Member
  • **
  • Posts: 133
Better
« Reply #125 on: March 02, 2006, 11:16:22 AM »
Better for me on the numbers,
old was avg of 15 hops, avg 50 - 53 ms.


New is avg of 12 hops, avg 17 - 20ms.

both connections steady, no fluctuations to speak of.
Logged

Offline Mugzeee

  • Silver Member
  • ****
  • Posts: 1650
How is the Main Arena connection for you?
« Reply #126 on: March 02, 2006, 12:39:40 PM »
New
13 Hops @ 70 Major spike at 10th Hop 4.78.24.74 doesnt display DNS for this IP.
Old
20 Hops @ 41 no spikes.
ISP= Earthlink.net through Roadrunner cable line.
Logged

Offline PuckHead

  • Zinc Member
  • *
  • Posts: 73
How is the Main Arena connection for you?
« Reply #127 on: March 02, 2006, 01:07:50 PM »
My ping has dropped from I would say an average of 84 down to 61-63, with a dsl connect.

PuCk
Logged

Offline Vad

  • Nickel Member
  • ***
  • Posts: 474
How is the Main Arena connection for you?
« Reply #128 on: March 02, 2006, 01:38:49 PM »
Game experience is the same or a little bit worse. Looks like more players around are warping.

Pings to old server look better and more stable:

PING 206.16.60.38 (206.16.60.38) 56(84) bytes of data.
64 bytes from 206.16.60.38: icmp_seq=1 ttl=240 time=66.0 ms
64 bytes from 206.16.60.38: icmp_seq=2 ttl=240 time=66.5 ms
64 bytes from 206.16.60.38: icmp_seq=3 ttl=240 time=71.1 ms
64 bytes from 206.16.60.38: icmp_seq=4 ttl=240 time=66.6 ms
64 bytes from 206.16.60.38: icmp_seq=5 ttl=240 time=67.5 ms
64 bytes from 206.16.60.38: icmp_seq=6 ttl=240 time=66.4 ms
64 bytes from 206.16.60.38: icmp_seq=7 ttl=240 time=68.1 ms
64 bytes from 206.16.60.38: icmp_seq=8 ttl=240 time=66.9 ms
64 bytes from 206.16.60.38: icmp_seq=9 ttl=240 time=69.3 ms
64 bytes from 206.16.60.38: icmp_seq=10 ttl=240 time=66.4 ms
64 bytes from 206.16.60.38: icmp_seq=11 ttl=240 time=66.1 ms
64 bytes from 206.16.60.38: icmp_seq=12 ttl=240 time=68.0 ms
64 bytes from 206.16.60.38: icmp_seq=13 ttl=240 time=65.6 ms
64 bytes from 206.16.60.38: icmp_seq=14 ttl=240 time=65.8 ms
64 bytes from 206.16.60.38: icmp_seq=15 ttl=240 time=70.5 ms
64 bytes from 206.16.60.38: icmp_seq=16 ttl=240 time=65.9 ms

--- 206.16.60.38 ping statistics ---
16 packets transmitted, 16 received, 0% packet loss, time 15150ms
rtt min/avg/max/mdev = 65.603/67.343/71.132/1.683 ms



PING 206.123.111.42 (206.123.111.42) 56(84) bytes of data.
64 bytes from 206.123.111.42: icmp_seq=1 ttl=239 time=73.2 ms
64 bytes from 206.123.111.42: icmp_seq=2 ttl=239 time=75.9 ms
64 bytes from 206.123.111.42: icmp_seq=3 ttl=239 time=75.9 ms
64 bytes from 206.123.111.42: icmp_seq=4 ttl=239 time=74.7 ms
64 bytes from 206.123.111.42: icmp_seq=5 ttl=239 time=75.5 ms
64 bytes from 206.123.111.42: icmp_seq=6 ttl=239 time=77.1 ms
64 bytes from 206.123.111.42: icmp_seq=7 ttl=239 time=75.0 ms
64 bytes from 206.123.111.42: icmp_seq=8 ttl=239 time=73.7 ms
64 bytes from 206.123.111.42: icmp_seq=9 ttl=239 time=74.6 ms
64 bytes from 206.123.111.42: icmp_seq=10 ttl=239 time=72.4 ms
64 bytes from 206.123.111.42: icmp_seq=11 ttl=239 time=74.7 ms
64 bytes from 206.123.111.42: icmp_seq=12 ttl=239 time=80.9 ms
64 bytes from 206.123.111.42: icmp_seq=13 ttl=239 time=72.6 ms
64 bytes from 206.123.111.42: icmp_seq=14 ttl=239 time=83.6 ms
64 bytes from 206.123.111.42: icmp_seq=15 ttl=239 time=75.4 ms

--- 206.123.111.42 ping statistics ---
15 packets transmitted, 15 received, 0% packet loss, time 14140ms
rtt min/avg/max/mdev = 72.461/75.733/83.620/2.913 ms


UDP and ICMP traceroutes to both destinations are very similar, so protocol isn't an issue:


[root@]# traceroute 206.16.60.38
traceroute to 206.16.60.38 (206.16.60.38), 30 hops max, 38 byte packets
 1  10.105.138.1 (10.105.138.1)  7.739 ms  7.501 ms  11.121 ms
 2  gw03.mtnk.phub.net.cable.roge rs.com (66.185.90.97)  8.268 ms  7.311 ms  7.415 ms
 3  64.71.241.53 (64.71.241.53)  7.876 ms  7.546 ms  6.929 ms
 4  gw03.ym.phub.net.cable.rogers .com (66.185.83.118)  9.121 ms  9.663 ms  9.472 ms
 5  igw01.vaash.phub.net.cable.ro gers.com (66.185.80.190)  27.793 ms  25.858 ms  26.661 ms
 6  if-15-0.core2.AEQ-Ashburn.teleglobe.net (209.58.27.33)  24.503 ms  25.471 ms  24.797 ms
 7  ix-13-1.core2.AEQ-Ashburn.teleglobe.net (209.58.27.42)  33.005 ms  31.504 ms  31.582 ms
 8  12.122.81.226 (12.122.81.226)  70.418 ms  68.998 ms  71.791 ms
 9  tbr1-cl4.sl9mo.ip.att.net (12.122.10.30)  67.912 ms  66.169 ms  67.601 ms
10  tbr2-cl6.dlstx.ip.att.net (12.122.10.90)  68.322 ms  67.384 ms  67.320 ms
11  gbr2-p100.dlstx.ip.att.net (12.122.12.82)  69.958 ms  67.277 ms  68.375 ms
12  gar1-p370.dlstx.ip.att.net (12.123.16.237)  65.636 ms  66.275 ms  69.478 ms
13  mdf1-gsr12-2-pos-7-0.dal1.attens.net (12.122.255.170)  69.026 ms  65.750 ms  66.415 ms
14  mdf1-bi8k-2-eth-1-2.dal1.attens.net (63.241.192.210)  67.727 ms  70.049 ms  66.821 ms
15  206.16.60.38 (206.16.60.38)  67.536 ms  76.215 ms  67.182 ms

[root@]# traceroute -I 206.16.60.38
traceroute to 206.16.60.38 (206.16.60.38), 30 hops max, 38 byte packets
 1  10.105.138.1 (10.105.138.1)  8.163 ms  8.033 ms  7.472 ms
 2  gw03.mtnk.phub.net.cable.roge rs.com (66.185.90.97)  13.743 ms  10.639 ms  8.954 ms
 3  64.71.241.53 (64.71.241.53)  11.298 ms  8.894 ms  7.397 ms
 4  gw03.ym.phub.net.cable.rogers .com (66.185.83.118)  8.684 ms  11.547 ms  9.574 ms
 5  igw01.vaash.phub.net.cable.ro gers.com (66.185.80.190)  25.795 ms  25.443 ms  23.633 ms
 6  if-15-0.core2.AEQ-Ashburn.teleglobe.net (209.58.27.33)  25.667 ms  25.827 ms  26.274 ms
 7  ix-13-1.core2.AEQ-Ashburn.teleglobe.net (209.58.27.42)  31.110 ms  30.044 ms  36.254 ms
 8  12.122.81.226 (12.122.81.226)  69.141 ms  70.769 ms  69.194 ms
 9  tbr1-cl4.sl9mo.ip.att.net (12.122.10.30)  67.497 ms  66.126 ms  68.219 ms
10  tbr2-cl6.dlstx.ip.att.net (12.122.10.90)  75.108 ms  67.408 ms  68.900 ms
11  gbr2-p100.dlstx.ip.att.net (12.122.12.82)  65.602 ms  112.010 ms  80.270 ms
12  gar1-p370.dlstx.ip.att.net (12.123.16.237)  65.306 ms  69.019 ms  66.365 ms
13  mdf1-gsr12-2-pos-7-0.dal1.attens.net (12.122.255.170)  66.040 ms  67.149 ms  67.975 ms
14  mdf1-bi8k-2-eth-1-2.dal1.attens.net (63.241.192.210)  67.760 ms  76.597 ms  67.317 ms
15  206.16.60.38 (206.16.60.38)  67.841 ms  67.718 ms  66.795 ms


[root@]# traceroute  206.123.111.42
traceroute to 206.123.111.42 (206.123.111.42), 30 hops max, 38 byte packets
 1  10.105.138.1 (10.105.138.1)  6.692 ms  7.552 ms  8.099 ms
 2  gw03.mtnk.phub.net.cable.roge rs.com (66.185.90.97)  18.599 ms  8.553 ms  8.394 ms
 3  gw01.mtnk.phub.net.cable.roge rs.com (66.185.83.93)  18.926 ms  7.902 ms  9.702 ms
 4  gw02.mtnk.phub.net.cable.roge rs.com (66.185.80.162)  7.736 ms  8.649 ms  7.113 ms
 5  igw01.ny8th.phub.net.cable.ro gers.com (66.185.81.13)  29.872 ms  29.642 ms  32.299 ms
 6  if-8-0.core1.NTO-NewYork.teleglobe.net (216.6.82.33)  24.347 ms  23.642 ms  25.629 ms
 7  if-11-0.mcore3.NJY-Newark.teleglobe.net (216.6.82.6)  34.835 ms  30.555 ms  30.322 ms
 8  if-3-0.mcore4.NJY-Newark.teleglobe.net (216.6.57.6)  27.311 ms  26.430 ms  28.268 ms
 9  if-5-0.core2.AEQ-Ashburn.teleglobe.net (216.6.63.18)  30.529 ms  28.412 ms  29.408 ms
10  so-1-2-0.e1.Washington1.Level3.net (65.59.88.209)  43.678 ms  35.667 ms  35.196 ms
11  so-2-1-0.bbr2.Washington1.Level3.net (209.244.11.13)  47.881 ms so-2-1-0.bbr1.Washington1.Level3.net (209.244.11.9)  39.229 ms so-2-1-0.bbr2.Washington1.Level3.net (209.244.11.13)  36.418 ms
12  as-0-0.bbr2.Dallas1.Level3.net (64.159.0.137)  72.402 ms  71.826 ms  71.645 ms
13  ae-22-54.car2.Dallas1.Level3.net (4.68.122.110)  74.352 ms  73.941 ms ae-22-56.car2.Dallas1.Level3.net (4.68.122.174)  72.271 ms
14  4.78.224.74 (4.78.224.74)  80.355 ms  73.613 ms  78.364 ms
15  206.123.64.30 (206.123.64.30)  76.178 ms  60.425 ms  59.061 ms
16  206.123.64.98 (206.123.64.98)  63.261 ms  59.776 ms  59.788 ms
17  argon.gamerslobby.net (206.123.111.42)  74.382 ms  75.339 ms  74.610 ms

[root@]# traceroute  -I 206.123.111.42
traceroute to 206.123.111.42 (206.123.111.42), 30 hops max, 38 byte packets
 1  10.105.138.1 (10.105.138.1)  10.146 ms  6.370 ms  8.681 ms
 2  gw03.mtnk.phub.net.cable.roge rs.com (66.185.90.97)  8.900 ms  7.731 ms  10.560 ms
 3  gw01.mtnk.phub.net.cable.roge rs.com (66.185.83.93)  8.221 ms  8.059 ms  7.932 ms
 4  gw02.mtnk.phub.net.cable.roge rs.com (66.185.80.162)  24.791 ms  8.165 ms  8.159 ms
 5  igw01.ny8th.phub.net.cable.ro gers.com (66.185.81.13)  28.722 ms  30.034 ms  30.399 ms
 6  if-8-0.core1.NTO-NewYork.teleglobe.net (216.6.82.33)  28.006 ms  25.935 ms  25.180 ms
 7  if-11-0.mcore3.NJY-Newark.teleglobe.net (216.6.82.6)  29.004 ms  29.425 ms  31.614 ms
 8  if-3-0.mcore4.NJY-Newark.teleglobe.net (216.6.57.6)  25.227 ms  25.718 ms  23.569 ms
 9  if-5-0.core2.AEQ-Ashburn.teleglobe.net (216.6.63.18)  36.523 ms  30.540 ms  33.729 ms
10  so-1-2-0.e1.Washington1.Level3.net (65.59.88.209)  37.481 ms  38.969 ms  37.288 ms
11  so-2-1-0.bbr2.Washington1.Level3.net (209.244.11.13)  37.780 ms so-2-1-0.bbr1.Washington1.Level3.net (209.244.11.9)  35.799 ms  38.939 ms
12  as-0-0.bbr2.Dallas1.Level3.net (64.159.0.137)  71.042 ms  74.147 ms  75.033 ms
13  ae-22-54.car2.Dallas1.Level3.net (4.68.122.110)  80.052 ms ae-22-56.car2.Dallas1.Level3.net (4.68.122.174)  73.014 ms  79.648 ms
14  4.78.224.74 (4.78.224.74)  76.927 ms  74.495 ms  73.568 ms
15  206.123.64.30 (206.123.64.30)  59.075 ms  58.864 ms  62.436 ms
16  206.123.64.98 (206.123.64.98)  60.100 ms  59.594 ms  59.829 ms
17  argon.gamerslobby.net (206.123.111.42)  73.828 ms  74.302 ms  74.342 ms


ISP - Rogers.com, Toronto.
Logged

Offline Gianlupo

  • Platinum Member
  • ******
  • Posts: 5154
How is the Main Arena connection for you?
« Reply #129 on: March 02, 2006, 02:40:57 PM »
Basically same:

old server



new server

Logged
Live to fly, fly to live!

Offline fartwinkle

  • Parolee
  • Nickel Member
  • ***
  • Posts: 551
How is the Main Arena connection for you?
« Reply #130 on: March 02, 2006, 03:48:58 PM »
Verizon. Plano Tx

Logged

Offline wrag

  • Gold Member
  • *****
  • Posts: 3499
How is the Main Arena connection for you?
« Reply #131 on: March 02, 2006, 04:16:40 PM »
OOPS OK adding info.

Hops same 16 old 16 new.

ISP dialup Outdrs.net.  Nevada.  No cable or DSL available. :(

I do seem to get allot of switching on 2 of the hops.  Last digit of hop address seems to change every hop?  Pingplotter set to poll every second.

Yesterday AFTER I posted the 1st time I connected, my connect seemed to go back to the way it used to be?  But now in the mornings where it used to be better? My Shots lookin like they go right through the cons?

Wonder if the new AH ISP is just concentrating on makin the connect nice for a few days to insure payment then ignore us?  Then again maybe just a short term glich somewhere?

So connect seems maybe worse?  Will repost in 2 or 3 days to see if it improves to at least where it used to be.
Logged
It's been said we have three brains, one cobbled on top of the next. The stem is first, the reptilian brain; then the mammalian cerebellum; finally the over developed cerebral cortex.  They don't work together in awfully good harmony - hence ax murders, mobs, and socialism.

Offline grmrpr

  • Copper Member
  • **
  • Posts: 246
      • http://www.maderios.org/
Multi Test
« Reply #132 on: March 02, 2006, 04:28:27 PM »
Pinging from Unix Boxes with command:

for i in 206.123.111.42 206.16.60.38; do ping -c 10 -q $i; done



Results:

Quote

Raleigh, NC Sprint 3MB DSL

--- 206.123.111.42 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9000ms
rtt min/avg/max/mdev = 64.743/65.250/65.879/0.423 ms, pipe 2

--- 206.16.60.38 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9009ms
rtt min/avg/max/mdev = 60.384/60.819/62.077/0.548 ms, pipe 2


Quote

Durham, NC SunGuard Dual OC3

--- 206.123.111.42 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9080ms
rtt min/avg/max/mdev = 49.487/49.873/50.188/0.373 ms, pipe 2

--- 206.16.60.38 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9088ms
rtt min/avg/max/mdev = 45.462/45.774/45.992/0.194 ms, pipe 2


Quote

Portland, OR AT&T T1

--- 206.123.111.42 ping statistics ---
10 packets transmitted, 10 received, 0% loss, time 9089ms
rtt min/avg/max/mdev = 60.707/61.223/62.649/0.635 ms

--- 206.16.60.38 ping statistics ---
10 packets transmitted, 10 received, 0% loss, time 9084ms
rtt min/avg/max/mdev = 63.546/63.745/64.549/0.335 ms



Quote

Suak Rapids, MN  3mb Cable

10 packets transmitted, 10 received, 0% loss, time 9089ms
rtt min/avg/max/mdev = 44.001/46.044/51.885/2.223 ms

--- 206.16.60.38 ping statistics ---
10 packets transmitted, 10 received, 0% loss, time 9092ms
rtt min/avg/max/mdev = 44.873/51.313/64.855/6.659 ms



Quote

Billings, MT 2mb Cable

--- 206.123.111.42 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9089ms
rtt min/avg/max/mdev = 54.797/57.493/66.340/3.406 ms, pipe 2

--- 206.16.60.38 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9090ms
rtt min/avg/max/mdev = 53.460/56.416/63.730/2.981 ms, pipe 2


Quote

Memphis, TN AT&T 128k ISDN

--- 206.123.111.42 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9084ms
rtt min/avg/max/mdev = 91.873/93.483/95.215/0.954 ms, pipe 2

--- 206.16.60.38 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9093ms
rtt min/avg/max/mdev = 90.855/92.676/94.190/1.073 ms, pipe 2


Quote

Newport, NC RoadRunner 5mb Cable

--- 206.123.111.42 ping statistics ---
10 packets transmitted, 10 received, 0% loss, time 9093ms
rtt min/avg/max/mdev = 54.500/55.849/57.558/0.905 ms

--- 206.16.60.38 ping statistics ---
10 packets transmitted, 10 received, 0% loss, time 9091ms
rtt min/avg/max/mdev = 52.853/54.106/55.510/0.781 ms



That should be a decent sample set.  May I also add that since moving I have not seen a single "Outage".

GrmRpr
Logged

Offline grmrpr

  • Copper Member
  • **
  • Posts: 246
      • http://www.maderios.org/
Re: Multi Test
« Reply #133 on: March 02, 2006, 04:32:36 PM »
Skuzzy if you want traceroutes from all these let me know.
Logged

Offline yb11

  • Copper Member
  • **
  • Posts: 118
How is the Main Arena connection for you?
« Reply #134 on: March 02, 2006, 04:41:50 PM »
can we lock this thred my e mail is gitting jamed up think we have enuff en fo
Logged
Pages: 1 ... 6 7 8 [9] 10 11 12 ... 16   Go Up
« previous next »