LC-202 PS4 please for the love of god help me

I have been on the phone with my ISP (comcast), Blizzard and Playstation 4 for 18+ hrs in the last 3 days trying to deal with this issue. I have used looking glass, port forwarding ( at least i think ), removed noise boxes, reset all routers ( even swapped one out ), unplugged all cords, uninstalled overwatch, removed my link gamed status from account, atttempted to try and have ISP type 1 or change my IPV6 to IPV4 and boht options they refused to help with. My neighbor has xfinity as well and i can log in just fine with no issue. PLEASE COMMUNITY HELP. . please do not hestitate with any help you may have.

Is your neighbor also playing Overwatch? And can you provide your WinMTR results here? Maybe it’s an issue on your local network. Use the </> icon to paste the results.

my neighbor is not. i am using their wifi and playing my account. I am on ps4 so how can i send the glass report from there? i have the photos from the ps4 on my phone.

I’m not sure if there is much troubleshooting we can do if it’s for someone else’s internet connection. Where are you connecting from? Are you in one of the locations having issues that people have been discussing in this forum? There are a lot of threads about the LC-202 error, and a stickied troubleshooting thread from the staff.

I am not sure. I have checked most posts i believe and i am not in B.C. where most seem to be. i am connected either via wifi or lan depending on method and in ILLINOIS usa

So to clarify, your Overwatch on PS4 works at the neighbor’s house but not at your house?

not their house just their wifi but yes. i can leave my ps4 connected to their wifi and play but as soon as i switch over to my wifi i get the error message

Oh ok, I understand now. Since it’s not likely to be a routing (across the country) issue if you can connect from your neighbor’s wifi, we’re probably looking at an issue with either your PS4 or your modem/router. What happened when you called Xfinity?

they blamed blizzard or playstation. i called playstation they had no issues since the eroor code was blizzard related in nature

Are you accessing the forums from a PC? Would you be able to provide the results of a WinMTR test? http://winmtr.net

tbh idk how. idk my full IP. do you want the pc with lan ip or ps4 with lan ip? sorry not the most savvy

|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
popeyes.hsd1.il.comcast.ne - 0 59 59 0 0 1 0
________________________________________________ ______ ______ ______ ______ ______ ______

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

You can use the </> icon and paste between them to include all of it.

dang ive never used half of these apps.

You don’t use your own IP in WinMTR, you use the IP of the server you’re connecting to. If you have those images I will take a look but you’ll have to upload them somewhere else and share a link.

TRACEROUTE:
traceroute to 73.45.251.133 (73.45.251.133), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.323 ms 0.298 ms 0.291 ms
2 37.244.22.3 (37.244.22.3) 0.628 ms 0.636 ms 0.712 ms
3 24.105.30.152 (24.105.30.152) 1.145 ms 1.154 ms 1.155 ms
4 137.221.66.2 (137.221.66.2) 1.569 ms 1.599 ms 1.670 ms
5 137.221.68.70 (137.221.68.70) 1.538 ms 1.546 ms 1.545 ms
6 137.221.68.34 (137.221.68.34) 1.125 ms 1.173 ms 1.134 ms
7 te-0-10-0-1-4-pe01.600wseventh.ca.ibone.comcast.ne (23.30.206.153) 1.243 ms 1.740 ms 1.711 ms
8 be-11545-cr02.losangeles.ca.ibone.comcast.ne (68.86.84.233) 1.834 ms 3.161 ms 3.117 ms
9 be-11015-cr02.sunnyvale.ca.ibone.comcast.ne (68.86.86.97) 10.214 ms 10.232 ms 10.231 ms
10 be-11020-cr01.champa.co.ibone.comcast.ne (68.86.84.10) 53.920 ms 53.930 ms 53.337 ms
11 be-12021-cr02.1601milehigh.co.ibone.comcast.ne (68.86.84.226) 53.304 ms 52.041 ms 52.002 ms
12 be-10521-cr02.350ecermak.il.ibone.comcast.ne (68.86.85.169) 52.340 ms 54.114 ms 54.078 ms
13 be-7922-ar01.area4.il.chicago.comcast.ne (68.86.91.166) 53.273 ms 52.844 ms 52.586 ms
14 be-123-rur02.homewood.il.chicago.comcast.ne (69.139.235.46) 53.954 ms 53.665 ms 53.647 ms
15 68.87.235.242 (68.87.235.242) 53.473 ms 53.490 ms 53.467 ms

31/07/2018 05:13:12 UTC

TRACEROUTE:
traceroute to 73.45.251.133 (73.45.251.133), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.299 ms 0.270 ms 0.266 ms
2 37.244.23.2 (37.244.23.2) 0.638 ms 0.668 ms 0.767 ms
3 24.105.62.150 (24.105.62.150) 1.206 ms 1.271 ms 1.350 ms
4 137.221.66.14 (137.221.66.14) 2.097 ms 2.135 ms 2.187 ms
5 137.221.69.68 (137.221.69.68) 2.118 ms 2.118 ms 2.120 ms
6 137.221.69.32 (137.221.69.32) 2.335 ms 1.609 ms 1.643 ms
7 te-0-11-0-0-3-pe01.350ecermak.il.ibone.comcast.ne (50.242.151.153) 1.239 ms 1.466 ms 1.447 ms
8 be-10563-cr02.350ecermak.il.ibone.comcast.ne (68.86.82.157) 2.601 ms 3.964 ms 3.940 ms
9 be-7922-ar01.area4.il.chicago.comcast.ne (68.86.91.166) 3.828 ms 3.403 ms 3.380 ms
10 be-123-rur02.homewood.il.chicago.comcast.ne (69.139.235.46) 3.591 ms 3.600 ms 3.612 ms
11 68.87.235.242 (68.87.235.242) 3.429 ms 3.361 ms 3.394 ms
12 c-73-45-251-133.hsd1.il.comcast.ne (73.45.251.133) 22.249 ms 25.482 ms 25.466 ms

31/07/2018 05:13:12 UTC

PING:
PING 73.45.251.133 (73.45.251.133) 56(84) bytes of data.
64 bytes from 73.45.251.133: icmp_seq=2 ttl=52 time=67.1 ms
64 bytes from 73.45.251.133: icmp_seq=3 ttl=52 time=65.4 ms
64 bytes from 73.45.251.133: icmp_seq=4 ttl=52 time=67.2 ms

— 73.45.251.133 ping statistics —
4 packets transmitted, 3 received, 25% packet loss, time 3002ms
rtt min/avg/max/mdev = 65.447/66.618/67.249/0.828 ms

31/07/2018 05:13:12 UTC

PING:
PING 73.45.251.133 (73.45.251.133) 56(84) bytes of data.
64 bytes from 73.45.251.133: icmp_seq=2 ttl=53 time=24.7 ms
64 bytes from 73.45.251.133: icmp_seq=3 ttl=53 time=21.2 ms
64 bytes from 73.45.251.133: icmp_seq=4 ttl=53 time=24.2 ms

— 73.45.251.133 ping statistics —
4 packets transmitted, 3 received, 25% packet loss, time 3003ms
rtt min/avg/max/mdev = 21.246/23.443/24.788/1.566 ms

31/07/2018 05:13:13 UTC

Do you also have the MTR results? Definitely seeing an issue here with the packet loss of 25%

MTR:
Start: Tue Jul 31 05:34:27 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0
2.|-- 37.244.23.130 0.0% 10 0.5 0.6 0.5 0.8 0.0
3.|-- 24.105.62.150 0.0% 10 1.1 1.0 0.8 1.1 0.0
4.|-- 137.221.66.10 0.0% 10 2.5 2.5 2.4 2.7 0.0
5.|-- 137.221.69.70 0.0% 10 2.4 2.6 2.3 3.8 0.3
6.|-- 137.221.69.34 0.0% 10 1.6 1.8 1.6 2.1 0.0
7.|-- te-0-11-0-0-2-pe01.350ecermak.il.ibone.comcast.ne 0.0% 10 2.2 2.3 2.2 2.5 0.0
8.|-- be-10563-cr02.350ecermak.il.ibone.comcast.ne 0.0% 10 3.2 3.5 3.0 4.0 0.0
9.|-- be-7922-ar01.area4.il.chicago.comcast.ne 0.0% 10 3.9 3.3 2.5 3.9 0.3
10.|-- be-123-rur02.homewood.il.chicago.comcast.ne 0.0% 10 4.3 4.3 4.2 4.5 0.0
11.|-- 68.87.235.242 0.0% 10 4.0 4.0 3.9 4.2 0.0
12.|-- c-73-45-251-133.hsd1.il.comcast.ne 0.0% 10 12.7 13.4 12.7 14.5 0.3

31/07/2018 05:34:27 UTC

MTR:
Start: Tue Jul 31 05:34:27 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0
2.|-- 37.244.22.131 0.0% 10 0.5 0.5 0.4 0.6 0.0
3.|-- 24.105.30.152 0.0% 10 1.1 1.1 1.0 1.2 0.0
4.|-- 137.221.66.6 0.0% 10 1.7 1.6 1.5 1.7 0.0
5.|-- 137.221.68.72 0.0% 10 1.4 6.0 1.4 47.3 14.5
6.|-- 137.221.68.34 0.0% 10 1.2 2.0 1.1 5.5 1.4
7.|-- te-0-10-0-1-4-pe01.600wseventh.ca.ibone.comcast.ne 0.0% 10 1.2 1.3 1.2 1.4 0.0
8.|-- be-11545-cr02.losangeles.ca.ibone.comcast.ne 0.0% 10 2.8 2.9 2.0 3.4 0.0
9.|-- be-11015-cr02.sunnyvale.ca.ibone.comcast.ne 0.0% 10 10.6 10.2 9.4 11.1 0.3
10.|-- be-11020-cr01.champa.co.ibone.comcast.ne 0.0% 10 53.8 53.3 52.2 53.9 0.0
11.|-- be-12021-cr02.1601milehigh.co.ibone.comcast.ne 0.0% 10 53.1 53.0 52.1 54.1 0.3
12.|-- be-10521-cr02.350ecermak.il.ibone.comcast.ne 0.0% 10 52.7 53.1 51.9 53.9 0.7
13.|-- be-7922-ar01.area4.il.chicago.comcast.ne 0.0% 10 52.9 53.6 52.6 54.5 0.5
14.|-- be-123-rur02.homewood.il.chicago.comcast.ne 0.0% 10 53.5 53.6 53.4 53.8 0.0
15.|-- 68.87.235.242 0.0% 10 53.4 53.4 53.3 53.5 0.0
16.|-- c-73-45-251-133.hsd1.il.comcast.ne 0.0% 10 69.8 64.9 62.4 70.6 3.4

31/07/2018 05:34:27 UTC

this is from my pc connected to my lan

If you do the other tests from your PC connected to the LAN and see 0% packet loss, then we have narrowed it down to an issue with your wifi. Can you connect the PS4 via cable also? It could be that your router is not functioning properly, and if the cable also doesn’t work, there could be a problem with the cable itself or the port you’re plugging it into.