Just saw this thread. Honestly, the Cupshe site architecture is always a bit glitchy during high-traffic events like this, which explains your 404 err...