/v1/requests/current api not working from specific locations

Github issues are for bug reports. If this is a question around usage or understanding please use
Stack Overflow. https://stackoverflow.com/questions/tagged/uber-api

Library version: v0.9.1

Repro steps, stacktrace, screenshots:
We have integrated /v1/requests/current api in android application since last couple of years. It was working fine but recently we have encountered weird issue with this api - "api does not give response for users from India where as for USA users, this api works fine."
Logs -

java.net.SocketTimeoutException: timeout
at okhttp3.internal.http2.Http2Stream$StreamTimeout.newTimeoutException(Http2Stream.java:656)
at okhttp3.internal.http2.Http2Stream$StreamTimeout.exitAndThrowIfTimedOut(Http2Stream.java:664)
at okhttp3.internal.http2.Http2Stream.takeHeaders(Http2Stream.java:153)
at okhttp3.internal.http2.Http2Codec.readResponseHeaders(Http2Codec.java:131)
at okhttp3.internal.http.CallServerInterceptor.intercept(CallServerInterceptor.java:88)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:45)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:93)

Does Uber has made any changes in cloud backend OR any updates required in application?

Can you please guide me ?

I am aware that v1 apis are deprecated now but will be planning our app to upgrade to use v1.2 apis.

Expected Behavior:

Start by reproducing /v1/requests/current with rides-android-sdk v0.9.1 from India and the USA, using the reported OkHttp timeout as the symptom to investigate. Determine whether the difference comes from the backend or the Android application, and verify whether upgrading to the mentioned v1.2 APIs resolves it. Done requires a confirmed cause and a documented resolution or confirmation that the deprecated API cannot be fixed.