Streaming API down from OVH


#1

Hi,

It seems that the streaming API is currently down from OVH (one of the biggest dedicated server provider).

Ping is ok, however the TCP connection can not be established:

$ curl https://stream.twitter.com

tcpdump:

$ tcpdump -vvv -i any -n net 199.16.156.0/24
tcpdump: listening on any, link-type LINUX_SLL (Linux cooked), capture size 262144 bytes
09:52:28.123010 IP (tos 0x0, ttl 64, id 23201, offset 0, flags [DF], proto TCP (6), length 60)
    217.182.xx.xx.53038 > 199.16.156.20.443: Flags [S], cksum 0xeaa5 (incorrect -> 0x78ff), seq 995233847, win 29200, options [mss 1460,sackOK,TS val 191908502 ecr 0,nop,wscale 7], length 0
09:52:29.151276 IP (tos 0x0, ttl 64, id 23202, offset 0, flags [DF], proto TCP (6), length 60)
    217.182.xx.xx.53038 > 199.16.156.20.443: Flags [S], cksum 0xeaa5 (incorrect -> 0x77fd), seq 995233847, win 29200, options [mss 1460,sackOK,TS val 191908760 ecr 0,nop,wscale 7], length 0
09:52:31.167339 IP (tos 0x0, ttl 64, id 23203, offset 0, flags [DF], proto TCP (6), length 60)
    217.182.xx.xx.53038 > 199.16.156.20.443: Flags [S], cksum 0xeaa5 (incorrect -> 0x7605), seq 995233847, win 29200, options [mss 1460,sackOK,TS val 191909264 ecr 0,nop,wscale 7], length 0
09:52:35.199273 IP (tos 0x0, ttl 64, id 23204, offset 0, flags [DF], proto TCP (6), length 60)
    217.182.xx.xx.53038 > 199.16.156.20.443: Flags [S], cksum 0xeaa5 (incorrect -> 0x7215), seq 995233847, win 29200, options [mss 1460,sackOK,TS val 191910272 ecr 0,nop,wscale 7], length 0
09:52:43.391331 IP (tos 0x0, ttl 64, id 23205, offset 0, flags [DF], proto TCP (6), length 60)
    217.182.xx.xx.53038 > 199.16.156.20.443: Flags [S], cksum 0xeaa5 (incorrect -> 0x6a15), seq 995233847, win 29200, options [mss 1460,sackOK,TS val 191912320 ecr 0,nop,wscale 7], length 0
09:52:59.519291 IP (tos 0x0, ttl 64, id 23206, offset 0, flags [DF], proto TCP (6), length 60)
    217.182.xx.xx.53038 > 199.16.156.20.443: Flags [S], cksum 0xeaa5 (incorrect -> 0x5a55), seq 995233847, win 29200, options [mss 1460,sackOK,TS val 191916352 ecr 0,nop,wscale 7], length 0

#2

Got the same issue (of course, my servers are at OVH too)
curl on stream is working from providers in Belgium.

Twitter Status page shows performance issue on Stream (was Service disruption 10 minutes ago)
https://dev.twitter.com/overview/status


#3

I’ve created an EC2 proxy instance (irland) and use this proxy for all stream.twitter.com requests and it’s working well.

Seems to be more a routing problem at OVH side


#4

The last time I saw something like this reported was about 2 years ago, and it turned out to be related to a configuration change on the OVH side. I would suggest raising this with their support in the first instance.


#5

Hi Andy, thanks for your reply. I had a similar issue 5 years ago (on search.twitter.com) and finally was related to a routing problem on OVH side.
I’m currently in contact with them.
Thanks for your help

Pascal


#6

I experience the same problem…


#7

Sorry to hear that, unfortunately it is not something that we can currently do much about from our side.


#8

I’ve got the same problem, OVH TCP connection issues


#9

To all, there is now a ticket opened at OVH.

Currently I work with a proxy installed on an Amazon EC2 instance


#10

OVH is working on it https://twitter.com/ovh_support_fr/status/860140226836037632


#11

Thanks for sharing this update!


#12

Have you had any update from OVH on this?

I wonder if this is low on their priority list. :fearful:


#13

“admins are working on it”

let’s cross fingers


#14

For the others, @andypiper and OVH CEO are on the issue :slight_smile:
https://twitter.com/olesovhcom/status/860233713254363140


#15

On our radar but also note that this is (so far) a single host inbound issue. Thanks.


#16

Now solved by OVH CEO
https://twitter.com/olesovhcom/status/860236808902279168


#17

Super pleased to hear this thank you @zorrobiwan for keeping us informed!!


#18

Spam @oles by Twitter and mail succeeded :slight_smile:

Thx for your assistance too @andypiper. Have a great night


#19

You too glad this is resolved.


#20

So happy, I’m getting on a flight for a 8 day holiday in 6 hours and I was having palpitations.