yes - for example, on OS X, i would run
[ra...@tw-mbp13-raffi twitter (api_language_code)]$ *telnet 18.104.22.168
Connected to 22.214.171.124.
Escape character is '^]'.
showing i can establish a connection. and then also
[ra...@tw-mbp13-raffi twitter (api_language_code)]$ *traceroute
traceroute to 126.96.36.199 (188.8.131.52), 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 184.108.40.206... 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.
> (Sent from a mobile device)
Twitter Platform Team