Rank Tracker not Working.

[SammisBest]

That's all. It has not worked for last 3 days I believe. I use Google Chrome.

[Christy-Correll]

Hi, I am so sorry about this! Unfortunately, we are still experiencing intermittent issues with our tools as a result of DDoS attacks over the weekend. Moz engineers are working hard to resolve this. For status updates on all Moz products, please visit Moz Health. For details on the DDoS attacks against Moz and others, please read this article from _The New York Times - _ Tally of Cyber Extortion on Tech Companies Grows.

Thanks so much for your patience. We appreciate it!!

Kind Wishes,
Christy

[EGOL]

Wow.  Thanks for the update.   I'd like to see a WhiteBoard friday about this after its sorted out with graphics  on how DDoS are carried out and how they are deflected.  And, how you know its happening to you.

These guys must be pissants if they are only asking for a few hundred bucks.  Would be funny to see Mr Skinner point at the camera and say... "We didn't pay-off a $200 pissant and we will not pay you."

[SammisBest]

OK thank you for the update.

[Christy-Correll]

You are quite welcome, Sammie. Again, thanks so much for understanding. You rock!

[Christy-Correll]

That is a great suggestion, EGOL. I will definitely pass it on.

And this. "These guys must be pissants if they are only asking for a few hundred bucks.  Would be funny to see Mr Skinner point at the camera and say... "We didn't pay-off a $200 pissant and we will not pay you." Ha! No kidding, right??

[randfish]

Well, here's the complex thing - every time we share anything about the DDoS - on Twitter for example, or in the press (including when that NYTimes article was published), the DDoS crew hits us again. This weekend was insanely hard. Our tech ops team are staying up 30 hours in a row, missing meals, missing their families. It's pretty horrifying, and it's been going on for months.

It was only the first time they wanted a few hundred, then they emailed for thousands, now they don't even email anymore - they're clearly just out for revenge because we've been helping other companies to stop them using what we've learned.

My bias was to want to share that stuff, too. Unfortunately, if we do, not only do we risk more attacks, but we risk the attackers finding new vulnerabilities based on what we say we've done. It's an all around very sucky situation, and one of those times when we simply can't be as transparent as we'd like.

[randfish]

FYI - Rank Tracker appears to be back up and working for me. Not sure if we have the "all clear" from engineering, but you might want to give it another spin. I was able to successfully get the right rankings back on my queries just now.

[EGOL]

Thanks for the details.

Hang in there.  Tell staff we are cheering for them.

[Andy_Odom]

Here's the issue I'm having, and I'm not sure if it's related to the DDoS attacks. My campaign data doesn't appear when I'm using Chrome. The site loads, I can view the list of campaigns, and I'm even typing this in Chrome, but the actual data of my campaigns will not show. It's almost like there's some setting in Chrome blocking that, but I've done nothing to my browser settings. This is the same on my home MacBook Air and my work MacBook Pro. Any clue what might be causing this particular issue?

[Andy_Odom]

This post is deleted!

[randfish]

Hi Andy - never heard that one before... Very odd. I just looked in your account using my Chrome browser and your data looks fine to me, so my guess is that there's a setting in Chrome or possibly an extension that's causing the visibility problems. Unfortunately, browser troubleshooting isn't my specialty, but you might try installing Firefox or even Internet Explorer and seeing if you can see the data that way temporarily. In Chrome, you could try disabling extensions and/or doing an uninstall/reinstall (make sure you have another browser installed before you uninstall Chrome though or it will be a pain to re-download it).

Good luck!

[Andy_Odom]

Thanks Rand. I hadn't thought about a plug-in causing a conflict. I'll try disabling them and see if I can find the cause that way. It works fine in Safari, so that would make sense.