Re: [twitter-dev] 168.143.162.36... Connection timed out

2009-12-20 Thread shiplu
On Mon, Dec 21, 2009 at 2:52 AM, Andrew Badera  wrote:
> Probably better to email your IP address directly and not display it
> publicly ...

Dont worry. I dont own them.

I just check some of my peers of same ISP.
None of them is having the problem.
It seems somewhere something is broken.

-- 
Shiplu Mokaddim
My talks, http://talk.cmyweb.net
Follow me, http://twitter.com/shiplu
SUST Programmers, http://groups.google.com/group/p2psust
Innovation distinguishes bet ... ... (ask Steve Jobs the rest)


Re: [twitter-dev] 168.143.162.36... Connection timed out

2009-12-20 Thread Christopher Becker
I was confused, expecting an email from someone else and misread this.

But the IP address is umm...pretty public already wouldn't you say? just try:
ping livefyre.com 

On Dec 20, 2009, at 11:52 AM, Andrew Badera wrote:

> Probably better to email your IP address directly and not display it
> publicly ...
> 
> ∞ Andy Badera
> ∞ +1 518-641-1280 Google Voice
> ∞ This email is: [ ] bloggable [x] ask first [ ] private
> ∞ Google me: http://www.google.com/search?q=andrew%20badera
> 
> 
> 
> On Sun, Dec 20, 2009 at 2:51 PM, shiplu  wrote:
>> My external IP address is 202.56.7.116
>> Its dynamic. 202.56.7.* part is fixed.
>> 
>> --
>> Shiplu Mokaddim
>> My talks, http://talk.cmyweb.net
>> Follow me, http://twitter.com/shiplu
>> SUST Programmers, http://groups.google.com/group/p2psust
>> Innovation distinguishes bet ... ... (ask Steve Jobs the rest)
>> 



Re: [twitter-dev] 168.143.162.36... Connection timed out

2009-12-20 Thread Christopher Becker
We are @ 75.101.136.182

I just tried the help/test api call using curl and the result came back ok, so 
it now seems unlikely that its a blacklisted IP.

Thanks for your help,
Chris

On Dec 20, 2009, at 11:45 AM, John Adams wrote:

> On Dec 20, 2009, at 9:17 AM, shiplu wrote:
> 
>> Used all these ips.
>> 
>> 128.121.146.100
>> 128.121.146.228
>> 128.121.243.228
>> 168.143.161.20
>> 168.143.162.116
>> 168.143.162.36
>> 168.143.162.52
>> 168.143.162.68
>> 168.143.171.84
> 
> 
> It is possible your IP or network was blacklisted on our routers or firwealls.
> 
> Could you email me your source IP and I can check in our lists for you? 
> Thanks.
> 
> chrisLiveFyre, post your IP as well and we'll research.
> 
> -john
> Twitter Operations
> 



Re: [twitter-dev] 168.143.162.36... Connection timed out

2009-12-20 Thread Andrew Badera
Probably better to email your IP address directly and not display it
publicly ...

∞ Andy Badera
∞ +1 518-641-1280 Google Voice
∞ This email is: [ ] bloggable [x] ask first [ ] private
∞ Google me: http://www.google.com/search?q=andrew%20badera



On Sun, Dec 20, 2009 at 2:51 PM, shiplu  wrote:
> My external IP address is 202.56.7.116
> Its dynamic. 202.56.7.* part is fixed.
>
> --
> Shiplu Mokaddim
> My talks, http://talk.cmyweb.net
> Follow me, http://twitter.com/shiplu
> SUST Programmers, http://groups.google.com/group/p2psust
> Innovation distinguishes bet ... ... (ask Steve Jobs the rest)
>


Re: [twitter-dev] 168.143.162.36... Connection timed out

2009-12-20 Thread shiplu
My external IP address is 202.56.7.116
Its dynamic. 202.56.7.* part is fixed.

-- 
Shiplu Mokaddim
My talks, http://talk.cmyweb.net
Follow me, http://twitter.com/shiplu
SUST Programmers, http://groups.google.com/group/p2psust
Innovation distinguishes bet ... ... (ask Steve Jobs the rest)


Re: [twitter-dev] 168.143.162.36... Connection timed out

2009-12-20 Thread John Adams

On Dec 20, 2009, at 9:17 AM, shiplu wrote:


Used all these ips.

128.121.146.100
128.121.146.228
128.121.243.228
168.143.161.20
168.143.162.116
168.143.162.36
168.143.162.52
168.143.162.68
168.143.171.84



It is possible your IP or network was blacklisted on our routers or  
firwealls.


Could you email me your source IP and I can check in our lists for  
you? Thanks.


chrisLiveFyre, post your IP as well and we'll research.

-john
Twitter Operations



Re: [twitter-dev] 168.143.162.36... Connection timed out

2009-12-20 Thread shiplu
Used all these ips.

128.121.146.100
128.121.146.228
128.121.243.228
168.143.161.20
168.143.162.116
168.143.162.36
168.143.162.52
168.143.162.68
168.143.171.84

Result is same.


-- 
Shiplu Mokaddim
My talks, http://talk.cmyweb.net
Follow me, http://twitter.com/shiplu
SUST Programmers, http://groups.google.com/group/p2psust
Innovation distinguishes bet ... ... (ask Steve Jobs the rest)


Re: [twitter-dev] 168.143.162.36... Connection timed out

2009-12-20 Thread Raffi Krikorian
do you have access to a different IP address you can test from?  i've just
tested from a variety of networks (including a cellular one), and i'm able
to connect.

you could also try a different IP addresses for twitter.com run

dig twitter.com +short

each time i run it, i get a different IP address for twitter.com -- you
could also see if the other addresses are having issues for you.

On Sun, Dec 20, 2009 at 6:49 AM, shiplu  wrote:

> Telnet
>
> $ telnet 168.143.162.36 80
> Trying 168.143.162.36...
> telnet: Unable to connect to remote host: Connection timed out
>
>
> And traceroute
>
> traceroute --max-hops=64 168.143.162.36
> traceroute to 168.143.162.36 (168.143.162.36), 64 hops max, 40 byte packets
>  1  10.163.145.33 (10.163.145.33)  586.913 ms  603.874 ms  682.882 ms
>  2  10.163.145.34 (10.163.145.34)  682.872 ms  742.845 ms  783.829 ms
>  3  192.168.226.81 (192.168.226.81)  802.824 ms  825.815 ms  1042.790 ms
>  4  192.168.250.10 (192.168.250.10)  1083.787 ms  1144.770 ms  1263.762 ms
>  5  10.10.205.14 (10.10.205.14)  1303.748 ms  1304.740 ms  1485.743 ms
>  6  202.56.4.2 (202.56.4.2)  1485.733 ms  866.271 ms  923.607 ms
>  7  202.56.5.25 (202.56.5.25)  942.598 ms  980.567 ms  1003.552 ms
>  8  * * *
>  9  * * *
> 10  * * *
> 11  * * *
> 12  * * *
> 13  * * *
> 14  * * *
> 15  * * *
> 16  * * *
> 17  * * *
> 18  * * *
> 19  * * *
> 20  * * *
> 21  * * *
> 22  * * *
> 23  * * *
> 24  * * *
> 25  * * *
> 26  * * *
> 27  * * *
> 28  * * *
> 29  * * *
> 30  * * *
> 31  * * *
> 32  * * *
> 33  * * *
> 34  * * *
> 35  * * *
> 36  * * *
> 37  * * *
> 38  * * *
> 39  * * *
> 40  * * *
> 41  * * *
> 42  * * *
> 43  * * *
> 44  * * *
> 45  * * *
> 46  * * *
> 47  * * *
> 48  * * *
> 49  * * *
> 50  * * *
> 51  * * *
> 52  * * *
> 53  * * *
> 54  * * *
> 55  * * *
> 56  * * *
> 57  * * *
> 58  * * *
> 59  * * *
> 60  * * *
> 61  * * *
> 62  * * *
> 63  * * *
> 64  * * *
>
>
> --
> Shiplu Mokaddim
> My talks, http://talk.cmyweb.net
> Follow me, http://twitter.com/shiplu
> SUST Programmers, http://groups.google.com/group/p2psust
> Innovation distinguishes bet ... ... (ask Steve Jobs the rest)
>



-- 
Raffi Krikorian
Twitter Platform Team
http://twitter.com/raffi


Re: [twitter-dev] 168.143.162.36... Connection timed out

2009-12-20 Thread shiplu
Telnet

$ telnet 168.143.162.36 80
Trying 168.143.162.36...
telnet: Unable to connect to remote host: Connection timed out


And traceroute

traceroute --max-hops=64 168.143.162.36
traceroute to 168.143.162.36 (168.143.162.36), 64 hops max, 40 byte packets
 1  10.163.145.33 (10.163.145.33)  586.913 ms  603.874 ms  682.882 ms
 2  10.163.145.34 (10.163.145.34)  682.872 ms  742.845 ms  783.829 ms
 3  192.168.226.81 (192.168.226.81)  802.824 ms  825.815 ms  1042.790 ms
 4  192.168.250.10 (192.168.250.10)  1083.787 ms  1144.770 ms  1263.762 ms
 5  10.10.205.14 (10.10.205.14)  1303.748 ms  1304.740 ms  1485.743 ms
 6  202.56.4.2 (202.56.4.2)  1485.733 ms  866.271 ms  923.607 ms
 7  202.56.5.25 (202.56.5.25)  942.598 ms  980.567 ms  1003.552 ms
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
31  * * *
32  * * *
33  * * *
34  * * *
35  * * *
36  * * *
37  * * *
38  * * *
39  * * *
40  * * *
41  * * *
42  * * *
43  * * *
44  * * *
45  * * *
46  * * *
47  * * *
48  * * *
49  * * *
50  * * *
51  * * *
52  * * *
53  * * *
54  * * *
55  * * *
56  * * *
57  * * *
58  * * *
59  * * *
60  * * *
61  * * *
62  * * *
63  * * *
64  * * *


-- 
Shiplu Mokaddim
My talks, http://talk.cmyweb.net
Follow me, http://twitter.com/shiplu
SUST Programmers, http://groups.google.com/group/p2psust
Innovation distinguishes bet ... ... (ask Steve Jobs the rest)


Re: [twitter-dev] 168.143.162.36... Connection timed out

2009-12-20 Thread Raffi Krikorian
yes - for example, on OS X, i would run

[ra...@tw-mbp13-raffi twitter (api_language_code)]$ *telnet 168.143.162.36
80*
Trying 168.143.162.36...
Connected to 168.143.162.36.
Escape character is '^]'.
^]
telnet> quit
Connection closed.

showing i can establish a connection. and then also

[ra...@tw-mbp13-raffi twitter (api_language_code)]$ *traceroute
168.143.162.36*
traceroute to 168.143.162.36 (168.143.162.36), 64 hops max, 40 byte packets

to show what route packets are taking.

On Sun, Dec 20, 2009 at 6:30 AM, Scott Haneda  wrote:

> On Dec 20, 2009, at 5:53 AM, shiplu  wrote:
>
> Why is this?
>
> $ curl -iv http://twitter.com/shiplu
> * About to connect() to twitter.com port 80 (#0)
> *   Trying 168.143.162.36... Connection timed out
> * couldn't connect to host
> * Closing connection #0
> curl: (7) couldn't connect to host
>
> I am facing this for almost 3-4 days.
>
>
> Telnet to the ip with correct port, run traceroute or mtr. Report your
> results back here.
> --
> Scott
> (Sent from a mobile device)
>



-- 
Raffi Krikorian
Twitter Platform Team
http://twitter.com/raffi


Re: [twitter-dev] 168.143.162.36... Connection timed out

2009-12-20 Thread Scott Haneda

On Dec 20, 2009, at 5:53 AM, shiplu  wrote:


Why is this?

$ curl -iv http://twitter.com/shiplu
* About to connect() to twitter.com port 80 (#0)
*   Trying 168.143.162.36... Connection timed out
* couldn't connect to host
* Closing connection #0
curl: (7) couldn't connect to host

I am facing this for almost 3-4 days.


Telnet to the ip with correct port, run traceroute or mtr. Report your  
results back here.
--  
Scott

(Sent from a mobile device)

[twitter-dev] 168.143.162.36... Connection timed out

2009-12-20 Thread shiplu
Why is this?

$ curl -iv http://twitter.com/shiplu
* About to connect() to twitter.com port 80 (#0)
*   Trying 168.143.162.36... Connection timed out
* couldn't connect to host
* Closing connection #0
curl: (7) couldn't connect to host

I am facing this for almost 3-4 days.

-- 
Shiplu Mokaddim
My talks, http://talk.cmyweb.net
Follow me, http://twitter.com/shiplu
SUST Programmers, http://groups.google.com/group/p2psust
Innovation distinguishes bet ... ... (ask Steve Jobs the rest)