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
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
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.
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
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
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?
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
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
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
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)
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
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
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
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
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
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
+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
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
+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
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
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
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
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
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
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
Completely dead from multiple ISPs (Level3 upstream) as well as ATT in
Minnesota.
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
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
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
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
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
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,
32 matches
Mail list logo
