[caiu] Twitter OFF

[Alexandre Martini - Tecwave]

GVT Rs ok!

    1  187.58.132.253 4ms 4ms 4ms
    2  189.59.252.253 5ms 8ms 8ms
    3    189.59.248.9 23ms 23ms 24ms
    4 187.115.214.214 24ms 24ms 24ms
    5     64.208.26.5 22ms 22ms 22ms
    6   67.16.142.237 22ms 22ms 22ms
    7     67.16.139.2 136ms 136ms 158ms
    8    67.16.142.54 136ms 136ms 150ms
    9  208.178.58.198 136ms 136ms 136ms
   10    64.125.27.62 136ms 136ms 136ms
                       mpls-label=413073
   11   64.125.27.169 162ms 162ms 162ms
                       mpls-label=758651
   12   64.125.26.229 229ms 228ms 225ms
                       mpls-label=486212
   13    64.125.28.17 210ms 210ms 210ms
                       mpls-label=336482
   14   64.125.30.174 209ms 209ms 256ms
   15    209.66.115.2 208ms 208ms 208ms
   16   199.16.159.53 214ms 216ms 213ms
   17  199.59.149.198 216ms 217ms 216ms

[]s

Alexandre Martini
Network Admin - Tecwave Internet
:: http://www.tecwave.com.br ::
INOC-DBA 262695*100


Em 15/11/2011 11:51, Rafael Galdino da Cunha escreveu:
> Alguem com problema com o Twitter?
>
>
> noc at NOC-06:~$ traceroute www.twitter.com
> traceroute to www.twitter.com (199.59.149.230), 30 hops max, 60 byte packets
>   1  192.168.1.111 (192.168.1.111)  1.059 ms  1.029 ms  1.016 ms
>   2  * * *
>   3  * * *
>   4  * * *
>   5  * * *
>   6  * 201-12-241-201.intelignet.com.br (201.12.241.201)  63.357 ms  63.472
> ms
>   7  137.246.40.189.isp.timbrasil.com.br (189.40.246.137)  80.443 ms
> 141.246.40.189.isp.timbrasil.com.br (189.40.246.141)  72.350 ms  72.481 ms
>   8  ge2-0-0.sanpaolo1.spa.seabone.net (195.22.219.17)  65.187 ms  65.331 ms
> ge2-0-0.sanpaolo2.spa.seabone.net (195.22.219.25)  69.886 ms
>   9  te7-2.miami7.mia.seabone.net (195.22.199.111)  171.172 ms
> te3-4.miami7.mia.seabone.net (195.22.199.97)  177.601 ms
> te7-2.miami7.mia.seabone.net (195.22.199.111)  171.356 ms
> 10  te-7-4.car2.miami1.level3.net (63.209.150.165)  177.751 ms  177.894 ms
>   178.690 ms
> 11  4.69.138.123 (4.69.138.123)  171.301 ms  172.959 ms  172.004 ms
> 12  ae-2-2.ebr2.atlanta2.level3.net (4.69.140.142)  193.086 ms  192.847 ms
>   194.520 ms
> 13  ae-73-73.ebr3.atlanta2.level3.net (4.69.148.253)  182.143 ms  183.011
> ms  183.124 ms
> 14  ae-2-2.ebr1.washington1.level3.net (4.69.132.86)  201.279 ms  199.584
> ms  200.506 ms
> 15  ae-61-61.csw1.washington1.level3.net (4.69.134.130)  209.800 ms
> ae-91-91.csw4.washington1.level3.net (4.69.134.142)  208.137 ms
> ae-81-81.csw3.washington1.level3.net (4.69.134.138)  202.689 ms
> 16  ae-2-70.edge2.washington4.level3.net (4.69.149.80)  201.210 ms
> ae-3-80.edge2.washington4.level3.net (4.69.149.144)  204.167 ms
> ae-1-60.edge2.washington4.level3.net (4.69.149.16)  203.946 ms
> 17  twitter-inc.edge2.washington4.level3.net (4.53.114.102)  238.116 ms
>   237.945 ms  238.227 ms
> 18  * * *
> 19  * * *
> 20  * * *
> 21  * * *
> 22  * * *
> 23  * * *
> 24  * * *
> 25  * * *
> 26  * * *
> 27  * * *
> 28  * * *
> 29  * * *
> 30  * * *
>
> aparentemente o site não pinga e nem abre.
> mais alguem com problema?
>
> att.
> Rafael Galdino
> _______________________________________________
> caiu mailing list
> caiu at eng.registro.br
> https://eng.registro.br/mailman/listinfo/caiu
>
>
> -->  PARA SAIR DA LISTA SIGA AS INSTRUÇÕES em:
>
> https://eng.registro.br/mailman/options/caiu
>