Beck38
02-19-2014, 08:50 PM
I use a simple (bottom/cheapest) Giganews account to keep an eye on things.
Today, I started getting 'net work read error' from their US plant on every newsgroup I tried to update headers on; interestingly, the EU plant was working just fine (if a little slower from the other side of the planet, to be expected).
Giganews initial response, 'we're working fine'. Right. Well, they're still looking at it so I'll give them some time to 'wake up' and actually test some things out since they initially said I was transferring data (and indeed I was, from the EU plant but not the US one). I wonder if they have outsourced their service staff to the Dutch or they 'assume' that folks are all using the EU plant by 'default' or something.
Anyway, all just goes to prove (again) that the 'high priced spread' is nowhere near perfect in their operation and do suffer crap outs from time to time. :w00t::w00t::w00t:
Some update: it appears to be 'group' affecting, in that many are being affected but some are not. Very interesting! So, it isn't my newsreader (Newsrover) or any other setting.
MORE updates: They must/might be doing something, groups that were returning the 'network read error' are now working. Maybe I'll see some of those groups I found were working before, now going bad. (!) Okay. like the thread title says, even Giga screws up!
Final report: Getting close to around 12 hours since I first noticed this, and as of now, things have settled down in that the main/popular groups (like a.b.blu-ray, and a.b.dvd9 for example) have both been 'fixed'. Some others, like a.b.teevee, that maybe were never affected (who knows, my figures aren't that fast) are still okay.
Don't have any idea why this happened, I just tripped across it kinda by accident.
Today, I started getting 'net work read error' from their US plant on every newsgroup I tried to update headers on; interestingly, the EU plant was working just fine (if a little slower from the other side of the planet, to be expected).
Giganews initial response, 'we're working fine'. Right. Well, they're still looking at it so I'll give them some time to 'wake up' and actually test some things out since they initially said I was transferring data (and indeed I was, from the EU plant but not the US one). I wonder if they have outsourced their service staff to the Dutch or they 'assume' that folks are all using the EU plant by 'default' or something.
Anyway, all just goes to prove (again) that the 'high priced spread' is nowhere near perfect in their operation and do suffer crap outs from time to time. :w00t::w00t::w00t:
Some update: it appears to be 'group' affecting, in that many are being affected but some are not. Very interesting! So, it isn't my newsreader (Newsrover) or any other setting.
MORE updates: They must/might be doing something, groups that were returning the 'network read error' are now working. Maybe I'll see some of those groups I found were working before, now going bad. (!) Okay. like the thread title says, even Giga screws up!
Final report: Getting close to around 12 hours since I first noticed this, and as of now, things have settled down in that the main/popular groups (like a.b.blu-ray, and a.b.dvd9 for example) have both been 'fixed'. Some others, like a.b.teevee, that maybe were never affected (who knows, my figures aren't that fast) are still okay.
Don't have any idea why this happened, I just tripped across it kinda by accident.