Potential Teksavvy British Columbia Issue - LC-202 on PS4

Since a few days ago I can no longer log into the game. Tried everything including factory reset of my router and reinstalling the game.

Hey Iā€™m in the same boat. Itā€™s been happening for about 3 days for me. I tried disconnecting and reconnecting my blizzard account, resetting routers and modems, power cycles and reinstalling the game. Whatā€™s extra weird is a different user on my PS4 can access the game just fine.

1 Like

I have also been having an LC-202 issue since Thursday (pretty sure). I have not been able to log in since then. The ONLY thing I havenā€™t tried yet is reinitializing the PS4. The only reason I havenā€™t done that yet is because I need to get a USB drive to back up my capture galleryā€¦ I doubt that is going to work thoughā€¦ I have just about given up.

I connected to my cellā€™s wifi data and was able to connect. Which would mean itā€™s my ISP. But what would I tell them to fix the issue? In the past I usually wait a day and itā€™s fine, this time itā€™s been about 4 days.

Donā€™t suppose any of you use teksavvy as your internet provider? Maybe we have the same provider and they switched some settings?

If anyone does find a resolve please respond for the rest of our sanities.

Iā€™m having the same issue. I just switched to Teksavvy and Iā€™m not longer able to start overwatch. It gets stuck at ā€˜entering gameā€™ on the initial loading page. Iā€™ve tried every conceivable option to fix this except actually reaching out to teksavvy. I feel like that is the only remaining solution. I have created a ticket with blizzard and they are aware of this issue but state that it only appears to be teksavvy customers experiencing this issue. If i find a solution, ill post it here.

You hit the nail on the head Spline. All of you in this thread as of this posting are on Teksavvy in BC. The fact that using a mobile hotspot through nicanorā€™s phone worked tells me thereā€™s something strange going on, possibly ISP level. Do any of you have a PC version of the game as well which has similar connection issues?

I donā€™t have a overwatch pc version, but I can confirm that heroes of the storm works fine on pc

I donā€™t have a PC copy unfortunately, but is there anything I could ask teksavvy to switch to be able to play?

i started a reddit post for it also https://www.reddit.com/r/teksavvy/comments/8xgtxf/overwatch_ps4_servers_are_being_blocked_by/

they are usually pretty good about responding to /r/teksavvy posts

Unfortunately with consoles thereā€™s not much data we can gather from our end to be certain of whatā€™s going on. Iā€™m checking some things out on my end now, but I canā€™t yet tell you what to do to help work around or fix the issue. Can we have you all try running the looking glass from your console and post the results here? Thatā€™ll at least let us know if thereā€™s a problem on the path back from our servers to your console.

Another useful bit of information would be exactly what date you first noticed the problem so I can compare our historical data for PS4 for you all.

Yes, I am on teksavvy in BC!!! At least I know for sure it is themā€¦ Doubt they will be able to help. Have had terrible experience with them.

Yes, here is mine. I had to remove some periods from links otherwise I could not post the results. Itā€™s also not possible to copy and paste text from the sony browser so everything is transcribed and might not be 100% accurate.

TRACEROUTE:

traceroute to 69.172.154.248 (69.172.154.248), 15 hops max, 60 byte packets
1 24.105.30.3 (24.105.30.3) 4.023 ms 4.030 ms 4.054 ms
2 ***
3 137.221.66.0 (137.221.66.0) 1.294 ms 1.360 ms 1.421 ms
4 137.221.68.70 (137.221.68.70) 1.267 ms 1.277 ms 1.279 ms
5 137.221.68.34 (137.221.68.34) 1.011 ms 1.620 ms 1.635 ms
6 ae10-1993.cr0-lax1.ip4.gtt net (69.174.5.21) 0.842 ms 0.827 ms 0.804 ms
7 xe-3-2-1.cr0-van1.ip4.gtt net (141.136.108.34) 33.708 ms 33.729 ms 33.737 ms
8 ip4.gtt net (69.174.15.210) 29.894 ms 29.907 ms 29.864 ms
9 76-10-191-14.dsl.teksawy com (76.10.191.14) 30.675 ms 30.855 ms 30.990 ms
10***
11***
12***
13***
14***
15***

10/07/2018 02:10:51 UTC

PING:
PING 69.172.154.248 (69.172.154.248) 56(84) bytes of data.

ā€”69.172.154.248 ping statistics ā€”
4 packets transmitted. 0 received. 100% packet loss, time 2998ms

MTR:

Start: Tue Jul 10 02:10:51 2018 Blizzard 1.|ā€“24.105.30.3 0.0% 10 0.8 0.7 0.5 1.2 0.0
2.|-??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3.|ā€“137.221.66.0 0.0% 10 1.5 1.4 1.2 1.5 0.0
4.|ā€“137.221.68.70 0.0% 10 7.0 1.8 1.2 7.0 1.8
5.|ā€“137.221.68.34 0.0% 10 1.1 1.1 0.9 1.6 0.0
6.|-ae10-1993.cr0-lax1.ip4.gtt net 0.0% 10 1.0 1.0 0.9 1.6 0.0
7.|-xe-3-2-1.cr0-van1.ip4.gtt net 0.0% 10 30.4 30.7 30.3 32.9 0.7
8.|ā€“ip4.gtt.net 0.0% 10 29.9 36.3 29.9 69.0 13.6
9.|ā€“76-10-191-14.dsl.teksawy.com 10.0% 10 30.7 30.9 30.5 31.8 0.4
10.|-??? 100.0 10 0.0 0.0 0.0 0.0 0.0

Using Battlenet Authentication as service for below.

MTR:
Start: Tue Jul 10 02:43:16 2018 Blizzard 1.|-- 24.105.30.2 0.0% 10 0.6 0.6 0.5 0.9 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3.|-- 137.221.66.4 0.0% 10 1.4 1.4 1.3 1.4 0.0
4.|-- 137.221.68.72 0.0% 10 1.2 1.2 1.1 1.6 0.0
5.|-- 137.221.68.34 0.0% 10 0.9 1.8 0.9 9.2 2.5
6.|-- ae10-1993.cr0-lax1.ip4.gtt net 0.0% 10 0.8 1.0 0.8 2.0 0.0
7.|-- xe-3-2-1.cr0-van1.ip4.gtt net 0.0% 10 30.4 30.6 30.3 31.3 0.0
8.|-- ip4.gtt net 0.0% 10 30.0 34.6 29.9 59.3 9.3
9.|-- 76-10-191-158.dsl.teksavvy com 0.0% 10 30.5 31.2 30.5 32.6 0.6
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

10/07/2018 02:43:16 UTC

TRACEROUTE:
traceroute to 69.172.162.123 (69.172.162.123), 15 hops max, 60 byte packets
1 24.105.30.2 (24.105.30.2) 1.211 ms 1.222 ms 1.232 ms
2 * * *
3 137.221.66.4 (137.221.66.4) 1.317 ms 1.386 ms 1.455 ms
4 137.221.68.72 (137.221.68.72) 1.224 ms 1.233 ms 1.234 ms
5 137.221.68.34 (137.221.68.34) 1.009 ms 1.032 ms 1.034 ms
6 ae10-1993.cr0-lax1.ip4.gtt net (69.174.5.21) 0.826 ms 0.791 ms 0.776 ms
7 xe-3-2-1.cr0-van1.ip4.gtt net (141.136.108.34) 30.297 ms 30.323 ms 30.284 ms
8 ip4.gtt net (69.174.15.210) 29.966 ms 29.963 ms 29.961 ms
9 76-10-191-158.dsl.teksavvy com (76.10.191.158) 30.595 ms 30.661 ms 31.939 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

10/07/2018 02:40:51 UTC

Ping is %100 packet loss. I ran looking glass on my Android phone but same result on PS4 and my PC.

If I select OW as service;
MTR - same but just a few more lines.
traceroute - I only get *** @ line 15
Ping - Still %100 packet loss.

My problem started somewhere around July 4th, give or take a day.

Iā€™ve had that exact issue since July 5th.
I was on the phone with blizzard and Teksavvy for hours over the weekend trying to figure this out on both sides.
They initially said it was my router, then said it was my modem so Iā€™ve got one in the wayā€¦

Funny thing though is I know they are doing an update as Iā€™m writing this, and their supposed to end it in 30min. I tried logging in and I didnā€™t get LC-202 anymore, but BC-101 (I think), and now I am getting just ā€œError, Disconnectedā€.

Iā€™ll wait out until 7pm and update the thread to see if anything changed.

the Ping is going to be at 100% loss because you have to change a response setting through your router. Itā€™s a little complicated to understand/explain, but I mentioned that to the ISP and they were able to change it easily (not that it made a difference in trying to connect).

add me to the list - on Teksavvy in BC - dropped service last Thursday tried everything - the issue is involved in authentication being blocked

I spoke again to TekSavvy and theyā€™re doing a bunch of deeper tests. I should get a call back or email today. Only think to do right now is waitā€¦

Thanks for the update.