UPDATES On Connection Issue With Rivals

[Tango Two]

We've had a network partner make some changes that might affect this issue.

Looks like this might have worked, which means the issue is a network problem in a layer above Rivals, which is why it's impacting other Yahoo properties. We have some ability to route Rivals around that, which is why forums is now working, however we can't as easily do the same for the article side of the site, nor do we have any control over the other Yahoo products.

We are preparing a summary to pass to upstream network providers in the hopes one of them finds themselves to be the origin of this block list.

We think we may have found the service provider with the block and they've removed it, so everything should work now (Rivals content, techcrunch, engadget, etc)

 

[Tango Two]

If anyone is still having an issue let me know I'll pass it along.

 

[satnom]

GO RU

 

[Knight Shift]

GO RU

Yahoo!

 

[UMRU]

We've had a network partner make some changes that might affect this issue.

Looks like this might have worked, which means the issue is a network problem in a layer above Rivals, which is why it's impacting other Yahoo properties. We have some ability to route Rivals around that, which is why forums is now working, however we can't as easily do the same for the article side of the site, nor do we have any control over the other Yahoo products.

We are preparing a summary to pass to upstream network providers in the hopes one of them finds themselves to be the origin of this block list.

We think we may have found the service provider with the block and they've removed it, so everything should work now (Rivals content, techcrunch, engadget, etc)

Logged on with no problem - first time since December. Thanks!

 

[Leonard23]

We've had a network partner make some changes that might affect this issue.

Looks like this might have worked, which means the issue is a network problem in a layer above Rivals, which is why it's impacting other Yahoo properties. We have some ability to route Rivals around that, which is why forums is now working, however we can't as easily do the same for the article side of the site, nor do we have any control over the other Yahoo products.

We are preparing a summary to pass to upstream network providers in the hopes one of them finds themselves to be the origin of this block list.

We think we may have found the service provider with the block and they've removed it, so everything should work now (Rivals content, techcrunch, engadget, etc)

Nice work finally getting a tech to dig in and uncover the issue. Everything works now, and honestly loads much faster than ever before.

 

[mdk01]

If anyone is still having an issue let me know I'll pass it along.

Yes. Phone OK, desktop Edge a no go

 

[cappy95]

Desktop and phone now working....first time since the Pinstripe Bowl so thank you!

 

[mdh2003]

We've had a network partner make some changes that might affect this issue.

Looks like this might have worked, which means the issue is a network problem in a layer above Rivals, which is why it's impacting other Yahoo properties. We have some ability to route Rivals around that, which is why forums is now working, however we can't as easily do the same for the article side of the site, nor do we have any control over the other Yahoo products.

We are preparing a summary to pass to upstream network providers in the hopes one of them finds themselves to be the origin of this block list.

We think we may have found the service provider with the block and they've removed it, so everything should work now (Rivals content, techcrunch, engadget, etc)

Working for me too!

Thanks to everyone that kept pushing this to a solution, at least for the forums.

 

[ClassOf02]

It’s nice to be back.

 

[Tango Two]

Another update:

Rivals network is typically reached through a couple of internet 'edge' layer services, intermediate service providers that route traffic and do stuff like block malicious activity, cache content to speed it up, etc.

Apparently one of those layers above us had reacted to a very aggressive attack in December by auto-blocking a large (but not comprehensive) list IP addresses, most originating from the northeast.

My guess is this attack was highly distributed across a bunch of ISPs intentionally to try to avoid such firewall countermeasures, so it impacted a bunch of seemingly random end-users.

Now that the provider has removed their blocks, we're about to revert our original temporary fix (the one that got TKR forums back online originally for impacted folks) because it should be superfluous now.

 

[GL113]

If anyone is still having an issue let me know I'll pass it along.

Still having an issue. Using Chrome no problem there.

 

[kupuna133]

Desktop worked yesterday afternoon is back out.

I get an “oops” message.

 

[RU_FML]

Never had an issue until Wednesday. Can access on my phone but not my laptop or desktop, both running Chrome.

 

[PSAL_Hoops]

Issue fixed! Thank you

 

[RUGuitarMan]

Yes, I can now access the site without turning off the WI FI.

 

[yesrutgers01]

All of my access is back- iPhone and laptop

 

[newell138]

I didn’t realize there was a problem

 

[mildone]

Appears to still be working for me, post-revert.

 

[mildone]

Another update:

Rivals network is typically reached through a couple of internet 'edge' layer services, intermediate service providers that route traffic and do stuff like block malicious activity, cache content to speed it up, etc.

Apparently one of those layers above us had reacted to a very aggressive attack in December by auto-blocking a large (but not comprehensive) list IP addresses, most originating from the northeast.

My guess is this attack was highly distributed across a bunch of ISPs intentionally to try to avoid such firewall countermeasures, so it impacted a bunch of seemingly random end-users.

Now that the provider has removed their blocks, we're about to revert our original temporary fix (the one that got TKR forums back online originally for impacted folks) because it should be superfluous now.

Hm.

One wonders how the “large (but not comprehensive) list of IP addresses” was compiled. We know that the affected IP addresses were pretty disparate, spanning multiple ISPs and regions.

I suspect we are not, and will not be, getting the full story. Which is fine, since the problem appears to be resolved. Didn’t expect the full story given it seemed security-related (filtering) almost right from the start.

I still wonder if it somehow involved the Nuts troll.

 

[kupuna133]

PC still out for me. No issues with phone access.

 

[DJ Spanky]

Appears to still be working for me, post-revert.

Damn!