We are experiencing a number of issues at the moment which are preventing
the API and website from operating correctly. You can read more on this
mailing list thread [1] and stay up to date with progress by checking
http://status.twitter.com

Best,
Matt

1.
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/7d4e73b85f6d9174/6b8629833b3b4ea2#6b8629833b3b4ea2

On Mon, Jul 19, 2010 at 9:46 PM, Adam Loving <adamlov...@gmail.com> wrote:

> I am also currently seeing the "Something is technically wrong."
> response on calls to https://api.twitter.com/oauth/access_token
>
>
>
> On Jul 19, 8:04 pm, akaii <chibiak...@gmail.com> wrote:
> > We're experiencing problems with Twitter's OAuth login. After the
> > "Redirecting you back to your application..." page, we get a 500
> > error:
> >
> > "Internal Server Error
> >
> > The server encountered an internal error or misconfiguration and was
> > unable to complete your request.
> >
> > Please contact the server administrator, y...@example.com and inform
> > them of the time the error occurred, and anything you might have done
> > that may have caused the error.
> >
> > More information about this error may be available in the server error
> > log."
> >
> > Is there anything wrong with Twitter's services at the moment? This
> > started around 12-14 hours prior to this mail (10pm Tokyo time). The
> > API status page indicates nothing is wrong though.
>



-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

Reply via email to