[twitter-dev] Re: Problems Connecting to the API

2009-10-19 Thread Rich

We're getting problems on the iPhone clients again, it looks like the
old 200 error might have cropped up again of serving HTML instead of
XML too.

On Oct 18, 4:10 pm, Michael Steuer mste...@gmail.com wrote:
 I only have two endpoints to test from. Hosted: fails. Home DSL: no  
 problem. I have several iPhone clients, but I'm bot sure if they're  
 proxies or connect to the API directly...

 On Oct 18, 2009, at 7:56 AM, John Kalucki jkalu...@gmail.com wrote:



  And here's the next question:

  Is anyone having trouble from non-service, non-hosted endpoints. In
  other words, problem from home ISPs and desktop clients?

  -John Kalucki
 http://twitter.com/jkalucki
  Services, Twitter Inc.

  On Oct 18, 7:55 am, John Kalucki jkalu...@gmail.com wrote:
  OK. I think we have enough traceroutes for now. Thanks for sending
  them in!

  If we need more datapoints or information, I'll update this thread.

  On Oct 18, 7:14 am, John Kalucki jkalu...@gmail.com wrote:

  I don't see any operational issues from here, but I'm not an
  operational guy. At first glance the system looks fine, and the
  operational team isn't in response mode. This is puzzling.

  Seems like a connectivity issue upstream from twitter. At lest a few
  developers: please send a traceroute to this list. Also, if you  
  aren't
  timing out, but rather are getting an HTTP error, send the response
  headers. After say 4 or 5 responses, they'll probably have enough  
  info
  to triage this.

  -John Kaluckihttp://twitter.com/jkalucki
  Services, Twitter Inc.

  On Oct 18, 6:40 am, Dewald Pretorius dpr...@gmail.com wrote:

  Does anyone else have problems connecting to the API at the moment
  (Sunday morning October 18)?

  Dewald


[twitter-dev] Re: Problems Connecting to the API

2009-10-19 Thread Dewald Pretorius

I've also been seeing intermittent connection refuses and really very
slow performance at times today.

Dewald

On Oct 19, 3:13 pm, Michael Steuer mste...@gmail.com wrote:
 Hi All,

 While it's not complete unreachability like yesterday morning, I'm again
 experiencing, let's call it spotty reachability this morning... Requests
 time out or are really slow to complete... Anyone else seeing this?

 Thanks,

 Michael.

 On 10/19/09 9:45 AM, John Kalucki jkalu...@gmail.com wrote:



  Dewald, are you down, getting weird headers, or OK?

  If you can't connect at all, traceroutes are best. If you get weird
  headers, a copy of the header (and your IP address) are best.

  Thanks.

  On Oct 18, 7:23 am, Dewald Pretorius dpr...@gmail.com wrote:
  traceroute to twitter.com (168.143.162.100), 30 hops max, 40 byte
  packets
   1  81.b5.85ae.static.theplanet.com (174.133.181.129)  1.351 ms  1.439
  ms  1.464 ms
   2  et2-5.ibr01.hstntx1.theplanet.com (207.218.223.5)  0.198 ms  0.229
  ms  0.266 ms
   3  et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154)  0.444 ms
  et3-2.ibr02.hstntx1.theplanet.com (70.87.253.157)
  0.224 ms et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154)  0.466 ms
   4  et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58)  0.519 ms
  et1-2.ibr02.hstntx2.theplanet.com (70.87.253.169)  0
  .454 ms  0.522 ms
   5  xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5)  167.161 ms
  167.045 ms  167.206 ms
   6  xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228)  1.185 ms
  1.164 ms  1.180 ms
   7  p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129)  6.424
  ms  6.331 ms  6.358 ms
   8  po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74)  6.400 ms
  6.451 ms  6.489 ms
   9  * * *

  --

  traceroute to twitter.com (168.143.162.116), 30 hops max, 40 byte
  packets
   1  81.b5.85ae.static.theplanet.com (174.133.181.129)  0.387 ms  0.432
  ms  0.475 ms
   2  et2-5.ibr01.hstntx1.theplanet.com (207.218.223.5)  0.211 ms  0.257
  ms  0.273 ms
   3  et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154)  0.472 ms
  et3-2.ibr02.hstntx1.theplanet.com (70.87.253.157)
  0.221 ms  0.249 ms
   4  et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58)  0.404 ms  0.466
  ms  0.553 ms
   5  xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5)  107.597 ms
  107.679 ms  107.742 ms
   6  xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228)  1.136 ms
  1.114 ms  1.035 ms
   7  p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129)  6.293
  ms  8.708 ms  6.335 ms
   8  po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74)  6.433 ms
  6.486 ms  6.535 ms
   9  * * *

  -

  traceroute to twitter.com (168.143.162.36), 30 hops max, 40 byte
  packets
   1  81.b5.85ae.static.theplanet.com (174.133.181.129)  0.429 ms  0.515
  ms  0.567 ms
   2  et2-5.ibr02.hstntx1.theplanet.com (207.218.245.5)  8.956 ms  8.986
  ms  9.024 ms
   3  et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58)  0.439 ms  0.493
  ms  0.546 ms
   4  xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5)  1.156 ms
  1.206 ms  1.254 ms
   5  xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228)  1.114 ms
  1.113 ms  1.131 ms
   6  p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129)  6.280
  ms  6.256 ms  6.717 ms
   7  po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74)  6.377 ms
  6.444 ms  6.499 ms
   8  * * *

  On Oct 18, 11:14 am, John Kalucki jkalu...@gmail.com wrote:

  I don't see any operational issues from here, but I'm not an
  operational guy. At first glance the system looks fine, and the
  operational team isn't in response mode. This is puzzling.

  Seems like a connectivity issue upstream from twitter. At lest a few
  developers: please send a traceroute to this list. Also, if you aren't
  timing out, but rather are getting an HTTP error, send the response
  headers. After say 4 or 5 responses, they'll probably have enough info
  to triage this.

  -John Kaluckihttp://twitter.com/jkalucki
  Services, Twitter Inc.

  On Oct 18, 6:40 am, Dewald Pretorius dpr...@gmail.com wrote:

  Does anyone else have problems connecting to the API at the moment
  (Sunday morning October 18)?

  Dewald


[twitter-dev] Re: Problems Connecting to the API

2009-10-19 Thread Arnaldo de Moraes Pereira
I'm also experiencing that today. It started to get slow several days ago,
but today is worse.

Regards,
Arnaldo

On Mon, Oct 19, 2009 at 5:58 PM, Dewald Pretorius dpr...@gmail.com wrote:


 I've also been seeing intermittent connection refuses and really very
 slow performance at times today.

 Dewald

 On Oct 19, 3:13 pm, Michael Steuer mste...@gmail.com wrote:
  Hi All,
 
  While it's not complete unreachability like yesterday morning, I'm again
  experiencing, let's call it spotty reachability this morning... Requests
  time out or are really slow to complete... Anyone else seeing this?
 
  Thanks,
 
  Michael.
 
  On 10/19/09 9:45 AM, John Kalucki jkalu...@gmail.com wrote:
 
 
 
   Dewald, are you down, getting weird headers, or OK?
 
   If you can't connect at all, traceroutes are best. If you get weird
   headers, a copy of the header (and your IP address) are best.
 
   Thanks.
 
   On Oct 18, 7:23 am, Dewald Pretorius dpr...@gmail.com wrote:
   traceroute to twitter.com (168.143.162.100), 30 hops max, 40 byte
   packets
1  81.b5.85ae.static.theplanet.com (174.133.181.129)  1.351 ms
  1.439
   ms  1.464 ms
2  et2-5.ibr01.hstntx1.theplanet.com (207.218.223.5)  0.198 ms
  0.229
   ms  0.266 ms
3  et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154)  0.444 ms
   et3-2.ibr02.hstntx1.theplanet.com (70.87.253.157)
   0.224 ms et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154)  0.466 ms
4  et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58)  0.519 ms
   et1-2.ibr02.hstntx2.theplanet.com (70.87.253.169)  0
   .454 ms  0.522 ms
5  xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5)  167.161 ms
   167.045 ms  167.206 ms
6  xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228)  1.185 ms
   1.164 ms  1.180 ms
7  p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129)  6.424
   ms  6.331 ms  6.358 ms
8  po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74)  6.400 ms
   6.451 ms  6.489 ms
9  * * *
 
   --
 
   traceroute to twitter.com (168.143.162.116), 30 hops max, 40 byte
   packets
1  81.b5.85ae.static.theplanet.com (174.133.181.129)  0.387 ms
  0.432
   ms  0.475 ms
2  et2-5.ibr01.hstntx1.theplanet.com (207.218.223.5)  0.211 ms
  0.257
   ms  0.273 ms
3  et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154)  0.472 ms
   et3-2.ibr02.hstntx1.theplanet.com (70.87.253.157)
   0.221 ms  0.249 ms
4  et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58)  0.404 ms  0.466
   ms  0.553 ms
5  xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5)  107.597 ms
   107.679 ms  107.742 ms
6  xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228)  1.136 ms
   1.114 ms  1.035 ms
7  p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129)  6.293
   ms  8.708 ms  6.335 ms
8  po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74)  6.433 ms
   6.486 ms  6.535 ms
9  * * *
 
   -
 
   traceroute to twitter.com (168.143.162.36), 30 hops max, 40 byte
   packets
1  81.b5.85ae.static.theplanet.com (174.133.181.129)  0.429 ms
  0.515
   ms  0.567 ms
2  et2-5.ibr02.hstntx1.theplanet.com (207.218.245.5)  8.956 ms
  8.986
   ms  9.024 ms
3  et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58)  0.439 ms  0.493
   ms  0.546 ms
4  xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5)  1.156 ms
   1.206 ms  1.254 ms
5  xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228)  1.114 ms
   1.113 ms  1.131 ms
6  p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129)  6.280
   ms  6.256 ms  6.717 ms
7  po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74)  6.377 ms
   6.444 ms  6.499 ms
8  * * *
 
   On Oct 18, 11:14 am, John Kalucki jkalu...@gmail.com wrote:
 
   I don't see any operational issues from here, but I'm not an
   operational guy. At first glance the system looks fine, and the
   operational team isn't in response mode. This is puzzling.
 
   Seems like a connectivity issue upstream from twitter. At lest a few
   developers: please send a traceroute to this list. Also, if you
 aren't
   timing out, but rather are getting an HTTP error, send the response
   headers. After say 4 or 5 responses, they'll probably have enough
 info
   to triage this.
 
   -John Kaluckihttp://twitter.com/jkalucki
   Services, Twitter Inc.
 
   On Oct 18, 6:40 am, Dewald Pretorius dpr...@gmail.com wrote:
 
   Does anyone else have problems connecting to the API at the moment
   (Sunday morning October 18)?
 
   Dewald




-- 
Arnaldo M Pereira


[twitter-dev] Re: Problems Connecting to the API

2009-10-19 Thread Ryan Rosario

I keep getting {request:/statuses/user_timeline.json?
user_id=TheUserIDcount=200,error:This method requires
authentication.}
when I try to pull a user's tweets. This never used to happen. Earlier
today I did not need to authenticate to do this.

Even when I pass my username and password, I still get this error:
curl -uMyUsername:MyPassword 
http://twitter.com/statuses/user_timeline.json?user_id=MyUserID\count=200
I keep getting {request:/statuses/user_timeline.json?
user_id=TheUserIDcount=200,error:This method requires
authentication.}

Did something change in the past few hours???

Thanks,
Ryan



On Oct 19, 1:06 pm, Arnaldo de Moraes Pereira eggh...@gmail.com
wrote:
 I'm also experiencing that today. It started to get slow several days ago,
 but today is worse.

 Regards,
 Arnaldo





 On Mon, Oct 19, 2009 at 5:58 PM, Dewald Pretorius dpr...@gmail.com wrote:

  I've also been seeing intermittent connection refuses and really very
  slow performance at times today.

  Dewald

  On Oct 19, 3:13 pm, Michael Steuer mste...@gmail.com wrote:
   Hi All,

   While it's not complete unreachability like yesterday morning, I'm again
   experiencing, let's call it spotty reachability this morning... Requests
   time out or are really slow to complete... Anyone else seeing this?

   Thanks,

   Michael.

   On 10/19/09 9:45 AM, John Kalucki jkalu...@gmail.com wrote:

Dewald, are you down, getting weird headers, or OK?

If you can't connect at all, traceroutes are best. If you get weird
headers, a copy of the header (and your IP address) are best.

Thanks.

On Oct 18, 7:23 am, Dewald Pretorius dpr...@gmail.com wrote:
traceroute to twitter.com (168.143.162.100), 30 hops max, 40 byte
packets
 1  81.b5.85ae.static.theplanet.com (174.133.181.129)  1.351 ms
   1.439
ms  1.464 ms
 2  et2-5.ibr01.hstntx1.theplanet.com (207.218.223.5)  0.198 ms
   0.229
ms  0.266 ms
 3  et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154)  0.444 ms
et3-2.ibr02.hstntx1.theplanet.com (70.87.253.157)
0.224 ms et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154)  0.466 ms
 4  et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58)  0.519 ms
et1-2.ibr02.hstntx2.theplanet.com (70.87.253.169)  0
.454 ms  0.522 ms
 5  xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5)  167.161 ms
167.045 ms  167.206 ms
 6  xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228)  1.185 ms
1.164 ms  1.180 ms
 7  p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129)  6.424
ms  6.331 ms  6.358 ms
 8  po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74)  6.400 ms
6.451 ms  6.489 ms
 9  * * *

--

traceroute to twitter.com (168.143.162.116), 30 hops max, 40 byte
packets
 1  81.b5.85ae.static.theplanet.com (174.133.181.129)  0.387 ms
   0.432
ms  0.475 ms
 2  et2-5.ibr01.hstntx1.theplanet.com (207.218.223.5)  0.211 ms
   0.257
ms  0.273 ms
 3  et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154)  0.472 ms
et3-2.ibr02.hstntx1.theplanet.com (70.87.253.157)
0.221 ms  0.249 ms
 4  et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58)  0.404 ms  0.466
ms  0.553 ms
 5  xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5)  107.597 ms
107.679 ms  107.742 ms
 6  xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228)  1.136 ms
1.114 ms  1.035 ms
 7  p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129)  6.293
ms  8.708 ms  6.335 ms
 8  po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74)  6.433 ms
6.486 ms  6.535 ms
 9  * * *

-

traceroute to twitter.com (168.143.162.36), 30 hops max, 40 byte
packets
 1  81.b5.85ae.static.theplanet.com (174.133.181.129)  0.429 ms
   0.515
ms  0.567 ms
 2  et2-5.ibr02.hstntx1.theplanet.com (207.218.245.5)  8.956 ms
   8.986
ms  9.024 ms
 3  et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58)  0.439 ms  0.493
ms  0.546 ms
 4  xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5)  1.156 ms
1.206 ms  1.254 ms
 5  xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228)  1.114 ms
1.113 ms  1.131 ms
 6  p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129)  6.280
ms  6.256 ms  6.717 ms
 7  po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74)  6.377 ms
6.444 ms  6.499 ms
 8  * * *

On Oct 18, 11:14 am, John Kalucki jkalu...@gmail.com wrote:

I don't see any operational issues from here, but I'm not an
operational guy. At first glance the system looks fine, and the
operational team isn't in response mode. This is puzzling.

Seems like a connectivity issue upstream from twitter. At lest a few
developers: please send a traceroute to this list. Also, if you
  aren't
timing out, but rather are getting an HTTP error, send the response
headers. After say 4 or 5 responses, they'll probably have enough
  info
to triage this.

-John 

[twitter-dev] Re: Problems Connecting to the API

2009-10-19 Thread Chad Etzel

Ryan,

Are you still experiencing this? I just tried several user timelines
(w/o authentication) from my home computer (outside of twitter
network) with no errors...

-Chad

On Mon, Oct 19, 2009 at 5:51 PM, Ryan Rosario uclamath...@gmail.com wrote:

 I keep getting {request:/statuses/user_timeline.json?
 user_id=TheUserIDcount=200,error:This method requires
 authentication.}
 when I try to pull a user's tweets. This never used to happen. Earlier
 today I did not need to authenticate to do this.

 Even when I pass my username and password, I still get this error:
 curl -uMyUsername:MyPassword 
 http://twitter.com/statuses/user_timeline.json?user_id=MyUserID\count=200
 I keep getting {request:/statuses/user_timeline.json?
 user_id=TheUserIDcount=200,error:This method requires
 authentication.}

 Did something change in the past few hours???

 Thanks,
 Ryan



 On Oct 19, 1:06 pm, Arnaldo de Moraes Pereira eggh...@gmail.com
 wrote:
 I'm also experiencing that today. It started to get slow several days ago,
 but today is worse.

 Regards,
 Arnaldo





 On Mon, Oct 19, 2009 at 5:58 PM, Dewald Pretorius dpr...@gmail.com wrote:

  I've also been seeing intermittent connection refuses and really very
  slow performance at times today.

  Dewald

  On Oct 19, 3:13 pm, Michael Steuer mste...@gmail.com wrote:
   Hi All,

   While it's not complete unreachability like yesterday morning, I'm again
   experiencing, let's call it spotty reachability this morning... Requests
   time out or are really slow to complete... Anyone else seeing this?

   Thanks,

   Michael.

   On 10/19/09 9:45 AM, John Kalucki jkalu...@gmail.com wrote:

Dewald, are you down, getting weird headers, or OK?

If you can't connect at all, traceroutes are best. If you get weird
headers, a copy of the header (and your IP address) are best.

Thanks.

On Oct 18, 7:23 am, Dewald Pretorius dpr...@gmail.com wrote:
traceroute to twitter.com (168.143.162.100), 30 hops max, 40 byte
packets
 1  81.b5.85ae.static.theplanet.com (174.133.181.129)  1.351 ms
   1.439
ms  1.464 ms
 2  et2-5.ibr01.hstntx1.theplanet.com (207.218.223.5)  0.198 ms
   0.229
ms  0.266 ms
 3  et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154)  0.444 ms
et3-2.ibr02.hstntx1.theplanet.com (70.87.253.157)
0.224 ms et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154)  0.466 ms
 4  et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58)  0.519 ms
et1-2.ibr02.hstntx2.theplanet.com (70.87.253.169)  0
.454 ms  0.522 ms
 5  xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5)  167.161 ms
167.045 ms  167.206 ms
 6  xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228)  1.185 ms
1.164 ms  1.180 ms
 7  p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129)  6.424
ms  6.331 ms  6.358 ms
 8  po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74)  6.400 ms
6.451 ms  6.489 ms
 9  * * *

--

traceroute to twitter.com (168.143.162.116), 30 hops max, 40 byte
packets
 1  81.b5.85ae.static.theplanet.com (174.133.181.129)  0.387 ms
   0.432
ms  0.475 ms
 2  et2-5.ibr01.hstntx1.theplanet.com (207.218.223.5)  0.211 ms
   0.257
ms  0.273 ms
 3  et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154)  0.472 ms
et3-2.ibr02.hstntx1.theplanet.com (70.87.253.157)
0.221 ms  0.249 ms
 4  et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58)  0.404 ms  0.466
ms  0.553 ms
 5  xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5)  107.597 ms
107.679 ms  107.742 ms
 6  xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228)  1.136 ms
1.114 ms  1.035 ms
 7  p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129)  6.293
ms  8.708 ms  6.335 ms
 8  po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74)  6.433 ms
6.486 ms  6.535 ms
 9  * * *

-

traceroute to twitter.com (168.143.162.36), 30 hops max, 40 byte
packets
 1  81.b5.85ae.static.theplanet.com (174.133.181.129)  0.429 ms
   0.515
ms  0.567 ms
 2  et2-5.ibr02.hstntx1.theplanet.com (207.218.245.5)  8.956 ms
   8.986
ms  9.024 ms
 3  et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58)  0.439 ms  0.493
ms  0.546 ms
 4  xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5)  1.156 ms
1.206 ms  1.254 ms
 5  xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228)  1.114 ms
1.113 ms  1.131 ms
 6  p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129)  6.280
ms  6.256 ms  6.717 ms
 7  po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74)  6.377 ms
6.444 ms  6.499 ms
 8  * * *

On Oct 18, 11:14 am, John Kalucki jkalu...@gmail.com wrote:

I don't see any operational issues from here, but I'm not an
operational guy. At first glance the system looks fine, and the
operational team isn't in response mode. This is puzzling.

Seems like a connectivity issue upstream from twitter. At lest a 

[twitter-dev] Re: Problems Connecting to the API

2009-10-19 Thread Ryan Rosario

Hi Chad,

I am still experiencing problems with this. I have tried on several
different computers, each with the same result. I am using curl to
test, but Python urllib2 returns a 401 instead.

Ryan

On Oct 19, 3:45 pm, Chad Etzel c...@twitter.com wrote:
 Ryan,

 Are you still experiencing this? I just tried several user timelines
 (w/o authentication) from my home computer (outside of twitter
 network) with no errors...

 -Chad



 On Mon, Oct 19, 2009 at 5:51 PM, Ryan Rosario uclamath...@gmail.com wrote:

  I keep getting {request:/statuses/user_timeline.json?
  user_id=TheUserIDcount=200,error:This method requires
  authentication.}
  when I try to pull a user's tweets. This never used to happen. Earlier
  today I did not need to authenticate to do this.

  Even when I pass my username and password, I still get this error:
  curl 
  -uMyUsername:MyPasswordhttp://twitter.com/statuses/user_timeline.json?user_id=MyUserID\count=200
  I keep getting {request:/statuses/user_timeline.json?
  user_id=TheUserIDcount=200,error:This method requires
  authentication.}

  Did something change in the past few hours???

  Thanks,
  Ryan

  On Oct 19, 1:06 pm, Arnaldo de Moraes Pereira eggh...@gmail.com
  wrote:
  I'm also experiencing that today. It started to get slow several days ago,
  but today is worse.

  Regards,
  Arnaldo

  On Mon, Oct 19, 2009 at 5:58 PM, Dewald Pretorius dpr...@gmail.com wrote:

   I've also been seeing intermittent connection refuses and really very
   slow performance at times today.

   Dewald

   On Oct 19, 3:13 pm, Michael Steuer mste...@gmail.com wrote:
Hi All,

While it's not complete unreachability like yesterday morning, I'm 
again
experiencing, let's call it spotty reachability this morning... 
Requests
time out or are really slow to complete... Anyone else seeing this?

Thanks,

Michael.

On 10/19/09 9:45 AM, John Kalucki jkalu...@gmail.com wrote:

 Dewald, are you down, getting weird headers, or OK?

 If you can't connect at all, traceroutes are best. If you get weird
 headers, a copy of the header (and your IP address) are best.

 Thanks.

 On Oct 18, 7:23 am, Dewald Pretorius dpr...@gmail.com wrote:
 traceroute to twitter.com (168.143.162.100), 30 hops max, 40 byte
 packets
  1  81.b5.85ae.static.theplanet.com (174.133.181.129)  1.351 ms
    1.439
 ms  1.464 ms
  2  et2-5.ibr01.hstntx1.theplanet.com (207.218.223.5)  0.198 ms
    0.229
 ms  0.266 ms
  3  et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154)  0.444 ms
 et3-2.ibr02.hstntx1.theplanet.com (70.87.253.157)
 0.224 ms et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154)  0.466 ms
  4  et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58)  0.519 ms
 et1-2.ibr02.hstntx2.theplanet.com (70.87.253.169)  0
 .454 ms  0.522 ms
  5  xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5)  167.161 ms
 167.045 ms  167.206 ms
  6  xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228)  1.185 
 ms
 1.164 ms  1.180 ms
  7  p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129)  6.424
 ms  6.331 ms  6.358 ms
  8  po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74)  6.400 ms
 6.451 ms  6.489 ms
  9  * * *

 --

 traceroute to twitter.com (168.143.162.116), 30 hops max, 40 byte
 packets
  1  81.b5.85ae.static.theplanet.com (174.133.181.129)  0.387 ms
    0.432
 ms  0.475 ms
  2  et2-5.ibr01.hstntx1.theplanet.com (207.218.223.5)  0.211 ms
    0.257
 ms  0.273 ms
  3  et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154)  0.472 ms
 et3-2.ibr02.hstntx1.theplanet.com (70.87.253.157)
 0.221 ms  0.249 ms
  4  et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58)  0.404 ms  
 0.466
 ms  0.553 ms
  5  xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5)  107.597 ms
 107.679 ms  107.742 ms
  6  xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228)  1.136 
 ms
 1.114 ms  1.035 ms
  7  p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129)  6.293
 ms  8.708 ms  6.335 ms
  8  po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74)  6.433 ms
 6.486 ms  6.535 ms
  9  * * *

 -

 traceroute to twitter.com (168.143.162.36), 30 hops max, 40 byte
 packets
  1  81.b5.85ae.static.theplanet.com (174.133.181.129)  0.429 ms
    0.515
 ms  0.567 ms
  2  et2-5.ibr02.hstntx1.theplanet.com (207.218.245.5)  8.956 ms
    8.986
 ms  9.024 ms
  3  et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58)  0.439 ms  
 0.493
 ms  0.546 ms
  4  xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5)  1.156 ms
 1.206 ms  1.254 ms
  5  xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228)  1.114 
 ms
 1.113 ms  1.131 ms
  6  p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129)  6.280
 ms  6.256 ms  6.717 ms
  7  po-1.r01.dllstx09.us.bb.gin.ntt.net 

[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread Michael Steuer



Yes, not connecting at all here. Kust timing out.


On Oct 18, 2009, at 6:40 AM, Dewald Pretorius dpr...@gmail.com wrote:



Does anyone else have problems connecting to the API at the moment
(Sunday morning October 18)?

Dewald


[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread Michael D. Ivey


Not just you. Every machine I've tried times out, but  
istwitterdown.com says No and Seesmic Web works. Seems to be  
connectivity issue.


Sent from my iPhone

On Oct 18, 2009, at 8:40 AM, Dewald Pretorius dpr...@gmail.com wrote:



Does anyone else have problems connecting to the API at the moment
(Sunday morning October 18)?

Dewald


[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread Michael Steuer


In fact, looking at my logs, the API was down since at least 2 AM  
Pacific (5 hours ago)...




On Oct 18, 2009, at 6:40 AM, Dewald Pretorius dpr...@gmail.com wrote:



Does anyone else have problems connecting to the API at the moment
(Sunday morning October 18)?

Dewald


[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread TCI

THANKS for posting - I've spent the last hour trying to figure this
out and since there were not reports I thought it was me.
Down from my server as well, although if I try the exact same calls
that my server (in USA) is making from my desktop (in Costa Rica) they
all return. This is what had me significantly confused.

Maybe they have different servers for each geo and only some areas are
down?


On Oct 18, 7:40 am, Dewald Pretorius dpr...@gmail.com wrote:
 Does anyone else have problems connecting to the API at the moment
 (Sunday morning October 18)?

 Dewald


[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread Michael Ivey
Further info I've collected:

Can't connect from:

   - ATT DSL in South Alabama
   - ATT iPhone network
   - Northwest Florida, probably Comcast
   - Other users in Atlanta
   - Scoble reported various flakiness
   - Servers at Slicehost in the St Louis datacenter

Can connect from:

   - Blackberry in Atlanta
   - Seesmic
   - CoTweet
   - Facebook
   - iPhones in CA (@jess updated via Echofon a little while ago)


 -- ivey


On Sun, Oct 18, 2009 at 8:40 AM, Dewald Pretorius dpr...@gmail.com wrote:


 Does anyone else have problems connecting to the API at the moment
 (Sunday morning October 18)?

 Dewald



[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread John Kalucki

I don't see any operational issues from here, but I'm not an
operational guy. At first glance the system looks fine, and the
operational team isn't in response mode. This is puzzling.

Seems like a connectivity issue upstream from twitter. At lest a few
developers: please send a traceroute to this list. Also, if you aren't
timing out, but rather are getting an HTTP error, send the response
headers. After say 4 or 5 responses, they'll probably have enough info
to triage this.

-John Kalucki
http://twitter.com/jkalucki
Services, Twitter Inc.



On Oct 18, 6:40 am, Dewald Pretorius dpr...@gmail.com wrote:
 Does anyone else have problems connecting to the API at the moment
 (Sunday morning October 18)?

 Dewald


[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread Dewald Pretorius

traceroute to twitter.com (168.143.162.100), 30 hops max, 40 byte
packets
 1  81.b5.85ae.static.theplanet.com (174.133.181.129)  1.351 ms  1.439
ms  1.464 ms
 2  et2-5.ibr01.hstntx1.theplanet.com (207.218.223.5)  0.198 ms  0.229
ms  0.266 ms
 3  et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154)  0.444 ms
et3-2.ibr02.hstntx1.theplanet.com (70.87.253.157)
0.224 ms et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154)  0.466 ms
 4  et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58)  0.519 ms
et1-2.ibr02.hstntx2.theplanet.com (70.87.253.169)  0
.454 ms  0.522 ms
 5  xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5)  167.161 ms
167.045 ms  167.206 ms
 6  xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228)  1.185 ms
1.164 ms  1.180 ms
 7  p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129)  6.424
ms  6.331 ms  6.358 ms
 8  po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74)  6.400 ms
6.451 ms  6.489 ms
 9  * * *

--

traceroute to twitter.com (168.143.162.116), 30 hops max, 40 byte
packets
 1  81.b5.85ae.static.theplanet.com (174.133.181.129)  0.387 ms  0.432
ms  0.475 ms
 2  et2-5.ibr01.hstntx1.theplanet.com (207.218.223.5)  0.211 ms  0.257
ms  0.273 ms
 3  et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154)  0.472 ms
et3-2.ibr02.hstntx1.theplanet.com (70.87.253.157)
0.221 ms  0.249 ms
 4  et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58)  0.404 ms  0.466
ms  0.553 ms
 5  xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5)  107.597 ms
107.679 ms  107.742 ms
 6  xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228)  1.136 ms
1.114 ms  1.035 ms
 7  p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129)  6.293
ms  8.708 ms  6.335 ms
 8  po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74)  6.433 ms
6.486 ms  6.535 ms
 9  * * *

-

traceroute to twitter.com (168.143.162.36), 30 hops max, 40 byte
packets
 1  81.b5.85ae.static.theplanet.com (174.133.181.129)  0.429 ms  0.515
ms  0.567 ms
 2  et2-5.ibr02.hstntx1.theplanet.com (207.218.245.5)  8.956 ms  8.986
ms  9.024 ms
 3  et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58)  0.439 ms  0.493
ms  0.546 ms
 4  xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5)  1.156 ms
1.206 ms  1.254 ms
 5  xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228)  1.114 ms
1.113 ms  1.131 ms
 6  p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129)  6.280
ms  6.256 ms  6.717 ms
 7  po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74)  6.377 ms
6.444 ms  6.499 ms
 8  * * *


On Oct 18, 11:14 am, John Kalucki jkalu...@gmail.com wrote:
 I don't see any operational issues from here, but I'm not an
 operational guy. At first glance the system looks fine, and the
 operational team isn't in response mode. This is puzzling.

 Seems like a connectivity issue upstream from twitter. At lest a few
 developers: please send a traceroute to this list. Also, if you aren't
 timing out, but rather are getting an HTTP error, send the response
 headers. After say 4 or 5 responses, they'll probably have enough info
 to triage this.

 -John Kaluckihttp://twitter.com/jkalucki
 Services, Twitter Inc.

 On Oct 18, 6:40 am, Dewald Pretorius dpr...@gmail.com wrote:

  Does anyone else have problems connecting to the API at the moment
  (Sunday morning October 18)?

  Dewald


[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread Michael Steuer
On my end: my server (at Rackspace) can't connect to twitter.com... If I
enter API URLs into my browser at home (Verizon DSL), I connect just fine.
Here's a traceroute from rackspace:

traceroute twitter.com
traceroute to twitter.com (168.143.161.20), 30 hops max, 60 byte packets
 1  xxx-xxx-xxx-xxx.static.cloud-ips.com (xxx.xxx.xxx.xxx)  4.000 ms  4.000
ms  4.000 ms
 2  98.129.84.216 (98.129.84.216)  0.000 ms  0.000 ms  0.000 ms
 3  edge3-core7-vlan3307.dfw1.rackspace.net (174.143.123.115)  4.000 ms
 4.000 ms edge3-core7-vlan2307.dfw1.rackspace.net (174.143.123.113)  4.000
ms
 4  dls-bb1-link.telia.net (213.248.88.173)  4.000 ms  4.000 ms  4.000 ms
 5  verio-ic-127187-dls-bb1.c.telia.net (213.248.81.62)  96.005 ms  96.005
ms  96.005 ms
 6  * * *

Based on my logs, this has been going on since before 2AM PST


On Sun, Oct 18, 2009 at 7:23 AM, Dewald Pretorius dpr...@gmail.com wrote:


 traceroute to twitter.com (168.143.162.100), 30 hops max, 40 byte
 packets
  1  81.b5.85ae.static.theplanet.com (174.133.181.129)  1.351 ms  1.439
 ms  1.464 ms
  2  et2-5.ibr01.hstntx1.theplanet.com (207.218.223.5)  0.198 ms  0.229
 ms  0.266 ms
  3  et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154)  0.444 ms
 et3-2.ibr02.hstntx1.theplanet.com (70.87.253.157)
 0.224 ms et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154)  0.466 ms
  4  et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58)  0.519 ms
 et1-2.ibr02.hstntx2.theplanet.com (70.87.253.169)  0
 .454 ms  0.522 ms
  5  xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5)  167.161 ms
 167.045 ms  167.206 ms
  6  xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228)  1.185 ms
 1.164 ms  1.180 ms
  7  p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129)  6.424
 ms  6.331 ms  6.358 ms
  8  po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74)  6.400 ms
 6.451 ms  6.489 ms
  9  * * *

 --

 traceroute to twitter.com (168.143.162.116), 30 hops max, 40 byte
 packets
  1  81.b5.85ae.static.theplanet.com (174.133.181.129)  0.387 ms  0.432
 ms  0.475 ms
  2  et2-5.ibr01.hstntx1.theplanet.com (207.218.223.5)  0.211 ms  0.257
 ms  0.273 ms
  3  et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154)  0.472 ms
 et3-2.ibr02.hstntx1.theplanet.com (70.87.253.157)
 0.221 ms  0.249 ms
  4  et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58)  0.404 ms  0.466
 ms  0.553 ms
  5  xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5)  107.597 ms
 107.679 ms  107.742 ms
  6  xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228)  1.136 ms
 1.114 ms  1.035 ms
  7  p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129)  6.293
 ms  8.708 ms  6.335 ms
  8  po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74)  6.433 ms
 6.486 ms  6.535 ms
  9  * * *

 -

 traceroute to twitter.com (168.143.162.36), 30 hops max, 40 byte
 packets
  1  81.b5.85ae.static.theplanet.com (174.133.181.129)  0.429 ms  0.515
 ms  0.567 ms
  2  et2-5.ibr02.hstntx1.theplanet.com (207.218.245.5)  8.956 ms  8.986
 ms  9.024 ms
  3  et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58)  0.439 ms  0.493
 ms  0.546 ms
  4  xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5)  1.156 ms
 1.206 ms  1.254 ms
  5  xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228)  1.114 ms
 1.113 ms  1.131 ms
  6  p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129)  6.280
 ms  6.256 ms  6.717 ms
  7  po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74)  6.377 ms
 6.444 ms  6.499 ms
  8  * * *


 On Oct 18, 11:14 am, John Kalucki jkalu...@gmail.com wrote:
  I don't see any operational issues from here, but I'm not an
  operational guy. At first glance the system looks fine, and the
  operational team isn't in response mode. This is puzzling.
 
  Seems like a connectivity issue upstream from twitter. At lest a few
  developers: please send a traceroute to this list. Also, if you aren't
  timing out, but rather are getting an HTTP error, send the response
  headers. After say 4 or 5 responses, they'll probably have enough info
  to triage this.
 
  -John Kaluckihttp://twitter.com/jkalucki
  Services, Twitter Inc.
 
  On Oct 18, 6:40 am, Dewald Pretorius dpr...@gmail.com wrote:
 
   Does anyone else have problems connecting to the API at the moment
   (Sunday morning October 18)?
 
   Dewald



[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread Michael Ivey
From slicehost St. Louis:
traceroute to twitter.com (168.143.161.20), 30 hops max, 60 byte packets
 1  174.143.199.2 (174.143.199.2)  4.000 ms  4.000 ms  4.000 ms
 2  98.129.84.172 (98.129.84.172)  4.000 ms  4.000 ms  4.000 ms
 3  edge3-core7-vlan3307.dfw1.rackspace.net (174.143.123.115)  4.000 ms
edge3-core7-vlan2307.dfw1.rackspace.net (174.143.123.113)  4.000 ms
edge3-core7-vlan3307.dfw1.rackspace.net (174.143.123.115)  4.000 ms
 4  dls-bb1-link.telia.net (213.248.88.173)  4.000 ms  4.000 ms  4.000 ms
 5  verio-ic-127187-dls-bb1.c.telia.net (213.248.81.62)  4.000 ms  0.000 ms
0.000 ms
6 * * *

traceroute to twitter.com (128.121.146.100), 30 hops max, 60 byte packets
 1  174.143.199.2 (174.143.199.2)  4.000 ms  4.000 ms  4.000 ms
 2  98.129.84.172 (98.129.84.172)  0.000 ms  0.000 ms  0.000 ms
 3  98.129.84.178 (98.129.84.178)  104.006 ms  104.006 ms  104.006 ms
 4  gateway.above.net (209.133.126.41)  40.002 ms  40.002 ms  40.002 ms
 5  64.125.12.218.available.above.net (64.125.12.222)  4.000 ms  4.000 ms
4.000 ms
 6  po-4.r02.dllstx09.us.bb.gin.ntt.net (129.250.2.93)  4.000 ms  4.000 ms
4.000 ms
 7  xe-6-2.r01.dllstx09.us.bb.gin.ntt.net (129.250.4.174)  0.000 ms  0.000
ms  0.000 ms
 8  * * *

traceroute to twitter.com (168.143.162.116), 30 hops max, 60 byte packets
 1  174.143.199.2 (174.143.199.2)  4.001 ms  4.001 ms  4.001 ms
 2  98.129.84.172 (98.129.84.172)  0.000 ms  0.000 ms  0.000 ms
 3  edge3-core7-vlan2307.dfw1.rackspace.net (174.143.123.113)  0.000 ms
edge3-core7-vlan3307.dfw1.rackspace.net (174.143.123.115)  0.000 ms
edge3-core7-vlan2307.dfw1.rackspace.net (174.143.123.113)  0.000 ms
 4  dls-bb1-link.telia.net (213.248.88.173)  36.002 ms  36.002 ms  36.002 ms
 5  verio-ic-127187-dls-bb1.c.telia.net (213.248.81.62)  100.005 ms  100.005
ms  100.005 ms
 6  * * *

From ATT DSL in Alabama:
traceroute to twitter.com (168.143.162.116), 64 hops max, 40 byte packets
 1  192.168.1.254 (192.168.1.254)  1.940 ms  2.202 ms  1.527 ms
 2  72.157.0.8 (72.157.0.8)  8.080 ms  14.058 ms  11.673 ms
 3  72.157.48.18 (72.157.48.18)  9.230 ms  8.685 ms  8.809 ms
 4  72.157.48.243 (72.157.48.243)  16.000 ms  20.867 ms  17.520 ms
 5  axr00mgm-so-0-1-0.bellsouth.net (65.83.239.80)  16.704 ms  32.931 ms
16.616 ms
 6  205.152.170.27 (205.152.170.27)  32.417 ms *  16.573 ms
 7  pxr00mna-so-1-0-0.bellsouth.net (65.83.236.62)  16.955 ms  17.866 ms
17.136 ms
 8  12.83.2.32 (12.83.2.32)  16.129 ms  17.257 ms  16.649 ms
 9  74.175.192.66 (74.175.192.66)  24.977 ms  25.824 ms  26.831 ms
10  cr2.attga.ip.att.net (12.122.140.186)  30.323 ms  26.766 ms
cr1.attga.ip.att.net (12.122.141.186)  28.070 ms
11  ggr6.attga.ip.att.net (12.122.89.241)  25.732 ms  25.075 ms  25.209 ms
12  192.205.36.158 (192.205.36.158)  26.543 ms  25.269 ms  25.468 ms
13  p64-5-0-0.r21.dllstx09.us.bb.gin.ntt.net (129.250.5.26)  44.591 ms
44.821 ms  44.474 ms
14  * * *

From datacenter in downtown Atlanta:
traceroute to twitter.com (168.143.162.36), 30 hops max, 38 byte packets
 1  atl-datacenter-r2.capitalinternet.com (208.32.175.2)  0.964 ms  0.526
ms  0.712 ms
 2  atl-downtown-r1.capitalinternet.com (199.0.160.1)  1.309 ms  1.567 ms
1.213 ms
 3  199.0.160.20 (199.0.160.20)  1.063 ms  1.326 ms  1.090 ms
 4  * * *


 -- ivey


On Sun, Oct 18, 2009 at 9:14 AM, John Kalucki jkalu...@gmail.com wrote:


 I don't see any operational issues from here, but I'm not an
 operational guy. At first glance the system looks fine, and the
 operational team isn't in response mode. This is puzzling.

 Seems like a connectivity issue upstream from twitter. At lest a few
 developers: please send a traceroute to this list. Also, if you aren't
 timing out, but rather are getting an HTTP error, send the response
 headers. After say 4 or 5 responses, they'll probably have enough info
 to triage this.

 -John Kalucki
 http://twitter.com/jkalucki
 Services, Twitter Inc.



 On Oct 18, 6:40 am, Dewald Pretorius dpr...@gmail.com wrote:
  Does anyone else have problems connecting to the API at the moment
  (Sunday morning October 18)?
 
  Dewald



[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread TCI

Tracert disabled from host - fail!
But I assume that if we can't reach you, you should not be able to
reach us either? My server's IP is 174.120.0.108 (The Planet)

On Oct 18, 8:14 am, John Kalucki jkalu...@gmail.com wrote:
 I don't see any operational issues from here, but I'm not an
 operational guy. At first glance the system looks fine, and the
 operational team isn't in response mode. This is puzzling.

 Seems like a connectivity issue upstream from twitter. At lest a few
 developers: please send a traceroute to this list. Also, if you aren't
 timing out, but rather are getting an HTTP error, send the response
 headers. After say 4 or 5 responses, they'll probably have enough info
 to triage this.

 -John Kaluckihttp://twitter.com/jkalucki
 Services, Twitter Inc.

 On Oct 18, 6:40 am, Dewald Pretorius dpr...@gmail.com wrote:

  Does anyone else have problems connecting to the API at the moment
  (Sunday morning October 18)?

  Dewald


[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread Richard

I'm getting this from my slicehost servers.

$ traceroute twitter.com
traceroute to twitter.com (168.143.161.20), 30 hops max, 40 byte
packets
 1  67-207-128-2.slicehost.net (67.207.128.2)  0.191 ms  0.165 ms
0.153 ms
 2  209-20-79-2.slicehost.net (209.20.79.2)  0.704 ms  0.776 ms  0.347
ms
 3  ge-6-10-163.car1.StLouis1.Level3.net (4.53.160.241)  1.813 ms
1.747 ms  1.720 ms
 4  ae-11-11.car2.StLouis1.Level3.net (4.69.132.186)  1.678 ms  1.680
ms  1.863 ms
 5  ae-4-4.ebr2.Chicago1.Level3.net (4.69.132.190)  14.920 ms  14.921
ms  14.899 ms
 6  ae-2-56.edge3.Chicago3.Level3.net (4.68.101.180)  21.901 ms
ae-2-52.edge3.Chicago3.Level3.net (4.68.101.52)  21.860 ms
ae-2-54.edge3.Chicago3.Level3.net (4.68.101.116)  7.653 ms
 7  4.68.63.198 (4.68.63.198)  8.226 ms  7.614 ms  8.172 ms
 8  ae-1.r21.chcgil09.us.bb.gin.ntt.net (129.250.3.8)  7.824 ms  7.650
ms  7.420 ms
 9  as-1.r21.dllstx09.us.bb.gin.ntt.net (129.250.3.17)  30.882 ms
33.149 ms  33.468 ms
10  po-2.r01.dllstx09.us.bb.gin.ntt.net (129.250.4.42)  33.440 ms
33.412 ms  33.027 ms
11  * * *

It's working from Freedom2surf ADSL in the UK.


On Oct 18, 3:31 pm, Michael Steuer mste...@gmail.com wrote:
 On my end: my server (at Rackspace) can't connect to twitter.com... If I
 enter API URLs into my browser at home (Verizon DSL), I connect just fine.
 Here's a traceroute from rackspace:

 traceroute twitter.com
 traceroute to twitter.com (168.143.161.20), 30 hops max, 60 byte packets
  1  xxx-xxx-xxx-xxx.static.cloud-ips.com (xxx.xxx.xxx.xxx)  4.000 ms  4.000
 ms  4.000 ms
  2  98.129.84.216 (98.129.84.216)  0.000 ms  0.000 ms  0.000 ms
  3  edge3-core7-vlan3307.dfw1.rackspace.net (174.143.123.115)  4.000 ms
  4.000 ms edge3-core7-vlan2307.dfw1.rackspace.net (174.143.123.113)  4.000
 ms
  4  dls-bb1-link.telia.net (213.248.88.173)  4.000 ms  4.000 ms  4.000 ms
  5  verio-ic-127187-dls-bb1.c.telia.net (213.248.81.62)  96.005 ms  96.005
 ms  96.005 ms
  6  * * *

 Based on my logs, this has been going on since before 2AM PST

 On Sun, Oct 18, 2009 at 7:23 AM, Dewald Pretorius dpr...@gmail.com wrote:

  traceroute to twitter.com (168.143.162.100), 30 hops max, 40 byte
  packets
   1  81.b5.85ae.static.theplanet.com (174.133.181.129)  1.351 ms  1.439
  ms  1.464 ms
   2  et2-5.ibr01.hstntx1.theplanet.com (207.218.223.5)  0.198 ms  0.229
  ms  0.266 ms
   3  et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154)  0.444 ms
  et3-2.ibr02.hstntx1.theplanet.com (70.87.253.157)
  0.224 ms et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154)  0.466 ms
   4  et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58)  0.519 ms
  et1-2.ibr02.hstntx2.theplanet.com (70.87.253.169)  0
  .454 ms  0.522 ms
   5  xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5)  167.161 ms
  167.045 ms  167.206 ms
   6  xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228)  1.185 ms
  1.164 ms  1.180 ms
   7  p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129)  6.424
  ms  6.331 ms  6.358 ms
   8  po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74)  6.400 ms
  6.451 ms  6.489 ms
   9  * * *

  --

  traceroute to twitter.com (168.143.162.116), 30 hops max, 40 byte
  packets
   1  81.b5.85ae.static.theplanet.com (174.133.181.129)  0.387 ms  0.432
  ms  0.475 ms
   2  et2-5.ibr01.hstntx1.theplanet.com (207.218.223.5)  0.211 ms  0.257
  ms  0.273 ms
   3  et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154)  0.472 ms
  et3-2.ibr02.hstntx1.theplanet.com (70.87.253.157)
  0.221 ms  0.249 ms
   4  et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58)  0.404 ms  0.466
  ms  0.553 ms
   5  xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5)  107.597 ms
  107.679 ms  107.742 ms
   6  xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228)  1.136 ms
  1.114 ms  1.035 ms
   7  p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129)  6.293
  ms  8.708 ms  6.335 ms
   8  po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74)  6.433 ms
  6.486 ms  6.535 ms
   9  * * *

  -

  traceroute to twitter.com (168.143.162.36), 30 hops max, 40 byte
  packets
   1  81.b5.85ae.static.theplanet.com (174.133.181.129)  0.429 ms  0.515
  ms  0.567 ms
   2  et2-5.ibr02.hstntx1.theplanet.com (207.218.245.5)  8.956 ms  8.986
  ms  9.024 ms
   3  et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58)  0.439 ms  0.493
  ms  0.546 ms
   4  xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5)  1.156 ms
  1.206 ms  1.254 ms
   5  xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228)  1.114 ms
  1.113 ms  1.131 ms
   6  p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129)  6.280
  ms  6.256 ms  6.717 ms
   7  po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74)  6.377 ms
  6.444 ms  6.499 ms
   8  * * *

  On Oct 18, 11:14 am, John Kalucki jkalu...@gmail.com wrote:
   I don't see any operational issues from here, but I'm not an
   operational guy. At first glance the system looks fine, and the
   operational team isn't in response mode. This is puzzling.

   Seems like a connectivity issue upstream from 

[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread Dean Collins

Time Warner NYC

Tracing route to twitter.com [168.143.162.116]


  4 8 ms 8 ms 7 ms  gig10-0-0-nycmnya-rtr1.nyc.rr.com
[24.29.157.98]
  5 7 ms 8 ms 5 ms  tenge-0-3-0-nwrknjmd-rtr.nyc.rr.com
[24.29.97.6]
  6 6 ms 8 ms 7 ms  ae-4-0.cr0.nyc30.tbone.rr.com
[66.109.6.78]
  714 ms28 ms23 ms  ae-4-0.cr0.dca20.tbone.rr.com
[66.109.6.28]
  822 ms13 ms11 ms  ae-1-0.pr0.dca10.tbone.rr.com
[66.109.6.165]
  923 ms17 ms18 ms  if-11-1.icore1.AEQ-Ashburn.as6453.net
[206.82.139.53]
 1018 ms ** ix-2-8.icore1.AEQ-Ashburn.as6453.net
[206.82.139.46]
 1113 ms14 ms11 ms  ae-2.r21.asbnva01.us.bb.gin.ntt.net
[129.250.2.98]
 1213 ms14 ms11 ms  xe-6-1.r00.asbnva02.us.bb.gin.ntt.net
[129.250.3.29]
 13 *** Request timed out.
 1481 ms80 ms78 ms  129.250.6.242
 1581 ms79 ms82 ms  128.121.150.133
 1684 ms78 ms77 ms  168.143.162.85
 1779 ms81 ms82 ms  168.143.162.116

 

 

 

Cheers,

Dean

 



[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread Michael Steuer

So somewhere before you reach twitter.com, traceroute must get
blocked. I just did a traceroute from my home (Verizon DSL) where I
can access Twitter perfectly, and traceroute still doesn't complete:

michael-steuers-computer:~ msteuer$ traceroute twitter.com
traceroute to twitter.com (128.121.146.100), 64 hops max, 52 byte
packets
 1  192.168.1.1 (192.168.1.1)  0.611 ms  0.311 ms  0.197 ms
 2  10.35.27.1 (10.35.27.1)  21.969 ms  22.321 ms  21.706 ms
 3  p0-3.lsanca-lcr-03.verizon-gni.net (130.81.34.248)  21.712 ms
21.478 ms  21.507 ms
 4  so-6-1-2-0.lax01-bb-rtr1.verizon-gni.net (130.81.28.225)  21.958
ms  21.830 ms  22.000 ms
 5  0.so-6-3-0.xt1.lax9.alter.net (152.63.10.153)  23.446 ms  23.323
ms  23.743 ms
 6  0.so-5-1-0.xt1.lax7.alter.net (152.63.116.253)  48.239 ms  24.029
ms  23.228 ms
 7  pos6-0.br2.lax7.alter.net (152.63.112.145)  23.472 ms  23.722 ms
23.467 ms
 8  p64-6-1-3.r20.lsanca03.us.bb.gin.ntt.net (129.250.8.205)  25.215
ms  24.968 ms  24.735 ms
 9  as-0.r21.snjsca04.us.bb.gin.ntt.net (129.250.4.96)  35.987 ms
36.747 ms  35.958 ms
10  po-2.r04.snjsca04.us.bb.gin.ntt.net (129.250.6.6)  36.516 ms
37.034 ms *
11  * * *

So I don't know how helpful all these traceroute results are going to
be for Twitter, given that both from networks that can connect, and
those that can't the traceroutes fail in the ntt.net or telia.net
networks

On Oct 18, 7:33 am, TCI ticoconid...@gmail.com wrote:
 Tracert disabled from host - fail!
 But I assume that if we can't reach you, you should not be able to
 reach us either? My server's IP is 174.120.0.108 (The Planet)

 On Oct 18, 8:14 am, John Kalucki jkalu...@gmail.com wrote:



  I don't see any operational issues from here, but I'm not an
  operational guy. At first glance the system looks fine, and the
  operational team isn't in response mode. This is puzzling.

  Seems like a connectivity issue upstream from twitter. At lest a few
  developers: please send a traceroute to this list. Also, if you aren't
  timing out, but rather are getting an HTTP error, send the response
  headers. After say 4 or 5 responses, they'll probably have enough info
  to triage this.

  -John Kaluckihttp://twitter.com/jkalucki
  Services, Twitter Inc.

  On Oct 18, 6:40 am, Dewald Pretorius dpr...@gmail.com wrote:

   Does anyone else have problems connecting to the API at the moment
   (Sunday morning October 18)?

   Dewald


[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread Cameron Kaiser

 So somewhere before you reach twitter.com, traceroute must get
 blocked. I just did a traceroute from my home (Verizon DSL) where I
 can access Twitter perfectly, and traceroute still doesn't complete:

I wouldn't read too much into that. From what I remember of Twitter's
infrastructure (IDNSOWFT), NTT is their provider, so you are reaching their
network, and I would not be surprised if ICMP were blocked once you got
through the outside NTT perimetre.

-- 
 personal: http://www.cameronkaiser.com/ --
  Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com
-- Seen on hand dryer: Push button for a message from your congressman. -


[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread MikeF

We also can't connect from Chicago.  I think we also lost connectivity
around 2am.

traceroute to cnn.com (157.166.255.18), 30 hops max, 40 byte packets
 1  ip131.67-202-65.static.steadfast.net (67.202.65.131)  0.393 ms
0.467 ms  0.507 ms
 2  te-8-2.car3.Chicago1.Level3.net (4.71.101.1)  0.332 ms  0.370 ms
0.457 ms
 3  ae-32-56.ebr2.Chicago1.Level3.net (4.68.101.190)  6.576 ms  6.813
ms  6.557 ms
 4  ae-3.ebr2.Atlanta2.Level3.net (4.69.132.74)  29.152 ms  29.128 ms
29.121 ms
 5  ae-11-51.car1.Atlanta1.Level3.net (4.68.103.2)  20.158 ms
ae-21-52.car1.Atlanta1.Level3.net (4.68.103.34)  19.592 ms
ae-11-51.car1.Atlanta1.Level3.net (4.68.103.2)  20.479 ms
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *


[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread Mark Ng

+1 can't connect from slicehost.com (I believe in St. Louis).

2009/10/18 Michael Ivey michael.i...@gmail.com:
 Further info I've collected:

 Can't connect from:

 ATT DSL in South Alabama
 ATT iPhone network
 Northwest Florida, probably Comcast
 Other users in Atlanta
 Scoble reported various flakiness
 Servers at Slicehost in the St Louis datacenter

 Can connect from:

 Blackberry in Atlanta
 Seesmic
 CoTweet
 Facebook
 iPhones in CA (@jess updated via Echofon a little while ago)

  -- ivey


 On Sun, Oct 18, 2009 at 8:40 AM, Dewald Pretorius dpr...@gmail.com wrote:

 Does anyone else have problems connecting to the API at the moment
 (Sunday morning October 18)?

 Dewald




[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread uzyn

NTT America is not responding to requests coming from certain IP
addresses.

According to my tests from a few different hosts, it seems that some
nodes of ntt.net are not relaying requests for US-based IPs, but a few
of Asian hosts that I tested from are able to reach twitter.com fine.


On Oct 18, 9:40 pm, Dewald Pretorius dpr...@gmail.com wrote:
 Does anyone else have problems connecting to the API at the moment
 (Sunday morning October 18)?

 Dewald


[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread Naveen Ayyagari


+1 also can not connect to twitter api from any of our servers.
On Oct 18, 2009, at 10:32 AM, Mark Ng wrote:



+1 can't connect from slicehost.com (I believe in St. Louis).

2009/10/18 Michael Ivey michael.i...@gmail.com:

Further info I've collected:

Can't connect from:

ATT DSL in South Alabama
ATT iPhone network
Northwest Florida, probably Comcast
Other users in Atlanta
Scoble reported various flakiness
Servers at Slicehost in the St Louis datacenter

Can connect from:

Blackberry in Atlanta
Seesmic
CoTweet
Facebook
iPhones in CA (@jess updated via Echofon a little while ago)

 -- ivey


On Sun, Oct 18, 2009 at 8:40 AM, Dewald Pretorius  
dpr...@gmail.com wrote:


Does anyone else have problems connecting to the API at the moment
(Sunday morning October 18)?

Dewald







[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread John Kalucki

OK. I think we have enough traceroutes for now. Thanks for sending
them in!

If we need more datapoints or information, I'll update this thread.

On Oct 18, 7:14 am, John Kalucki jkalu...@gmail.com wrote:
 I don't see any operational issues from here, but I'm not an
 operational guy. At first glance the system looks fine, and the
 operational team isn't in response mode. This is puzzling.

 Seems like a connectivity issue upstream from twitter. At lest a few
 developers: please send a traceroute to this list. Also, if you aren't
 timing out, but rather are getting an HTTP error, send the response
 headers. After say 4 or 5 responses, they'll probably have enough info
 to triage this.

 -John Kaluckihttp://twitter.com/jkalucki
 Services, Twitter Inc.

 On Oct 18, 6:40 am, Dewald Pretorius dpr...@gmail.com wrote:

  Does anyone else have problems connecting to the API at the moment
  (Sunday morning October 18)?

  Dewald


[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread John Kalucki

And here's the next question:

Is anyone having trouble from non-service, non-hosted endpoints. In
other words, problem from home ISPs and desktop clients?

-John Kalucki
http://twitter.com/jkalucki
Services, Twitter Inc.


On Oct 18, 7:55 am, John Kalucki jkalu...@gmail.com wrote:
 OK. I think we have enough traceroutes for now. Thanks for sending
 them in!

 If we need more datapoints or information, I'll update this thread.

 On Oct 18, 7:14 am, John Kalucki jkalu...@gmail.com wrote:

  I don't see any operational issues from here, but I'm not an
  operational guy. At first glance the system looks fine, and the
  operational team isn't in response mode. This is puzzling.

  Seems like a connectivity issue upstream from twitter. At lest a few
  developers: please send a traceroute to this list. Also, if you aren't
  timing out, but rather are getting an HTTP error, send the response
  headers. After say 4 or 5 responses, they'll probably have enough info
  to triage this.

  -John Kaluckihttp://twitter.com/jkalucki
  Services, Twitter Inc.

  On Oct 18, 6:40 am, Dewald Pretorius dpr...@gmail.com wrote:

   Does anyone else have problems connecting to the API at the moment
   (Sunday morning October 18)?

   Dewald


[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread Michael D. Ivey


Yes. Unable to connect via Tweetie from home (one of my traceroutes  
was from home) and lots of reports from iPhone, ATT and Comcast users  
in Southeast.


Sent from my iPhone

On Oct 18, 2009, at 9:56 AM, John Kalucki jkalu...@gmail.com wrote:



And here's the next question:

Is anyone having trouble from non-service, non-hosted endpoints. In
other words, problem from home ISPs and desktop clients?

-John Kalucki
http://twitter.com/jkalucki
Services, Twitter Inc.


On Oct 18, 7:55 am, John Kalucki jkalu...@gmail.com wrote:

OK. I think we have enough traceroutes for now. Thanks for sending
them in!

If we need more datapoints or information, I'll update this thread.

On Oct 18, 7:14 am, John Kalucki jkalu...@gmail.com wrote:


I don't see any operational issues from here, but I'm not an
operational guy. At first glance the system looks fine, and the
operational team isn't in response mode. This is puzzling.



Seems like a connectivity issue upstream from twitter. At lest a few
developers: please send a traceroute to this list. Also, if you  
aren't

timing out, but rather are getting an HTTP error, send the response
headers. After say 4 or 5 responses, they'll probably have enough  
info

to triage this.



-John Kaluckihttp://twitter.com/jkalucki
Services, Twitter Inc.



On Oct 18, 6:40 am, Dewald Pretorius dpr...@gmail.com wrote:



Does anyone else have problems connecting to the API at the moment
(Sunday morning October 18)?



Dewald


[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread MikeF

On Oct 18, 10:56 am, John Kalucki jkalu...@gmail.com wrote:
 And here's the next question:

 Is anyone having trouble from non-service, non-hosted endpoints. In
 other words, problem from home ISPs and desktop clients?

Everything works fine from my home ISP in New York.

But Twitter is completely inaccessible from our servers in Chicago:

curl http://twitter.com/
curl: (7) couldn't connect to host


[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread John Meyer


John Kalucki wrote:

And here's the next question:

Is anyone having trouble from non-service, non-hosted endpoints. In
other words, problem from home ISPs and desktop clients?

-John Kalucki
http://twitter.com/jkalucki
Services, Twitter Inc.
  



Yep. (comcast, cannot access through either the website or desktop clients).


[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread Michael Steuer


I only have two endpoints to test from. Hosted: fails. Home DSL: no  
problem. I have several iPhone clients, but I'm bot sure if they're  
proxies or connect to the API directly...




On Oct 18, 2009, at 7:56 AM, John Kalucki jkalu...@gmail.com wrote:



And here's the next question:

Is anyone having trouble from non-service, non-hosted endpoints. In
other words, problem from home ISPs and desktop clients?

-John Kalucki
http://twitter.com/jkalucki
Services, Twitter Inc.


On Oct 18, 7:55 am, John Kalucki jkalu...@gmail.com wrote:

OK. I think we have enough traceroutes for now. Thanks for sending
them in!

If we need more datapoints or information, I'll update this thread.

On Oct 18, 7:14 am, John Kalucki jkalu...@gmail.com wrote:


I don't see any operational issues from here, but I'm not an
operational guy. At first glance the system looks fine, and the
operational team isn't in response mode. This is puzzling.



Seems like a connectivity issue upstream from twitter. At lest a few
developers: please send a traceroute to this list. Also, if you  
aren't

timing out, but rather are getting an HTTP error, send the response
headers. After say 4 or 5 responses, they'll probably have enough  
info

to triage this.



-John Kaluckihttp://twitter.com/jkalucki
Services, Twitter Inc.



On Oct 18, 6:40 am, Dewald Pretorius dpr...@gmail.com wrote:



Does anyone else have problems connecting to the API at the moment
(Sunday morning October 18)?



Dewald


[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread Michael Steuer


This outage is now going on 7 hours. Any word from Twitter as to an  
ETA for resolution?




On Oct 18, 2009, at 8:08 AM, John Meyer john.l.me...@gmail.com wrote:



John Kalucki wrote:

And here's the next question:

Is anyone having trouble from non-service, non-hosted endpoints. In
other words, problem from home ISPs and desktop clients?

-John Kalucki
http://twitter.com/jkalucki
Services, Twitter Inc.




Yep. (comcast, cannot access through either the website or desktop  
clients).


[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread Dewald Pretorius

I'd be more than happy to wait longer for snazzy API 2.0 features so
that the Platform team can build a QoS system that monitors the API's
availability and performance from the outside. That will enable
Twitter to catch these kinds of issues long before we do.

Dewald

On Oct 18, 12:47 pm, Michael Steuer mste...@gmail.com wrote:
 This outage is now going on 7 hours. Any word from Twitter as to an  
 ETA for resolution?

 On Oct 18, 2009, at 8:08 AM, John Meyer john.l.me...@gmail.com wrote:



  John Kalucki wrote:
  And here's the next question:

  Is anyone having trouble from non-service, non-hosted endpoints. In
  other words, problem from home ISPs and desktop clients?

  -John Kalucki
 http://twitter.com/jkalucki
  Services, Twitter Inc.

  Yep. (comcast, cannot access through either the website or desktop  
  clients).


[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread David Dellanave
Completely dead from multiple ISPs (Level3 upstream) as well as ATT in
Minnesota.


[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread Michael Steuer


Amen to that. I find it kind of curious that as per John K., 5-6 hours  
into this issue, the Twitter ops team was still blissfully unaware of  
anything going on... Also weird that they apparently are unable to  
reproduce the issue without our help, ie. they really haven't set up  
any monitoring outside of their network...




On Oct 18, 2009, at 9:05 AM, Dewald Pretorius dpr...@gmail.com wrote:



I'd be more than happy to wait longer for snazzy API 2.0 features so
that the Platform team can build a QoS system that monitors the API's
availability and performance from the outside. That will enable
Twitter to catch these kinds of issues long before we do.

Dewald

On Oct 18, 12:47 pm, Michael Steuer mste...@gmail.com wrote:

This outage is now going on 7 hours. Any word from Twitter as to an
ETA for resolution?

On Oct 18, 2009, at 8:08 AM, John Meyer john.l.me...@gmail.com  
wrote:





John Kalucki wrote:

And here's the next question:



Is anyone having trouble from non-service, non-hosted endpoints. In
other words, problem from home ISPs and desktop clients?



-John Kalucki
http://twitter.com/jkalucki
Services, Twitter Inc.



Yep. (comcast, cannot access through either the website or desktop
clients).


[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread Bill Jacobson

Desktop via Comcast, Chicago, local times:
-last successful timeline call at 3:50am
-one search query got a response, at 7am
-no access to web site

Michael D. Ivey wrote:

 Yes. Unable to connect via Tweetie from home (one of my traceroutes 
 was from home) and lots of reports from iPhone, ATT and Comcast users 
 in Southeast.

 Sent from my iPhone

 On Oct 18, 2009, at 9:56 AM, John Kalucki jkalu...@gmail.com wrote:


 And here's the next question:

 Is anyone having trouble from non-service, non-hosted endpoints. In
 other words, problem from home ISPs and desktop clients?

 -John Kalucki
 http://twitter.com/jkalucki
 Services, Twitter Inc.


 On Oct 18, 7:55 am, John Kalucki jkalu...@gmail.com wrote:
 OK. I think we have enough traceroutes for now. Thanks for sending
 them in!

 If we need more datapoints or information, I'll update this thread.

 On Oct 18, 7:14 am, John Kalucki jkalu...@gmail.com wrote:

 I don't see any operational issues from here, but I'm not an
 operational guy. At first glance the system looks fine, and the
 operational team isn't in response mode. This is puzzling.

 Seems like a connectivity issue upstream from twitter. At lest a few
 developers: please send a traceroute to this list. Also, if you aren't
 timing out, but rather are getting an HTTP error, send the response
 headers. After say 4 or 5 responses, they'll probably have enough info
 to triage this.

 -John Kaluckihttp://twitter.com/jkalucki
 Services, Twitter Inc.

 On Oct 18, 6:40 am, Dewald Pretorius dpr...@gmail.com wrote:

 Does anyone else have problems connecting to the API at the moment
 (Sunday morning October 18)?

 Dewald



[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread Ryan Sarver

I wanted to check in and see if everyone is back to normal? We think
things have been fixed but its hard to confirm without your help.

Let me know if you are still experiencing any issues and if so, where
you are located.

Best, Ryan

On Sun, Oct 18, 2009 at 10:48 AM, Dewald Pretorius dpr...@gmail.com wrote:

 Same here. Can connect again.

 On Oct 18, 2:46 pm, Michael Steuer mste...@gmail.com wrote:
 The situation seems to have been resolved, at least for me, as of a
 few minutes ago. My Rackspace hosted servers can reach the API again...

 On Oct 18, 2009, at 10:35 AM, Dewald Pretorius dpr...@gmail.com wrote:



  I don't really blame Twitter Ops for not knowing. It's probably a new
  edge defense that was installed by their service provider during
  Sunday night.

  However, a while ago Alex said the Platform team were working on an
  external monitoring solution. Hopefully Ryan, who is now Director of
  the Platform team, will quickly move this forward to completion.

  Dewald

  On Oct 18, 1:30 pm, Michael Steuer mste...@gmail.com wrote:
  Amen to that. I find it kind of curious that as per John K., 5-6
  hours
  into this issue, the Twitter ops team was still blissfully unaware of
  anything going on... Also weird that they apparently are unable to
  reproduce the issue without our help, ie. they really haven't set up
  any monitoring outside of their network...

  On Oct 18, 2009, at 9:05 AM, Dewald Pretorius dpr...@gmail.com
  wrote:

  I'd be more than happy to wait longer for snazzy API 2.0 features so
  that the Platform team can build a QoS system that monitors the
  API's
  availability and performance from the outside. That will enable
  Twitter to catch these kinds of issues long before we do.

  Dewald

  On Oct 18, 12:47 pm, Michael Steuer mste...@gmail.com wrote:
  This outage is now going on 7 hours. Any word from Twitter as to an
  ETA for resolution?

  On Oct 18, 2009, at 8:08 AM, John Meyer john.l.me...@gmail.com
  wrote:

  John Kalucki wrote:
  And here's the next question:

  Is anyone having trouble from non-service, non-hosted
  endpoints. In
  other words, problem from home ISPs and desktop clients?

  -John Kalucki
 http://twitter.com/jkalucki
  Services, Twitter Inc.

  Yep. (comcast, cannot access through either the website or desktop
  clients).



[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread Bryan Longworth

I am connected via ATT DSL from Ft. Pierce, FL. I am unable to
connect with Firefox or TweetDeck. Firefox gives a time out error.

On Oct 18, 10:56 am, John Kalucki jkalu...@gmail.com wrote:
 And here's the next question:

 Is anyone having trouble from non-service, non-hosted endpoints. In
 other words, problem from home ISPs and desktop clients?

 -John Kaluckihttp://twitter.com/jkalucki
 Services, Twitter Inc.

 On Oct 18, 7:55 am, John Kalucki jkalu...@gmail.com wrote:

  OK. I think we have enough traceroutes for now. Thanks for sending
  them in!

  If we need more datapoints or information, I'll update this thread.

  On Oct 18, 7:14 am, John Kalucki jkalu...@gmail.com wrote:

   I don't see any operational issues from here, but I'm not an
   operational guy. At first glance the system looks fine, and the
   operational team isn't in response mode. This is puzzling.

   Seems like a connectivity issue upstream from twitter. At lest a few
   developers: please send a traceroute to this list. Also, if you aren't
   timing out, but rather are getting an HTTP error, send the response
   headers. After say 4 or 5 responses, they'll probably have enough info
   to triage this.

   -John Kaluckihttp://twitter.com/jkalucki
   Services, Twitter Inc.

   On Oct 18, 6:40 am, Dewald Pretorius dpr...@gmail.com wrote:

Does anyone else have problems connecting to the API at the moment
(Sunday morning October 18)?

Dewald


[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread Ryan Sarver

Dewald,

Can you produce some TCP dumps and requests with headers so we can better debug?

Thanks, Ryan

On Sun, Oct 18, 2009 at 12:05 PM, Dewald Pretorius dpr...@gmail.com wrote:

 I'm seeing lots of 502's now. Is the API overloaded?

 Dewald

 On Oct 18, 2:58 pm, Ryan Sarver rsar...@twitter.com wrote:
 Michael,

 We are still working on getting the full picture, but once we have the
 details I will report to the group what the issue was.

 Thanks for updating us.

 Best, Ryan

 On Sun, Oct 18, 2009 at 10:55 AM, Michael Steuer mste...@gmail.com wrote:
  It is working for me. Would you mind sharing with the group what exactly
  happened?
  Thanks.
  Michael

  On Oct 18, 2009, at 10:53 AM, Atul Kulkarni atulskulka...@gmail.com 
  wrote:

  Works Fine... Duluth, MN.

  On Sun, Oct 18, 2009 at 12:51 PM, Ryan Sarver rsar...@twitter.com wrote:

  I wanted to check in and see if everyone is back to normal? We think
  things have been fixed but its hard to confirm without your help.

  Let me know if you are still experiencing any issues and if so, where
  you are located.

  Best, Ryan

  On Sun, Oct 18, 2009 at 10:48 AM, Dewald Pretorius dpr...@gmail.com
  wrote:

   Same here. Can connect again.

   On Oct 18, 2:46 pm, Michael Steuer mste...@gmail.com wrote:
   The situation seems to have been resolved, at least for me, as of a
   few minutes ago. My Rackspace hosted servers can reach the API again...

   On Oct 18, 2009, at 10:35 AM, Dewald Pretorius dpr...@gmail.com
   wrote:

I don't really blame Twitter Ops for not knowing. It's probably a new
edge defense that was installed by their service provider during
Sunday night.

However, a while ago Alex said the Platform team were working on an
external monitoring solution. Hopefully Ryan, who is now Director of
the Platform team, will quickly move this forward to completion.

Dewald

On Oct 18, 1:30 pm, Michael Steuer mste...@gmail.com wrote:
Amen to that. I find it kind of curious that as per John K., 5-6
hours
into this issue, the Twitter ops team was still blissfully unaware
of
anything going on... Also weird that they apparently are unable to
reproduce the issue without our help, ie. they really haven't set up
any monitoring outside of their network...

On Oct 18, 2009, at 9:05 AM, Dewald Pretorius dpr...@gmail.com
wrote:

I'd be more than happy to wait longer for snazzy API 2.0 features
so
that the Platform team can build a QoS system that monitors the
API's
availability and performance from the outside. That will enable
Twitter to catch these kinds of issues long before we do.

Dewald

On Oct 18, 12:47 pm, Michael Steuer mste...@gmail.com wrote:
This outage is now going on 7 hours. Any word from Twitter as to
an
ETA for resolution?

On Oct 18, 2009, at 8:08 AM, John Meyer john.l.me...@gmail.com
wrote:

John Kalucki wrote:
And here's the next question:

Is anyone having trouble from non-service, non-hosted
endpoints. In
other words, problem from home ISPs and desktop clients?

-John Kalucki
   http://twitter.com/jkalucki
Services, Twitter Inc.

Yep. (comcast, cannot access through either the website or
desktop
clients).

  --
  Regards,
  Atul Kulkarni
 www.d.umn.edu/~kulka053



[twitter-dev] Re: Problems Connecting to the API

2009-10-18 Thread Dewald Pretorius

Ryan,

These 502s happen in my high-volume processes. I can't manually
reproduce them.

Most calls don't 502 after the second geometric back-off.

I'm guessing it's just everyone doing a 9-hour catch-up against the
API.

Dewald

On Oct 18, 4:54 pm, Ryan Sarver rsar...@twitter.com wrote:
 Dewald,

 Can you produce some TCP dumps and requests with headers so we can better 
 debug?

 Thanks, Ryan

 On Sun, Oct 18, 2009 at 12:05 PM, Dewald Pretorius dpr...@gmail.com wrote:

  I'm seeing lots of 502's now. Is the API overloaded?

  Dewald

  On Oct 18, 2:58 pm, Ryan Sarver rsar...@twitter.com wrote:
  Michael,

  We are still working on getting the full picture, but once we have the
  details I will report to the group what the issue was.

  Thanks for updating us.

  Best, Ryan

  On Sun, Oct 18, 2009 at 10:55 AM, Michael Steuer mste...@gmail.com wrote:
   It is working for me. Would you mind sharing with the group what exactly
   happened?
   Thanks.
   Michael

   On Oct 18, 2009, at 10:53 AM, Atul Kulkarni atulskulka...@gmail.com 
   wrote:

   Works Fine... Duluth, MN.

   On Sun, Oct 18, 2009 at 12:51 PM, Ryan Sarver rsar...@twitter.com 
   wrote:

   I wanted to check in and see if everyone is back to normal? We think
   things have been fixed but its hard to confirm without your help.

   Let me know if you are still experiencing any issues and if so, where
   you are located.

   Best, Ryan

   On Sun, Oct 18, 2009 at 10:48 AM, Dewald Pretorius dpr...@gmail.com
   wrote:

Same here. Can connect again.

On Oct 18, 2:46 pm, Michael Steuer mste...@gmail.com wrote:
The situation seems to have been resolved, at least for me, as of a
few minutes ago. My Rackspace hosted servers can reach the API 
again...

On Oct 18, 2009, at 10:35 AM, Dewald Pretorius dpr...@gmail.com
wrote:

 I don't really blame Twitter Ops for not knowing. It's probably a 
 new
 edge defense that was installed by their service provider during
 Sunday night.

 However, a while ago Alex said the Platform team were working on an
 external monitoring solution. Hopefully Ryan, who is now Director 
 of
 the Platform team, will quickly move this forward to completion.

 Dewald

 On Oct 18, 1:30 pm, Michael Steuer mste...@gmail.com wrote:
 Amen to that. I find it kind of curious that as per John K., 5-6
 hours
 into this issue, the Twitter ops team was still blissfully unaware
 of
 anything going on... Also weird that they apparently are unable to
 reproduce the issue without our help, ie. they really haven't set 
 up
 any monitoring outside of their network...

 On Oct 18, 2009, at 9:05 AM, Dewald Pretorius dpr...@gmail.com
 wrote:

 I'd be more than happy to wait longer for snazzy API 2.0 features
 so
 that the Platform team can build a QoS system that monitors the
 API's
 availability and performance from the outside. That will enable
 Twitter to catch these kinds of issues long before we do.

 Dewald

 On Oct 18, 12:47 pm, Michael Steuer mste...@gmail.com wrote:
 This outage is now going on 7 hours. Any word from Twitter as to
 an
 ETA for resolution?

 On Oct 18, 2009, at 8:08 AM, John Meyer john.l.me...@gmail.com
 wrote:

 John Kalucki wrote:
 And here's the next question:

 Is anyone having trouble from non-service, non-hosted
 endpoints. In
 other words, problem from home ISPs and desktop clients?

 -John Kalucki
http://twitter.com/jkalucki
 Services, Twitter Inc.

 Yep. (comcast, cannot access through either the website or
 desktop
 clients).

   --
   Regards,
   Atul Kulkarni
  www.d.umn.edu/~kulka053