4.3 Disconnects / Latency / Lag, OH, Time Warner

(Locked)

85 Worgen Druid
8475
::UPDATE 12/15/11::
As some other uses have pointed out this issue is now being reporting from a number of different realms across many of the different Blizzard Datacenters not localized to the LA center. Some users have offered other ideas that have fixed their issues however in many cases these fixes do resolve something on your end and not Blizzard's.

Currently the only fix I have found for those having the exact issues described in this post is to use a proxy or tunneling service to connect to WoW. This may or may not fix your issue depending on how traffic is being routed. Still no update from Blizzard, will update post if/when that happens.
::END UPDATE::

I am aware there are a number of threads concerning this issue however many of them have gone either unanswered, unsolved, or have incorrect/incomplete information. Also, a number of threads seem to be getting replies from "level 1" service reps. Unless you are a high-level technical support rep please don't waste your time replying to this thread as it will not help but only give false hope of an easy fix.

Now on to the fun part.. the issue at hand:
::READ THIS BEFORE YOU REPLY IN THIS THREAD::

Since 4.3, and for some people before the patch, the game client has repeatedly exhibited the following connection and latency issues:

1. Home latency remains low and consistent while world latency frequently "spikes" up anywhere from 100ms-4000ms+

2. Random disconnections from BGs, Raids, and/or Dungeons where the player is unable to log directly back into the game and resume play.
- BG: Player will be unable to log back in to the battle ground and will sit at a load screen until they have been removed from the battleground and given a deserter debuff (unless the BG ended before the player would be auto ported out)
- Raid: Player is unable to log back in and resume raiding and will eventually be ported either to the graveyard or the previous location prior to being ported into the raid instance. In some cases attempting to re-enter the raid instance will hang the load screen until a fair amount of time has passed.
- Dungeon: Similar to raids, however due to the time taken to relog into the game (load screen wait), players will typically be removed by the dungeon group for the disconnect.

3. Spells and abilities will "hang" or "lag", usually with world latency spiking, sometimes while being reported as normal, however during these bursts of lag the in-game chat system appears to be unaffected and continues without interruption. These spikes may last anywhere from a few moments to 30 seconds or more in which the game client will either catch up in key presses or world latency will spike to an unplayable amount. Also, this does not seem to cause a disconnection, only a large amount of lag.
------------------------------------------------------------------------------------------------------

If your issue is exactly as above feel free to post in this thread describing which part if not all of the above applies to you and add to the above issues with anything else you may be experiencing. If you are not having most of the issues stated above (based on what you do in the game) please post in another thread as your issue may be something else.

Before you post please be sure you have done the following (as most other threads think are the answer and I assure you if you have our issue they are not):

- Un-check the "Optimize Network Speed" option in your game client.
- Be sure all drivers and firmware are up to date
- Turn off/Remove all addons
- Delete Cache and WTF folders
- Run WoWRepair.exe
- Temporarily disable any virus scan software and/or firewalls to see if the error continues.
- Temporarily run msconfig and set windows startup to "selective startup" and un-check the "load statup items" box.
- In an elevated command prompt windows (still PC) run the command ipconfig /flushdns
- Close other programs and turn off devices that may be using the internet such as streaming video or music, torrents, skype, or any other drain on your bandwidth.
- If you are running a wireless connection to your PC, for the sake of testing, use a wired connection.
- If you are using a router between your pc and the internet connection (ie: Cable modem and router) connect directly to your internet source with a wired connection if possible.
- Check all cables and wires to be sure connections are not damaged in any way.
- In a command prompt window (for PC) run a trace route to your realm's IP address (as listed here: http://www.wowpedia.org/US_realm_list_by_datacenter) during events of extreme lag.
- If available connect from a different PC and/or connection (ie: friend's house)


Long list I know, but not a single one of them should fix the problem if you are "one of us" who still need Blizzard to do something about this game play debilitating issue. It is not on our end, it is not our ISP. We will provide you with whatever information you need to get it fixed but we need it fixed. At the moment that is what we are paying you for since our ability to play the game is being plagued by this issue.

Please post any information in the following format for this thread:
(to create the "box" around the trace route info, select all text, press the "pre" button above your post window)
-----------------------------------------------------------------------------------------------------
Ream: Firetree
Tracing route to 12.129.222.168 over a maximum of 30 hops

1 8 ms 8 ms 9 ms 10.228.0.1
2 18 ms 16 ms 16 ms gig8-0-0-9.mtgmoh1-rtr4.cinci.rr.com [24.29.2.209]
3 22 ms 21 ms 21 ms tge7-1-1.tr00.clmkohpe.mwrtn.rr.com [65.25.137.85]
4 23 ms 21 ms 22 ms ae-9-0.cr0.chi30.tbone.rr.com [107.14.19.16]
5 22 ms 24 ms 23 ms 107.14.17.147
6 46 ms 47 ms 46 ms 216.156.72.157.ptr.us.xo.net [216.156.72.157]
7 46 ms 46 ms 45 ms 206.111.2.90.ptr.us.xo.net [206.111.2.90]
8 90 ms 79 ms 82 ms cr1.cgcil.ip.att.net [12.122.81.94]
9 80 ms 80 ms 78 ms cr2.dvmco.ip.att.net [12.122.31.85]
10 80 ms 79 ms 80 ms cr1.slkut.ip.att.net [12.122.30.25]
11 88 ms 89 ms * cr2.la2ca.ip.att.net [12.122.30.30]
12 150 ms 100 ms 149 ms gar29.la2ca.ip.att.net [12.122.129.241]
13 80 ms 78 ms 79 ms 12-122-254-234.attens.net [12.122.254.234]
14 80 ms 79 ms 79 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.


Connection Type: Wired
Router Model: None
Modem Model: Motorola SB6580
Location: Cincinnati, OH
ISP: Time Warner Cable
Firewall Software: OFF
Anti-Virus Software: OFF
Computer OS: Windows 7 x64
Network Card Model: Killer 2100 NIC
Pingtest.net Grade: A
Additional Issues: None
------------------------------------------------------------------------------------------------

I will update this as needed. To get your line quality test grade visit pingtest.net and simply press "begin test".

Here is hoping Blizzard fixes this before the weekend... <ul/> <li/>
Edited by Animorphed on 12/15/2011 12:54 PM PST
85 Human Priest
4490
Finally a complete explanation of the issue and all possible fixes! You are right too, not a single one helps me either!

Realm: Firetree

Tracing route to 12.129.222.168 over a maximum of 30 hops

1 9 ms 6 ms 7 ms 10.228.0.1
2 9 ms 10 ms 11 ms gig8-0-0-9.mtgmoh1-rtr4.cinci.rr.com [24.29.2.209]
3 18 ms 12 ms 63 ms tge7-1-1.tr00.clmkohpe.mwrtn.rr.com [65.25.137.85]
4 31 ms 21 ms 21 ms ae-9-0.cr0.chi30.tbone.rr.com [107.14.19.16]
5 24 ms 40 ms 22 ms 107.14.17.147
6 44 ms 45 ms 45 ms 216.156.72.157.ptr.us.xo.net [216.156.72.157]
7 46 ms 45 ms 45 ms 206.111.2.90.ptr.us.xo.net [206.111.2.90]
8 78 ms 79 ms 80 ms cr1.cgcil.ip.att.net [12.122.81.94]
9 80 ms 79 ms 80 ms cr2.dvmco.ip.att.net [12.122.31.85]
10 82 ms 79 ms 79 ms cr1.slkut.ip.att.net [12.122.30.25]
11 80 ms 79 ms 83 ms cr2.la2ca.ip.att.net [12.122.30.30]
12 78 ms 78 ms 76 ms gar29.la2ca.ip.att.net [12.122.129.241]
13 78 ms 81 ms 78 ms 12-122-254-234.attens.net [12.122.254.234]
14 78 ms 78 ms 79 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Wasn't lagging when I did this, but I'm going to bed.

Connection Type: Wired
Router Model: None
Modem Model: Motorola SB6580
Location: Cincinnati, OH
ISP: TWC Extreme RR
Firewall Software: OFF
Anti-Virus Software: OFF
Computer OS: Windows 7 x64
Network Card Realtek GBE Onboard Ethernet Adapter
Pingtest.net Grade: A
Additional Issues: None
100 Human Priest
18090
And here I thought I was the only one experiencing this. I'm gonna post my info and results tonight.
I have the same problem, and I have done all the troubleshooting mentioned here. I am having a hard time believing its on my end.
90 Night Elf Druid
7595
Having this issue too, I've been having it since 1 day after the last maintenance (I spent the first day doing bgs without any issues), since then my world ping is averaging 2K while home is its usual 210-400. It will be fine for 2 minutes then seizure up for 15 seconds, Chat still works but everyone is running while not actually moving, can't loot, cant leave bgs etc.

Realm Suarfang
Tracing route to 12.129.255.44 over a maximum of 30 hops

1 2 ms 1 ms 1 ms home [10.0.0.138]
2 22 ms 18 ms 25 ms 172.18.112.71
3 * 21 ms 19 ms 172.18.93.154
4 19 ms 19 ms 19 ms 172.18.239.14
5 * 23 ms 23 ms 172.18.239.9
6 30 ms 24 ms * Bundle-Ether10.ken39.Sydney.telstra.net [203.45.17.17]
7 21 ms 22 ms 25 ms Bundle-Ether6.ken-core4.Sydney.telstra.net [203.50.6.145]
8 31 ms 23 ms 25 ms Bundle-Ether1.pad-gw2.Sydney.telstra.net [203.50.6.29]
9 19 ms 21 ms 20 ms 203.50.13.118
10 156 ms 157 ms 157 ms i-0-5-0-0.paix-core01.bx.reach.com [202.84.144.157]
11 * 157 ms * i-3-1.paix01.bi.reach.com [202.84.251.34]
12 213 ms 213 ms 211 ms 206.24.240.149
13 194 ms 192 ms 193 ms er2-xe-11-1-0.sanfrancisco.savvis.net [204.70.206.58]
14 193 ms * 193 ms pr2-ge-7-0-0.SanJoseEquinix.savvis.net [204.70.203.22]
15 * 214 ms 216 ms savvis-gw.sffca.ip.att.net [192.205.36.5]
16 209 ms 206 ms * cr1.sffca.ip.att.net [12.122.137.122]
17 228 ms 228 ms * cr1.la2ca.ip.att.net [12.122.3.122]
18 205 ms * 204 ms gar20.la2ca.ip.att.net [12.122.128.181]
19 223 ms 224 ms 226 ms 12-122-254-234.attens.net [12.122.254.234]
20 203 ms 204 ms 204 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.


Connection Type: Wired
Router Model: None
Modem Model: 2WIRE 2701HGV-W
Location: Terrigal, NSW, Australia
ISP: Bigpond (Telstra)
Firewall Software: OFF
Anti-Virus Software: OFF
Computer OS: Vista 32
Network Card Model: NVIDIA nForce 10/100/1000 Mbps Ethernet
Pingtest.net Grade: C
Additional Issues: None
I've been having the same problems. My home latency is always low but my world latency typically will be around 1000-4000 ms. My spells also lag. I'll be fine for a few seconds and then get a spike where I can't do anything other than type. All the spells I've tried to use will be lit up, but none of them will cast for a few seconds, sometimes lasting over 10 seconds. This makes raiding and pvp'ing impossible. The game doesn't register when my character moves, so I end up standing in stuff and dying.
85 Undead Rogue
2730
Same problems here. I am wasting so much time on the deserter debuff. I should be awarded at least honor points you get from a loss. I pay for this crap , and yet they won't address the issue to us in the forums. wow,
61 Gnome Warrior
1000
I've been having the same issues and I've tried almost everything in that list and some more (short of changing my OS). Is there really no hope? *melodramatic pause*

Realm: Shadow Council

Tracing route to 12.129.222.161 over a maximum of 30 hops

1 3 ms 3 ms 5 ms 192.168.100.1
2 11 ms 13 ms 4 ms 10.100.0.1
3 4 ms 3 ms 5 ms 10.0.0.254
4 7 ms 3 ms 3 ms fixed-203-69-2.iusacell.net [189.203.69.2]
5 17 ms 23 ms 21 ms 207.83.192.22
6 32 ms 30 ms 31 ms xe-10-0-0.bar2.Houston1.Level3.net [4.59.126.61]

7 29 ms 41 ms 30 ms ae-0-11.bar1.Houston1.Level3.net [4.69.137.133]

8 34 ms 34 ms 34 ms ae-13-13.ebr1.Dallas1.Level3.net [4.69.137.138]

9 47 ms 34 ms 38 ms ae-61-61.csw1.Dallas1.Level3.net [4.69.151.125]

10 41 ms 34 ms 34 ms ae-1-60.edge10.Dallas1.Level3.net [4.69.145.18]

11 37 ms 37 ms 39 ms ATT [4.68.62.230]
12 73 ms 70 ms 73 ms cr2.dlstx.ip.att.net [12.123.16.110]
13 82 ms 71 ms 72 ms cr2.la2ca.ip.att.net [12.122.28.178]
14 66 ms 67 ms 66 ms gar29.la2ca.ip.att.net [12.122.129.241]
15 69 ms 67 ms 67 ms 12-122-254-238.attens.net [12.122.254.238]
16 67 ms 67 ms 67 ms 12.129.193.254
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.


Connection Type: Wireless
Router Model: Huawei Echo Life HG8245
Modem Model: None
Location: Mexico City, Mexico
ISP: Iusacell PCS de México, S.A.
Firewall Software: OFF
Anti-Virus Software: OFF
Computer OS: Windows 7 64bit
Network Card Model: Intel Centrino Advanced-N 6200
Pingtest.net Grade: A
Additional Issues: None
100 Troll Hunter
9610
This is especially annoying in RBG. I get DC then when trying to log in I can't get back till I am ported out of the BG.
100 Human Mage
5200
Yep I am getting the lag, the stupidly high latency, the rubberbanding. It is unpredictable and inconsistent - sometimes I am fine, then suddenly not. It is intensely frustrating
76 Night Elf Druid
1160
It would be nice if Blizzard could at least acknowledge that there is a problem here. I am growing bored of the game because I can't do anything except sit in a city..... and sometimes I can't even do that.

Needless to say, I'll have to cancel my account soon if this issue isn't addressed. Not trying to threaten because I know it means nothing to Blizzard to loose my subscription. (obviously from their lack of care shown to the people affected by their problem)
90 Orc Warrior
6960
I've had the EXACT same issues as noted in your original post!
Please can anybody help us? It's making game play unbearable and irritating.
90 Human Death Knight
5925
I randomly crash and have Fatal Errors when im entering an specific zone or im in a fight like in Dragon Soul raid after Hagara screams "IMPOSSIBLE" after we destroy her lightning totems it crashes not even a warning has happened 2 times already and nothing seems to work
85 Draenei Shaman
6435
It seems the issue is with the packet return stream from ATT to any RR customer (TWC/Comcast) but varies. I am on Verizon Fios with normal play. My brother is the OP on TWC. He fixed the issue for himself for now by tethering to his 4G LTE phone. It's still an issue, it's not on the user's end, its on the AT&T side, and its in the packet return from AT&T (Blizz uses AT&T Data Centers btw for their WoW servers so it will take Blizzard actually doing something about it since they are the customer in this case). There has been no blue post to this thread yet because they cannot fix it by telling you to do anything as it's not you. It WOULD be nice though to see a Blue acknowledge the issue for people and let them know what they are doing about it on their end. Even a post stating "we are aware of the issue and that it is on our end but we do not have an ETA to repair at this time" would be better than silence imo.
100 Human Priest
18090
It seems the issue is with the packet return stream from ATT to any RR customer (TWC/Comcast) but varies. I am on Verizon Fios with normal play. My brother is the OP on TWC. He fixed the issue for himself for now by tethering to his 4G LTE phone. It's still an issue, it's not on the user's end, its on the AT&T side, and its in the packet return from AT&T (Blizz uses AT&T Data Centers btw for their WoW servers so it will take Blizzard actually doing something about it since they are the customer in this case). There has been no blue post to this thread yet because they cannot fix it by telling you to do anything as it's not you. It WOULD be nice though to see a Blue acknowledge the issue for people and let them know what they are doing about it on their end. Even a post stating "we are aware of the issue and that it is on our end but we do not have an ETA to repair at this time" would be better than silence imo.


Thank you. This makes a lot of sense. I've done everything possible to fix this problem including completely reinstalling the game and rebuilding my UI, and nothing is working. Blizzard needs to look into this because I'm having a hard time seeing myself paying them for a game I can barely play.
100 Dwarf Paladin
13765
It seems the issue is with the packet return stream from ATT to any RR customer (TWC/Comcast) but varies. I am on Verizon Fios with normal play. My brother is the OP on TWC. He fixed the issue for himself for now by tethering to his 4G LTE phone. It's still an issue, it's not on the user's end, its on the AT&T side, and its in the packet return from AT&T (Blizz uses AT&T Data Centers btw for their WoW servers so it will take Blizzard actually doing something about it since they are the customer in this case). There has been no blue post to this thread yet because they cannot fix it by telling you to do anything as it's not you. It WOULD be nice though to see a Blue acknowledge the issue for people and let them know what they are doing about it on their end. Even a post stating "we are aware of the issue and that it is on our end but we do not have an ETA to repair at this time" would be better than silence imo.


Close but if it is only happening to RR/TWC/Comcast customers and ALL WOW data goes through AT&T then it is NOT AT&T it is RR/TWC?Comcast or their upstream provider if they do not connect directly to AT&T. Almost no ISP will hand their data off directly to a Backbone.

Most people miss that it is not your ISP to AT&T it is ISP -> Upstream Provider maybe more than 1 and then AT&T. I have a hunch that in most cases it is that upstream provider that is the issue. I work as a level 3 Tech for an ISP about 2 years ago our customers where complaining about these same issues. We fixed them by switching upstream providers.

If the issue was with Blizzard or the AT&T data centers all users of the affected server would be having the same issue.

If you look through the traces you can see the hand offs between the providers the OP's ISP hands their data off to XO.com another poster's ISP goes through level3.net Eve's data stream goes through 2 intermediary carriers before AT&T, Reach and Savvis although her issue clearly starts at her ISP

I would assume most of the issue described here come down to some type of congestion on the upstream or bandwidth throttling of some type on the same. A lot of ISP's purchase X amount of Guaranteed upstream with the ability to burst above that for short periods. It is in the ISP's interest to throttle since they are usually charged extra if they burst above the guaranteed amount often. The other option would be that the upstream provider is not handing routing data to AT&T correctly causing the return route to be unstable.
85 Tauren Druid
7330
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\joe>tracert us.logon.battle.net

Tracing route to us.logon.battle.net [12.129.206.130]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 12 ms 13 ms 7 ms ge-3-37-ur02.carmel.ny.hartford.comcast.net [68.
85.140.177]
4 7 ms 8 ms 11 ms po-63-ur01.carmel.ny.hartford.comcast.net [68.86
.231.189]
5 8 ms 8 ms 8 ms po-64-ur01.danbury.ct.hartford.comcast.net [68.8
6.230.253]
6 11 ms 10 ms 10 ms be-53-ar01.berlin.ct.hartford.comcast.net [68.85
.162.185]
7 13 ms 12 ms 11 ms pos-0-14-0-0-ar01.chartford.ct.hartford.comcast.
net [68.87.144.146]
8 15 ms 14 ms 15 ms pos-1-4-0-0-ar01.needham.ma.boston.comcast.net [
68.85.162.69]
9 44 ms 44 ms 43 ms pos-2-4-0-0-cr01.newyork.ny.ibone.comcast.net [6
8.86.90.61]
10 43 ms 44 ms 43 ms pos-1-2-0-0-pe01.111eighthave.ny.ibone.comcast.n
et [68.86.86.74]
11 42 ms 43 ms 44 ms 192.205.37.33
12 108 ms 109 ms 107 ms cr1.n54ny.ip.att.net [12.122.131.86]
13 105 ms 108 ms 111 ms cr2.cgcil.ip.att.net [12.122.1.2]
14 106 ms 107 ms 105 ms cr1.cgcil.ip.att.net [12.122.2.53]
15 107 ms 107 ms 107 ms cr2.dvmco.ip.att.net [12.122.31.85]
16 110 ms 107 ms 116 ms cr1.slkut.ip.att.net [12.122.30.25]
17 114 ms 117 ms 107 ms cr2.la2ca.ip.att.net [12.122.30.30]
18 131 ms 123 ms 145 ms gar29.la2ca.ip.att.net [12.122.129.241]
19 112 ms 103 ms 103 ms 12-122-254-238.attens.net [12.122.254.238]
20 104 ms 104 ms 105 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.12
9.193.254]
21 * * 12.129.211.34 reports: Destination net unreachable.

Trace complete.

C:\Users\joe>


I hate this game right now because of this problem
85 Worgen Druid
8475
Close but if it is only happening to RR/TWC/Comcast customers and ALL WOW data goes through AT&T then it is NOT AT&T it is RR/TWC?Comcast or their upstream provider if they do not connect directly to AT&T. Almost no ISP will hand their data off directly to a Backbone.


That's not correct. While it is true all data does go through AT&T different providers are routed in different ways. The servers that exist along the route of the TWC/Comcast hand-off are causing the spikes in the data return. Data to the AT&T system is normal while the data coming back from AT&T across servers is not being sent correctly or some other issue causing the spike. I have been using my 4G LTE Verizon device to play now and have had no issues however running a traceroute to my server (Firetree) while on this connection does not pass through the same servers my TWC connection does. Another computer on my TWC connection is running a traceroute monitor to the server and right now all the issues with latency are on the AT&T side. I suppose it could be an issue with the server receiving the data back from AT&T yet other traceroutes to servers in that area that do not use AT&T pass over the same return server for TWC and have no issues. This is why I am placing the blame on AT&T.

With the users you stated, while they do have higher ping counts on their server before AT&T that may also be a normal ping amount for them to have at that point. Many people play with a ping of around 200+ consistently. It is the spikes that are the issue and looking at many different traceroutes from other threads as well describing the same issue they all are latency spiking on the AT&T side when it happens. You need to see before and after to make the assumption you made which is why the more posted trace data the better.
76 Night Elf Druid
1160
Bump
85 Tauren Druid
7330
I really want a blue post on this because I wanna be positive that it is them and not me....

btw i played some rbgs today and didnt lag out at all while i was on. My tracert still shows its going into AT&T servers when I guess its not supposed to?
This topic is locked.

Please report any Code of Conduct violations, including:

Threats of violence. We take these seriously and will alert the proper authorities.

Posts containing personal information about other players. This includes physical addresses, e-mail addresses, phone numbers, and inappropriate photos and/or videos.

Harassing or discriminatory language. This will not be tolerated.

Forums Code of Conduct

Report Post # written by

Reason
Explain (256 characters max)

Reported!

[Close]