When I'm at the office, I can browser to twitter.com and log in. No problem.

When I'm at my wife's computer at home, ditto.

When, however, my laptop is at home (behind the same NAT-ural router), twitter.com never responds. It does not matter whether I use Chrome, Firefox, or Safari.

I'm puzzled as to how Twitter can even distinguish the different computers at my house, and I have been unable to identify a 'front door' at twitter to whom I can inquire. Any ideas?

More information:

/Users/benson/x/oap-jas-gcoref ping twitter.com
PING twitter.com ( 56 data bytes
64 bytes from icmp_seq=0 ttl=248 time=106.766 ms
64 bytes from icmp_seq=1 ttl=248 time=107.800 ms

traceroute: Warning: twitter.com has multiple addresses; using
traceroute to twitter.com (, 64 hops max, 52 byte packets
1  wireless_broadband_router (  1.182 ms  0.969 ms  0.901 ms
2  l100.bstnma-vfttp-106.verizon-gni.net (  7.515 ms  7.186 ms  7.218 ms
3  g9-0-2-1706.bstnma-lcr-07.verizon-gni.net (  7.149 ms  6.877 ms     7.531 ms
4  * * *
5  ge-0-0-0-0.ny325-bb-rtr1.verizon-gni.net (  22.198 ms  14.758 ms  15.089 ms
6  0.so-0-0-0.xt1.nyc4.alter.net (  17.091 ms  19.365 ms  17.856 ms
7  0.ae3.br2.nyc4.alter.net (  14.671 ms  14.418 ms  15.333 ms
8 (  15.008 ms  72.287 ms  14.875 ms
9  vlan51.ebr1.newyork2.level3.net (  14.711 ms  14.531 ms  17.194 ms
10  ae-3-3.ebr2.washington1.level3.net (  22.859 ms  22.638 ms  21.937 ms
11  ae-82-82.csw3.washington1.level3.net (  22.879 ms
ae-72-72.csw2.washington1.level3.net (  26.549 ms  24.565 ms
12  ae-2-70.edge2.washington4.level3.net (  28.017 ms  29.232 ms  27.924 ms
13  twitter-inc.edge2.washington4.level3.net (  29.810 ms  29.826 ms  29.646 ms
14  xe-1-3-1.pao1-cr2.twttr.com (  97.955 ms
xe-0-2-0.sjc2-cr2.twttr.com (  89.643 ms
xe-1-3-1.pao1-cr2.twttr.com (  94.227 ms
15  xe-1-0-0.smf1-er1.twttr.com (  97.417 ms
xe-11-0-0.smf1-er1.twttr.com (  91.215 ms
xe-1-0-0.smf1-er2.twttr.com (  99.407 ms
16  r-199-59-148-10.twttr.com (  97.575 ms  101.617 ms  92.797 ms

On my wife's computer:

new-host-2:~ karenmackenzie$ ping twitter.com
PING twitter.com ( 56 data bytes
64 bytes from icmp_seq=0 ttl=250 time=104.334 ms
64 bytes from icmp_seq=1 ttl=250 time=106.221 ms

The IP addresses are quite different ... but browsing to this address also just sits there, no response. Just for fun I tried:

telnet http

on both machines. Hers gets a connection. Mine just sits there ... no connection.

This problem is completely unique to twitter. I have no problem talking to anything else. AFAIK there are no proxy settings on my laptop at all.

  • I don't think is Twitter, I think it's a laptop setting, like a proxy or something similar. Can you ping or traceroute twitter.com from your laptop?
    – Alex
    Commented Jan 16, 2012 at 13:54
  • My first guess is that it has something to do with the DNS settings. You can change it to use OpenDNS or Google's DNS servers and try. Commented Jan 16, 2012 at 13:59
  • 2
    Is Twitter the only site that affected? If not this would be a better question for Super User.
    – ChrisF
    Commented Jan 16, 2012 at 14:18
  • Only twitter. Nothing else. No proxies are configured on this machine.
    – bmargulies
    Commented Jan 16, 2012 at 14:26
  • @bmargulies Try tracerouting it and see if and where it stops. From command line on your machine, not using an online web service.
    – Alex
    Commented Jan 16, 2012 at 14:47

1 Answer 1


And the answer turns out to be:

Some insane policy in my Verizon router blocked some web sites (including twitter and newscenter.verizon.com). In particular, anything connected via Wifi to my timecapsule, and then by wire to the VZ router, encountered this problem. Anything wired directly to the VZ router did not.

Since the VZ support person could not be bothered to actually investigate the configuration of my router, and rather insisted that I do a hard reset, I can't tell what in particular other than cosmic rays or bad luck produced this situation.

Yoo, Hoo, diamond mods: perhaps this should migrate to superuser?

Not the answer you're looking for? Browse other questions tagged or ask your own question.