[caiu] Problema acesso rede 209.134.48.10
Daniel Zanutti
daniel.zanutti em gmail.com
Terça Maio 24 11:54:36 BRT 2011
Pessoal
Alguém consegue acessar a rede 209.134.48.10?
Da minha rede nem pinga, de outras redes está pingando mas o traceroute não
chega no host.
Rede local:
Rastreando a rota para 209.134.48.10 com no máximo 30 saltos
1 19 ms 2 ms 11 ms XXX
2 6 ms 2 ms 2 ms XXX
3 5 ms 5 ms 3 ms XXX
4 6 ms 5 ms 1 ms XXX
5 3 ms 11 ms 33 ms 73.3.125.189.static.impsat.net.br[189.125.3.73]
6 6 ms 7 ms 8 ms so0-1-1-2488m.scr1.gru1.gblx.net[67.17.111.57]
7 219 ms 203 ms 204 ms vlan69.csw1.NewYork1.Level3.net [4.68.16.62]
8 222 ms 148 ms 146 ms ae-62-62.ebr2.NewYork1.Level3.net[4.69.148.33]
9 163 ms 211 ms 195 ms ae-6-6.ebr2.NewYork2.Level3.net[4.69.141.22]
10 210 ms 177 ms 228 ms ae-2-2.ebr1.Chicago1.Level3.net[4.69.132.65]
11 251 ms 213 ms 195 ms ae-1-100.ebr2.Chicago1.Level3.net[4.69.132.42]
12 213 ms 208 ms 203 ms
xe11-0-0-0-grtwaseq4.red.telefonica-wholesale.ne
t [213.140.36.229]
13 166 ms 158 ms 209 ms xe-11-2-0.edge3.Washington4.Level3.net[4.53.112
.17]
14 219 ms 142 ms 262 ms vlan90.csw4.Washington1.Level3.net[4.69.149.254
]
15 180 ms 215 ms 191 ms ae-62-62.ebr2.Washington1.Level3.net[4.69.134.1
45]
16 243 ms 200 ms 203 ms ae-5-5.ebr2.Washington12.Level3.net[4.69.143.22
2]
17 216 ms 152 ms 269 ms ae-6-6.ebr2.Chicago2.Level3.net[4.69.148.146]
18 190 ms 203 ms 166 ms ae-5-5.ebr2.Chicago1.Level3.net[4.69.140.193]
19 190 ms 203 ms 202 ms ae-4-4.car2.StLouis1.Level3.net[4.69.132.189]
20 * * * Esgotado o tempo limite do pedido.
21 * * * Esgotado o tempo limite do pedido.
22 * * * Esgotado o tempo limite do pedido.
23 * * * Esgotado o tempo limite do pedido.
24 * * * Esgotado o tempo limite do pedido.
25 * * * Esgotado o tempo limite do pedido.
26 * * * Esgotado o tempo limite do pedido.
27 * * * Esgotado o tempo limite do pedido.
28 * * * Esgotado o tempo limite do pedido.
Rede que pinga:
traceroute to 209.134.48.10 (209.134.48.10), 30 hops max, 40 byte packets
1 msrvs4.hospedagem-de-site.info (189.1.162.125) 0.816 ms 0.819 ms
0.816 ms
2 35.175.1.189.in-addr.backbone-br.com.br (189.1.175.35) 0.795 ms 0.796
ms 0.795 ms
3 13.128.17.187.redenetworks.net.br (187.17.128.13) 1.028 ms 1.306 ms
1.016 ms
4 84.16.7.145 (84.16.7.145) 1.296 ms 1.292 ms 1.288 ms
5 xe5-0-6-0-grtsaosi3.red.telefonica-wholesale.net (213.140.38.190)
146.427 ms 146.420 ms 146.404 ms
6 xe5-0-0-0-grtmiabr3.red.telefonica-wholesale.net (213.140.43.109)
112.277 ms 115.141 ms 115.120 ms
7 xe0-0-0-0-grtwaseq4.red.telefonica-wholesale.net (213.140.36.153)
150.757 ms
xe7-1-0-0-grtwaseq4.red.telefonica-wholesale.net.122.142.94.in-addr.arpa
(94.142.122.157) 184.578 ms
xe11-0-0-0-grtwaseq4.red.telefonica-wholesale.net (213.140.36.229) 157.487
ms
8 xe-11-3-0.edge3.Washington4.Level3.net (4.53.112.9) 170.382 ms
xe-11-2-0.edge3.Washington4.Level3.net (4.53.112.17) 150.335 ms
xe-11-0-0.edge3.Washington4.Level3.net (4.53.112.33) 166.262 ms
9 vlan60.csw1.washington1.level3.net (4.69.149.62) 169.732 ms
vlan90.csw4.Washington1.Level3.net (4.69.149.254) 159.311 ms 156.917 ms
10 ae-72-72.ebr2.Washington1.Level3.net (4.69.134.149) 152.424 ms
ae-92-92.ebr2.Washington1.Level3.net (4.69.134.157) 166.619 ms
ae-72-72.ebr2.Washington1.Level3.net (4.69.134.149) 166.596 ms
11 ae-5-5.ebr2.Washington12.Level3.net (4.69.143.222) 155.393 ms 157.946
ms 158.243 ms
12 ae-6-6.ebr2.Chicago2.Level3.net (4.69.148.146) 156.580 ms 170.414 ms
167.004 ms
13 ae-5-5.ebr2.Chicago1.Level3.net (4.69.140.193) 154.280 ms 170.379 ms
164.603 ms
14 ae-4-4.car2.stlouis1.level3.net (4.69.132.189) 158.386 ms 173.923 ms
158.368 ms
15 catalyst-so.car2.stlouis1.level3.net (4.53.162.114) 246.263 ms 259.954
ms 259.514 ms
16 rp-4948-l3-02-svi-16.redplaid.com (208.74.31.196) 241.942 ms 252.895
ms 239.344 ms
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Alguém sabe o que ocorre?
Obrigado
Daniel Zanutti Gomes
Mais detalhes sobre a lista de discussão caiu