AUCTION ENDED EARLY OR SNIPE LATE and NETWORK ERROR

Wondering · Guest

Just lost an auction, snipe bid not entered (and was greater than the winning bid - I know, no guarantee, but my bid should have at least been entered). Reason / Status in Gixen web interface (snipe input with GDM) was AUCTION ENDED EARLY OR SNIPE LATE. I checked, and the auction closed at it's proper time, was NOT ended early, and there was a bid entered 13 seconds before scheduled close...

Lost the next auction 8 minutes later, again winning bid below my snipe bid, snipe not entered, and this time reason/status was NETWORK ERROR !?! Checked bid history, and no bid in last 20 minutes... is this an eBay network issue, or Gixen? I'm a free user (thanks Mario) and am wondering if it's time to sign up for Mirror service... Would this have prevented me loosing these two listings?

Wondering · Guest

OK, I started typing OP before Mario posted about the network issue, so sorry for that. Mario's post was after I lost the two auctions, though... wish I had known about the issue, especially for that second auction - I really wanted it!?! Sad

mario · Site Admin Joined: 03 Oct 2006 Posts: 7267

See http://www.gixen.com/forum/viewtopic.php?t=5732, I just posted an announcement on this.

Gixen main facility provider, corenetworks seems to be having some problems at the moment. I implemented a workaround, however what's missed is missed. Failures have been intermittent in the last three hours.

Gixen mirror server was not affected by this.

mario · Site Admin Joined: 03 Oct 2006 Posts: 7267

Gixen · Advertisements

delle · Guest

All of the auctions I set to snipe failed today (May 8th) due to a network error. I know this is a free service but I lost some very important items, and had I known this issue was an ongoing problem (I wish an announcement had been posted upon login), I would have used an alternate sniping service. Has this issue been resolved?

mario · Site Admin Joined: 03 Oct 2006 Posts: 7267

delle,

When I noticed the issue I implemented a workaround right away, so there was no time or point really to post an announcement. All affected snipes were in a three-hour window.

Yes, this is resolved now.

I don't want to give a sales pitch, but this is really what the mirror service is good for - when one site has an issue, the second one still executes.