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 <talkli...@newgeo.com> wrote:

> On Dec 20, 2009, at 5:53 AM, shiplu <shiplu....@gmail.com> wrote:
>
> Why is this?
>
> $ curl -iv <http://twitter.com/shiplu>http://twitter.com/shiplu
> * About to connect() to <http://twitter.com>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

Reply via email to