General API slowness

candsl · 2016-10-24T16:14:08.567Z

I have my application and recently after DDoS all twitter API calls become much slower.
Sometimes cal to followers/ids takes 5 seconds.
And users/lookup also reaches 8 seconds.
Getting direct messages also takes long time.

Please note this is just examples and such slow responses happening very frequently.
Please note this has nothing to do with accounts as same accounts worked much faster before, and response times for these accounts varies lately as well.

My general experience now that all is running almost 3 times slower.
Any known issues with Twitter APIs ?

andypiper · 2016-10-24T16:24:29.237Z

There are no known issues with the REST API that I’ve heard of - there appear to be some issues with the Streaming API. However, as you reference, there was a recent DDoS that affected multiple services (including Twitter), so it is possible that there are ongoing shakeout issues. Apologies if you’re affected by that.

candsl · 2016-10-26T00:47:15.068Z

I found older thread REST API timeout which is exactly what I’m experiencing. All people saying it suddenly resolved, no one did anything.

I wonder if I the only one impacted or other people as well.
I tried to do ping from my server to api.twitter.com and at the same time to google.com
The ping times out on api.twitter.com time to time, but never on google. That makes me think that my server is fine.

Also I run trace:

tracert api.twitter.com

Tracing route to api.twitter.com [199.16.156.8]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms 216.105.85.198
2 <1 ms <1 ms <1 ms 10.77.77.2
3 1 ms <1 ms <1 ms 204.101.4.49
4 13 ms 13 ms 13 ms agg1-toronto47_9-1-0.net.bell.ca [64.230.151.161]
5 18 ms 13 ms 16 ms tcore3-toronto47_xe-0-0-4-0_core.net.bell.ca [64.230.161.121]
6 15 ms 14 ms 14 ms NEWCORE1-CHICAGOCP_so3-0-0-0.net.bell.ca [64.230.186.126]
7 33 ms 12 ms 14 ms bx5-chicagodt_xe-0-0-3_0.net.bell.ca [64.230.186.106]
8 13 ms 13 ms 26 ms eqix-ch1.twitter.com [206.223.119.231]
9 * * * Request timed out.
10 32 ms 32 ms 31 ms 199.16.156.8

Trace complete.

And on hop #9 as you can see there is timeout. Which makes me think the problem is on twitter network.