3 ms·
Think this was due to the uptick in traffic - scaled up the heroku processes to accomodate. Should be ok now!
by neon 14y ago
Think this was due to the uptick in traffic - scaled up the heroku processes to accomodate. Should be ok now!
- saiko-chriskun 14y agoI don't think so I'm getting a very similar issue.
- neon 14y agoStrange. Many submissions have gone through ok - looking into it now.
- saiko-chriskun 14y agochrome's request dump: http://scrib.in/e23e9s http://scrib.in/e23e9s
- corroded 14y agoI'm still getting the 500 error as of now
- lobo_tuerto 14y agoI'm seeing the 500 Internal Server Error message "We're sorry, but something went wrong." too.