Sorry to hear that. We appear to have a client-side caching bug (ironic!)
Can you try refreshing on the 404 page and see if you have access now?