League of Legends Match History Site Does Not Work

I know.. I have to lolking everyone :(

its works but takes forever load pls fix

Blocked my Adblock (even uninstalled it) and it still doesn't work. Left the window on for about an hour and still doesn't work. Cleared my history, cookies, cache and that doesn't work either. I even tried Incognito mode and IT STILL DIDN'T WORK:

http://i844.photobucket.com/albums/ab9/tpirates/League%20of%20Legends%20Match%20History_zpsghx2tbhv.jpg

...I'm still wondering if half of these people who are proposing these solutions still experience the same problem which I do, even when they attempt their own proposed solution..!

It's been like that for quite some time, I figured it was discontinued or something.

Hi, webdeveloper here, I have tracked it down myself to a truncated Twig.js file. I think maybe you guys got a bad push somewhere or something corrupted on a cdn. It seems you load theses assets off of S3, so maybe check your buckets.

http://matchhistory.na.leagueoflegends.com/assets/1.0.19/lib/twig.js

that's the link to the truncated JS in question.

Here is the remote IP that it's being resolved to: 104.16.139.241

Please fix. Let me know if you need more info.

Yeh

when a 3rd party site has better service than you,feelsriotman

Thank you for saying this. I was gonna post but I was afraid I was the only one.

Your adblock is blocking it. Turn it off for the website that worked for me.

I asked about this a few days ago and they hadn't responded then so....

Mine works just fine. I can view mine and others right away.

Open up the match history and take a look at the developer tools (F12 in most browsers, or ctrl+shift+i in windows, cmd+shit+i in mac) see if it is similar to http://boards.na.leagueoflegends.com/en/c/help-support/MffEPIuO-match-history-not-functioning-properly?comment=00000000

Same here, really disappointing.

This has been a problem on and off. My Chrome extension may fix your issue. Original post.

Some folks are experiencing a 403 issue with AWS, in which case this extension won't fix the issue.

same issue