Since yesterday my download speeds using SabNZB 07.1.6 have been about 1MB/s or less, they should be and always are between 2.5-3.0MB/s I have no idea why they are now so slow, but no amount of rebooting my Mac, restarting SabNZB or resetting my internet connection fixes the problem. My ISP is not throttling me, is this a Giganew issue or what?
Any help or suggestions would be appreciated, my download speeds are now sitting at 180KB/s
I am running the latest version of Mavericks 10.9.2 and before yesterday everything was fine, nothing changed in software or hardware, this just starting happening out of the blue.
AM
Download speeds terribly slow
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Re: Download speeds terribly slow
Are these older downloads?
They can be slower on Giganews.
They can be slower on Giganews.
-
ashman1970
- Newbie

- Posts: 3
- Joined: March 15th, 2014, 11:58 am
Re: Download speeds terribly slow
When you say older, what do you mean? These downloads are no older then 52 weeks, some only a few weeks, some hours old, there is no rhyme or reason to it.
Re: Download speeds terribly slow
Are you using WiFi or a wired connection?
WiFi not recommended.
Something else to try is a full queue repair (Status page).
WiFi not recommended.
Something else to try is a full queue repair (Status page).
-
ashman1970
- Newbie

- Posts: 3
- Joined: March 15th, 2014, 11:58 am
Re: Download speeds terribly slow
I always only use wired connections. Problem is resolved now, seems it was a newsgroup provider issue, thanks.
