This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox maxing out connection to 173.194.28.48 on it's own

  • 2 respostas
  • 1 has this problem
  • 1 view
  • Last reply by rhy7s

more options

I've been trying to figure out what's been using a whole lot of data over the past couple of months. There was quite a bit used while we were out today. Been watching resource monitor for a bit and have just seen Firefox start maxing out the connection to the Google IP 173.194.28.48 in a sustained fashion while just sitting there with one tab open. Does anyone know what Addon or feature would be communicating with that IP?

I've been trying to figure out what's been using a whole lot of data over the past couple of months. There was quite a bit used while we were out today. Been watching resource monitor for a bit and have just seen Firefox start maxing out the connection to the Google IP 173.194.28.48 in a sustained fashion while just sitting there with one tab open. Does anyone know what Addon or feature would be communicating with that IP?

Chosen solution

It does seem to have been NoScript, usage has plateaued since removing it.

Ler a resposta no contexto 👍 0

All Replies (2)

more options

Just looking around and have seen a few instances reported of the same behaviour, e.g. http://productforums.google.com/forum/#!topic/gmail/s5dwskbcCAQ & https://support.mozilla.org/en-US/questions/971122 - I'll keep an eye on it, had already removed NoScript which is implicated in the second link. (Edit: and I note was in use by the user in the first link as well).

rhy7s modificouno o

more options

Chosen Solution

It does seem to have been NoScript, usage has plateaued since removing it.