+ Reply to Thread
Results 1 to 4 of 4
Discussion: Battlefield 2142 / Battlefield 2142 - Technical Support & FAQs - Found the culprit (maybe) - I think I might have found the culprit that has been causing my erratic and
-
04-21-2009, 03:12 AM #1
- Join Date
- Aug 2008
- Location
- Shooting down Repaq and Tom Da Slaya's Gunship with a SAAW after being TV missled....ok National City, CA
- Posts
- 399
Found the culprit (maybe)
I think I might have found the culprit that has been causing my erratic and high server ping. I ran a tracer route this evening around 7:30 and here are the results:
Tracing route to 64.34.163.112 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.0.1
2 17 ms 18 ms 8 ms 10.146.120.1
3 48 ms 7 ms 11 ms 68.6.11.170
4 11 ms 23 ms 7 ms 68.6.8.236
5 9 ms 8 ms 10 ms fed1dsrj01-ge500.0.rd.sd.cox.net [68.6.8.0]
6 66 ms 44 ms 28 ms paltbbrj01-ae2.0.r2.pt.cox.net [68.1.2.98]
7 48 ms 56 ms 52 ms 10ge.xe-0-0-0.sea-coloc-dis-1.peer1.net [216.187.88.201]
8 52 ms 93 ms 61 ms oc48.so-3-2-0.van-hc21e-cor-1.peer1.net [216.187.88.29]
9 89 ms 88 ms 88 ms oc48.so-3-0-2.tor-151f-cor-1.peer1.net [216.187.114.138]
10 101 ms 102 ms 102 ms oc48-po3-0.mtl-bvh-cor-1.peer1.net [216.187.114.198]
11 101 ms * 100 ms 10ge.xe-0-0-0.mtl-bvh-cor-1.peer1.net [216.187.115.85]
12 101 ms 100 ms 104 ms oc192.xe-4-0-0.nyc-telx-dis-1.peer1.net [216.187.115.54]
13 104 ms 106 ms 104 ms 10ge.ten1-2.wdc-sp2-cor-2.peer1.net [216.187.115.222]
14 * 99 ms 101 ms 10ge.ten1-1.wdc-sp2-cor-1.peer1.net [216.187.116.253]
15 101 ms 101 ms 111 ms 216.187.120.234
16 108 ms 109 ms 108 ms 64.34.163.112
and again at 10:30
Tracing route to 64.34.163.112 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.0.1
2 28 ms 30 ms 28 ms 10.146.120.1
3 65 ms 30 ms 30 ms 68.6.11.170
4 32 ms 41 ms 31 ms 68.6.8.236
5 38 ms 29 ms 27 ms fed1dsrj01-ge500.0.rd.sd.cox.net [68.6.8.0]
6 54 ms 52 ms 86 ms paltbbrj01-ae2.0.r2.pt.cox.net [68.1.2.98]
7 69 ms 72 ms 71 ms 10ge.xe-0-0-0.sea-coloc-dis-1.peer1.net [216.187.88.201]
8 73 ms 73 ms 77 ms oc48.so-3-2-0.van-hc21e-cor-1.peer1.net [216.187.88.29]
9 108 ms 119 ms 110 ms oc48.so-3-0-2.tor-151f-cor-1.peer1.net [216.187.114.138]
10 140 ms 125 ms 123 ms oc48-po3-0.mtl-bvh-cor-1.peer1.net [216.187.114.198]
11 135 ms 122 ms 124 ms 10ge.xe-0-0-0.mtl-bvh-cor-1.peer1.net [216.187.115.85]
12 123 ms 121 ms 122 ms oc192.xe-4-0-0.nyc-telx-dis-1.peer1.net [216.187.115.54]
13 126 ms 136 ms 130 ms 10ge.ten1-2.wdc-sp2-cor-2.peer1.net [216.187.115.222]
14 125 ms 120 ms 122 ms 10ge.ten1-1.wdc-sp2-cor-1.peer1.net [216.187.116.253]
15 168 ms 122 ms 120 ms 216.187.120.234
16 131 ms 128 ms 138 ms 64.34.163.112
My ping really begins to spike when it reaches the peer1.net servers and this continues until I reach the TG server. Anyone ever heard of peer1.net? Any info on their reputation as a company? I am going to contact them by e-mail and see what response I get. I would welcome any thoughts or suggestions on how to pursue this. Also, if I have misinterpreted these tracer results and it isn't peer1.net please tell me.
AB
"Press the red shiny button"~Vortex
"I may give out, but I'll never give in." ~ Lou Bond "To the Establishment"
-
04-21-2009, 09:42 AM #2
- Join Date
- Apr 2008
- Location
- London
- Age
- 30
- Posts
- 2,243
Re: Found the culprit (maybe)
This doesn't really help too much. You don't have a say in where your connection goes once on the web and it will rarely will use the same route. Is your ping to server up and down?
ping 64.34.163.112 -t
Leave it run for 20 seconds and see if it's up and down a lot. If it's stable, then try larger packets:
ping 64.34.163.112 -t -l 500
(Not sure packet size of game data...)
I found larger packets were more speradic, but that's expected. It won't help fix the issue, but I noticed problem with my connection, and it was my providers fault as I had a lot of noise on the phone line, so I needed to a) fix the phone sockets and b) get the ISP to change the noise level, which sometimes slows the connection down, but makes it much more reliable! I was dropping packets though, so contact your ISP and see what they say. They have things they can change. I'm overseas, so I get about 100 ping.
Also, peer1.net must just be the local ISP where the server is held, so your always going to go through this, like the rest of us..BF3 Soldier: DrSparky
"Cum bellum clamavit, respondivi"
-
04-21-2009, 10:06 AM #3
- Join Date
- Apr 2007
- Location
- Norway
- Age
- 35
- Posts
- 5,666
Re: Found the culprit (maybe)
Peer1 is company that does peering with ISPs.
Looks like they either had problems or was doing changes. If you still have problems, tell your ISP.
-
04-21-2009, 03:35 PM #4
- Join Date
- Aug 2008
- Location
- Shooting down Repaq and Tom Da Slaya's Gunship with a SAAW after being TV missled....ok National City, CA
- Posts
- 399
Re: Found the culprit (maybe)
It's not my ISP. I've had two of their technicians at my house and they replaced all my connections and they tested the signal to their server and it is very good. Obviously, they can't control anything beyond their server. It just seems when my connection reaches the peer1.net servers my ping begins to spike. I suspect this could mean a lot of users and not enough bandwidth.
My ping can be stable and erratic. One moment it can be 110 and then it starts rising and falling between 120 and 150. I'd love to have a stable ping of around a 100. I'm in southwest coast of the US and used to have an 85-90 ping. I rarely have that now. I cannot be the only one having performance problems. There must be other people in my area who connect to servers on the east coast. I did run a ping test at -n 100 and had 0 packet loss. I'll give 500 a go. I appreciate the responses."Press the red shiny button"~Vortex"I may give out, but I'll never give in." ~ Lou Bond "To the Establishment"
Reply With QuoteThread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
Bookmarks