#1

So weird. In the last few days, a few users reported that they see this screen when they click “Sign in with Twitter”.

error
error1920×1080 114 KB

Here are some info I gathered:

  • When I change the URL from api.twitter.com/oauth/... to twitter.com/oauth/..., the problem goes away.
  • It only happen for users from India (as far as I know). I confirmed this by using a VPN to India and test it myself. Here are the screenshots:

with-api-india
with-api-india1314×975 67 KB

no-api-india
no-api-india1314×975 63.9 KB

(as you can see the URL is exactly the same except for the api. part)

This affect all Twitter apps (that use “api.twitter.com/oauth”), not just my app.

According to the API document, api.twitter.com/oauth should be the correct URL. However, because of this issue, I’m redirecting my users to twitter.com/oauth for now.

Can we have more info on why is this happening?

Thanks.

PS: :wave: if you are a developer building apps/SaaS with Twitter API, join my Twitter Makers community, where I first shared about this issue: Slack

8 Likes
Error authorizing to Twitter api 1.0. Getting a 401 error (with the json response error being 32: Could not authenticate you.")
Request_token 404 response with Poodle on a chair?
#2

maybe related:

1 Like
#3

Some more relevant reports:

#4

I’ve also had several users report the same problem. The ones whose location I got were in India, so it might be some kind of localised issue.

#5

We’ve also started getting reports of this, eg Twitter signup 404s in India · Issue #1192 · snarfed/bridgy · GitHub

#6

I have a same issue at Japan.
during to make a WPF application with CoreTweet.

#7

Same Issue switched to https//twitter.com… for now. Couldn’t find any solution used different libraries in node.js to make a request nothing seemed to work. I was doubting my code. This post helped a lot so thankyou. Never thought it will be annoying to see a dog sitting on a couch .

#8

I’m also having the same issue here in France, with a .NET v4.8 application :frowning:

#9

several users report the same problem whose location we got were from India

#10

I’ve just had my first report of this too. No changes on my end, and user appears to be coming from India.

I have also confirmed this using a VPN and trying to sign in from a location in India.

CC: @i_am_daniele @andypiper

#11

Thank you all for reporting - This is on our radar and the team is actively investigating. Very sorry for any inconvenience.

2 Likes
#12

Now twitter.com is down :sweat_smile:

CleanShot 2022-05-10 at 08.05.06
CleanShot 2022-05-10 at 08.05.061714×1253 116 KB

2 Likes
#14

Same here, tried edge and chrome
Sydney

image
image1569×962 108 KB

1 Like
#15

image
in brazil too

#16

Same here, The Netherlands.

#17

Same problem here. In Turkey

#18

We are facing the same problem in Sweden and US. And currently, we are getting too many complaints from our Twitter account users. We would be happy to get a response about the issue asap.

#19

Is there any solution for this? I am unable to log in using firebase

#20

Thank you for the reports and apologies for the frustration. We understand that this has an impact on your apps. This is under active investigation. Unfortunately we are not able to share an ETA to resolution at this time.

The API Status page has an item you can subscribe to for updates.

3 Likes
.Net apps getting 404's for oauth endpoints
#21

We are currently working on a remediation, hopefully this should start to resolve from this point. Please let us know if you are observing a change in success rates.

3 Likes