Welcome to the Forum Archive!

Years of conversation fill a ton of digital pages, and we've kept all of it accessible to browse or copy over. Whether you're looking for reveal articles for older champions, or the first time that Rammus rolled into an "OK" thread, or anything in between, you can find it here. When you're finished, check out the boards to join in the latest League of Legends discussions.

GO TO BOARDS


The Reason FIOS is screwing up LoL for us in the NorthEast

12
Comment below rating threshold, click here to show it.

Callyswag

Member

05-31-2013

I did some research and found out that the reason we can't play/ log in is because the hot days is screwing with the transit connector. We can only hope Verizon will upgrade it in one day. Well **** this kinda pisses me off the one day I have 10 hours to play I can't play...


Comment below rating threshold, click here to show it.

Karma Killed You

Junior Member

05-31-2013

Nice job doing the research. Aye I agree, I can really get some playing time in today, but sadly can't connect.


Comment below rating threshold, click here to show it.

ski107

Member

05-31-2013

Source on this? I find it hard to believe that heat would affect major telecom infrastructure. The fiber transit lines would need 300+ degrees before damage would occur and all the major equipment is in cooled datacenters.

It is possible that there was a power outage in a datacenter as a result of the heat and air conditioners, but it's unlikely that there wouldn't be UPS behind that.


Comment below rating threshold, click here to show it.

Callyswag

Member

05-31-2013

http://www.broadbandreports.com/forum/r28294754-Northeast-Lag-in-League-of-Legends-online-video-game


Comment below rating threshold, click here to show it.

ski107

Member

05-31-2013

Quote:
Callyswag:
http://www.broadbandreports.com/forum/r28294754-Northeast-Lag-in-League-of-Legends-online-video-game


With respect, that mentions nothing about heat. The "transit connection" is the connection between Verizon's Networks and the backbone, which then routes towards the West Coast before dropping off on Riot's network. There is no chance that heat would affect that.

That backbone connection is most likely the issue, but it's not due to heat.


Comment below rating threshold, click here to show it.

Smartcow

Senior Member

05-31-2013

The point is Verizon is bad and prevents us from playing League, or in my case, makes me disconnect in the lobby and therefore lose me elo/lp


Comment below rating threshold, click here to show it.

ski107

Member

05-31-2013

My tracert makes it all the way to one of Internap'ss border routers in LA, then drops off:

C:\Users\ski>tracert 216.133.234.22 (this is the address of the pvp.net chat server and possibly other client-related functions)

Tracing route to 216.133.234.22 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 6 ms 7 ms L100.BSTNMA-VFTTP-137.verizon-gni.net
3 7 ms 6 ms 7 ms G11-0-6-1837.BSTNMA-LCR-08.verizon-gni.net [130.
81.139.220]
4 7 ms 7 ms 9 ms so-0-0-2-0.BOS-BB-RTR2.verizon-gni.net [130.81.2
9.254]
5 80 ms 79 ms 79 ms 0.so-7-0-0.XL4.LAX15.ALTER.NET [152.63.112.61]
6 80 ms 82 ms * POS7-0-0.GW3.LAX15.ALTER.NET [152.63.112.109]
7 87 ms 86 ms 86 ms internapGIGE-gw.customer.alter.net [157.130.236.
110]
8 82 ms 82 ms 84 ms border1.po1-20g-bbnet1.lax010.pnap.net [216.52.2
55.13]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.


Comment below rating threshold, click here to show it.

Karma Killed You

Junior Member

05-31-2013

What I can't understand, is how would Verizon's backbone be underpar sort of speak. This started happening for me today, after this patch with Riot. I was fine yesterday and the day before, etc.

I find it interesting that the day of a patch, and the day these errors occur, are on the same day.


Comment below rating threshold, click here to show it.

ski107

Member

05-31-2013

Quote:
Cokedajoke:
What I can't understand, is how would Verizon's backbone be underpar sort of speak. This started happening for me today, after this patch with Riot. I was fine yesterday and the day before, etc.

I find it interesting that the day of a patch, and the day these errors occur, are on the same day.


Eh, coincedences will happen. The few tracerts i've seen so far point to a major hub in LA with an issue:

8 82 ms 82 ms 84 ms border1.po1-20g-bbnet1.lax010.pnap.net [216.52.2
55.13]

Anything past that point is either dropped or comes back with several seconds of latency. This is a major backbone owned by Internap, so Verizon might not even have anything they can do either.


Comment below rating threshold, click here to show it.

Chyeaaaaaa

Senior Member

05-31-2013

jeez no wonder i cant log into either of my accts. was starting to think i got banned or something lol


12