[caiu] Lentidão para a NET RJ

Pedro Alves pedro em moebius.com.br
Terça Julho 16 12:10:13 BRT 2013


Nossa empresa é uma operadora baseada no Rio de Janeiro.
Estamos conectados no PTT RJ  e SP diretamente.

C:\Users\Pedro>fping  179.223.68.1 -c -w20 -t200

Fast pinger version 3.00
(c) Wouter Dhondt (http://www.kwakkelflap.com)

socket() - WSAError: 10013
switching to ICMP dll
Pinging 179.223.68.1 with 32 bytes of data every 200 ms:

Reply[1] from 179.223.68.1: bytes=32 time=33.3 ms TTL=49
Reply[2] from 179.223.68.1: bytes=32 time=32.4 ms TTL=49
Reply[3] from 179.223.68.1: bytes=32 time=50.9 ms TTL=49
Reply[4] from 179.223.68.1: bytes=32 time=59.6 ms TTL=49
Reply[5] from 179.223.68.1: bytes=32 time=36.0 ms TTL=49
Reply[6] from 179.223.68.1: bytes=32 time=73.0 ms TTL=49
Reply[7] from 179.223.68.1: bytes=32 time=55.7 ms TTL=49
Reply[8] from 179.223.68.1: bytes=32 time=49.7 ms TTL=49
Reply[9] from 179.223.68.1: bytes=32 time=49.1 ms TTL=49
Reply[10] from 179.223.68.1: bytes=32 time=47.4 ms TTL=49
Reply[11] from 179.223.68.1: bytes=32 time=46.3 ms TTL=49
Reply[12] from 179.223.68.1: bytes=32 time=53.4 ms TTL=49
Reply[13] from 179.223.68.1: bytes=32 time=50.1 ms TTL=49
Reply[14] from 179.223.68.1: bytes=32 time=49.2 ms TTL=49
Reply[15] from 179.223.68.1: bytes=32 time=45.4 ms TTL=49
Reply[16] from 179.223.68.1: bytes=32 time=59.8 ms TTL=49
Reply[17] from 179.223.68.1: bytes=32 time=74.2 ms TTL=49
Reply[18] from 179.223.68.1: bytes=32 time=58.3 ms TTL=49
Reply[19] from 179.223.68.1: bytes=32 time=75.1 ms TTL=49
179.223.68.1: request timed out
Reply[21] from 179.223.68.1: bytes=32 time=56.2 ms TTL=49
Reply[22] from 179.223.68.1: bytes=32 time=44.5 ms TTL=49
Reply[23] from 179.223.68.1: bytes=32 time=39.5 ms TTL=49
Reply[24] from 179.223.68.1: bytes=32 time=64.5 ms TTL=49
Reply[25] from 179.223.68.1: bytes=32 time=47.3 ms TTL=49
Reply[26] from 179.223.68.1: bytes=32 time=42.9 ms TTL=49
179.223.68.1: request timed out
Reply[28] from 179.223.68.1: bytes=32 time=48.8 ms TTL=49
Reply[29] from 179.223.68.1: bytes=32 time=39.4 ms TTL=49
179.223.68.1: request timed out
Reply[31] from 179.223.68.1: bytes=32 time=49.7 ms TTL=49
Reply[32] from 179.223.68.1: bytes=32 time=50.6 ms TTL=49
Reply[33] from 179.223.68.1: bytes=32 time=60.3 ms TTL=49
Reply[34] from 179.223.68.1: bytes=32 time=56.2 ms TTL=49
Reply[35] from 179.223.68.1: bytes=32 time=69.8 ms TTL=49
Reply[36] from 179.223.68.1: bytes=32 time=61.1 ms TTL=49
Reply[37] from 179.223.68.1: bytes=32 time=42.7 ms TTL=49
Reply[38] from 179.223.68.1: bytes=32 time=55.5 ms TTL=49
Reply[39] from 179.223.68.1: bytes=32 time=51.8 ms TTL=49
Reply[40] from 179.223.68.1: bytes=32 time=44.8 ms TTL=49
Reply[41] from 179.223.68.1: bytes=32 time=55.3 ms TTL=49
Reply[42] from 179.223.68.1: bytes=32 time=57.4 ms TTL=49
Reply[43] from 179.223.68.1: bytes=32 time=47.1 ms TTL=49
Reply[44] from 179.223.68.1: bytes=32 time=42.4 ms TTL=49
Reply[45] from 179.223.68.1: bytes=32 time=56.0 ms TTL=49
Reply[46] from 179.223.68.1: bytes=32 time=56.2 ms TTL=49
Reply[47] from 179.223.68.1: bytes=32 time=55.0 ms TTL=49
Reply[48] from 179.223.68.1: bytes=32 time=39.3 ms TTL=49
Reply[49] from 179.223.68.1: bytes=32 time=49.4 ms TTL=49
Reply[50] from 179.223.68.1: bytes=32 time=59.4 ms TTL=49
Reply[51] from 179.223.68.1: bytes=32 time=39.3 ms TTL=49
Reply[52] from 179.223.68.1: bytes=32 time=40.0 ms TTL=49
Reply[53] from 179.223.68.1: bytes=32 time=59.1 ms TTL=49
179.223.68.1: request timed out

Ping statistics for 179.223.68.1:
         Packets: Sent = 54, Received = 50, Lost = 4 (7% loss)
Approximate round trip times in milli-seconds:
         Minimum = 32.4 ms, Maximum = 75.1 ms, Average = 51.6 ms

C:\Users\Pedro>tracert -d 179.223.68.1

Rastreando a rota para 179.223.68.1 com no máximo 30 saltos

   1     1 ms    <1 ms    <1 ms  10.2.40.254
   2     1 ms     1 ms     1 ms  189.45.5.118
   3     3 ms     2 ms    13 ms  200.165.141.37
   4    16 ms    15 ms    15 ms  200.164.13.203
   5    81 ms    68 ms    29 ms  200.164.40.24
   6    31 ms   145 ms    31 ms  200.164.11.30
   7    29 ms    21 ms    19 ms  200.199.54.93
   8    32 ms    31 ms    25 ms  200.211.219.113
   9    37 ms    35 ms    35 ms  200.230.231.10
  10    33 ms    27 ms    36 ms  200.230.251.5
  11    25 ms    27 ms    27 ms  200.244.140.61
  12    24 ms    16 ms    22 ms  200.167.53.6
  13    42 ms    39 ms    54 ms  179.223.68.1

Rastreamento concluído.

Pedro Alves
Diretor de Tecnologia
21 8762-1264  /  21 2294-1087
21 7701-7742  / 87 * 148311
pedro at moebius.com.br

Em 16/07/2013 11:53, Bruno Mattos escreveu:
> Pedro,
>
> Você é cliente NET? Poderia, por gentileza, realizar os mesmos testes no
> e-mail acima para o ip 179.223.68.1?
>
> Referente aos testes com direção ao site www.dialhost.com.br, existem
> algumas restrições com relação ao número de pacotes ICMP, por isso, o
> grande número de pacotes "perdidos".
>
> Atenciosamente,
>
> *Bruno Mattos* | Analista de Redes
> CCENT, CCNA, CCIP
> brunomattos at dialhost.com.br
> *DialHost Internet* | http://www.dialhost.com.br
> BH: (31) 3519-9800
> RJ: (21) 3512-9800
> SP: (11) 3514-9800
> DF: (61) 3246-9890
> GO: (62) 3412-9890
> PR: (41) 3012-0000
> BA: (71) 3512-9800
> PE: (81) 3771-9800
> CE: (85) 3771-9800
>
> Em 16 de julho de 2013 11:43, Pedro Alves <pedro at moebius.com.br> escreveu:
>
>> Amigo,
>>
>>    O trace completa normal...
>>
>> Rastreando a rota para www.dialhost.com.br [177.52.160.69]
>> com no máximo 30 saltos:
>>
>>    1     1 ms    <1 ms    <1 ms  10.2.40.254
>>    2    <1 ms    <1 ms    <1 ms  189-45-5-116.nbtelecom.com.br[189.45.5.116]
>>    3    21 ms    22 ms    21 ms  as16735.rj.ptt.br [200.219.138.6]
>>    4    22 ms    21 ms    22 ms  et-4-0-0-0.core-b.fac001.ctbc.**com.br<http://et-4-0-0-0.core-b.fac001.ctbc.com.br>
>> [201.48.44.237]
>>    5    24 ms    24 ms    24 ms  ae2-0.core-b.ula001.ctbc.com.**br<http://ae2-0.core-b.ula001.ctbc.com.br>[201.48.44.9]
>>    6    24 ms    24 ms    25 ms  et-3-0-0-0.core-a.ula001.ctbc.**com.br<http://et-3-0-0-0.core-a.ula001.ctbc.com.br>[201.48.44.5]
>>    7    33 ms    32 ms    32 ms  xe-2-0-0-0.edge-a.bhe515.ctbc.**com.br<http://xe-2-0-0-0.edge-a.bhe515.ctbc.com.br>[201.48.46.18]
>>    8    34 ms    33 ms    33 ms  201-016-233-197.static.**
>> ctbctelecom.com.br <http://201-016-233-197.static.ctbctelecom.com.br>[201.16.233.197]
>>    9    30 ms    30 ms    30 ms  172.16.100.2
>>   10    29 ms    29 ms    29 ms  dialhost.com.br [177.52.160.69]
>>
>> Rastreamento concluído.
>>
>> Ja o ping mais rápido perde muito pacote...
>>
>> C:\Users\Pedro>fping  www.dialhost.com.br -c -w20 -t200
>>
>> Fast pinger version 3.00
>> (c) Wouter Dhondt (http://www.kwakkelflap.com)
>>
>> socket() - WSAError: 10013
>> switching to ICMP dll
>> Pinging www.dialhost.com.br [177.52.160.69] with 32 bytes of data every
>> 200 ms:
>>
>> Reply[1] from www.dialhost.com.br: bytes=32 time=30.7 ms TTL=55
>> Reply[2] from www.dialhost.com.br: bytes=32 time=31.1 ms TTL=55
>> Reply[3] from www.dialhost.com.br: bytes=32 time=30.0 ms TTL=55
>> Reply[4] from www.dialhost.com.br: bytes=32 time=30.2 ms TTL=55
>> Reply[5] from www.dialhost.com.br: bytes=32 time=30.8 ms TTL=55
>> 177.52.160.69: request timed out
>> Reply[7] from www.dialhost.com.br: bytes=32 time=30.9 ms TTL=55
>> 177.52.160.69: request timed out
>> 177.52.160.69: request timed out
>> Reply[10] from www.dialhost.com.br: bytes=32 time=30.4 ms TTL=55
>> 177.52.160.69: request timed out
>> 177.52.160.69: request timed out
>> Reply[13] from www.dialhost.com.br: bytes=32 time=30.6 ms TTL=55
>> 177.52.160.69: request timed out
>> 177.52.160.69: request timed out
>> Reply[16] from www.dialhost.com.br: bytes=32 time=30.7 ms TTL=55
>> 177.52.160.69: request timed out
>> 177.52.160.69: request timed out
>> Reply[19] from www.dialhost.com.br: bytes=32 time=30.2 ms TTL=55
>> 177.52.160.69: request timed out
>> 177.52.160.69: request timed out
>> Reply[22] from www.dialhost.com.br: bytes=32 time=30.3 ms TTL=55
>> 177.52.160.69: request timed out
>> 177.52.160.69: request timed out
>> Reply[25] from www.dialhost.com.br: bytes=32 time=30.2 ms TTL=55
>> 177.52.160.69: request timed out
>> 177.52.160.69: request timed out
>> Reply[28] from www.dialhost.com.br: bytes=32 time=31.6 ms TTL=55
>> 177.52.160.69: request timed out
>> 177.52.160.69: request timed out
>> Reply[31] from www.dialhost.com.br: bytes=32 time=30.1 ms TTL=55
>> 177.52.160.69: request timed out
>> 177.52.160.69: request timed out
>> Reply[34] from www.dialhost.com.br: bytes=32 time=30.1 ms TTL=55
>> 177.52.160.69: request timed out
>> 177.52.160.69: request timed out
>> Reply[37] from www.dialhost.com.br: bytes=32 time=30.4 ms TTL=55
>> 177.52.160.69: request timed out
>>
>> Ping statistics for www.dialhost.com.br:
>>          Packets: Sent = 38, Received = 16, Lost = 22 (57% loss)
>> Approximate round trip times in milli-seconds:
>>          Minimum = 30.0 ms, Maximum = 31.6 ms, Average = 30.5 ms
>>
>>
>>
>> Pedro Alves
>> Diretor de Tecnologia
>> 21 8762-1264  /  21 2294-1087
>> 21 7701-7742  / 87 * 148311
>> pedro at moebius.com.br
>>
>> Em 16/07/2013 10:49, Bruno Mattos escreveu:
>>
>>> Prezados,
>>>
>>> Verifiquei grande lentidão para a rede 179.223.0.0/17, referente ao
>>> AS28573, Net Serviços de Comunicação S.A, oriundo da rede da Algar
>>> Telecom. Alguém mais notou este mesmo problema?
>>>
>>> Estatísticas do Ping para 179.223.68.1:
>>>       Pacotes: Enviados = 393, Recebidos = 333, Perdidos = 60 (15% de
>>> perda),
>>> Aproximar um número redondo de vezes em milissegundos:
>>>       Mínimo = 86ms, Máximo = 256ms, Média = 94ms
>>>
>>>
>>>
>>> Atenciosamente,
>>>
>>> *Bruno Mattos* | Analista de Redes
>>> CCENT, CCNA, CCIP
>>> brunomattos at dialhost.com.br
>>> *DialHost Internet* | http://www.dialhost.com.br
>>>
>>> BH: (31) 3519-9800
>>> RJ: (21) 3512-9800
>>> SP: (11) 3514-9800
>>> DF: (61) 3246-9890
>>> GO: (62) 3412-9890
>>> PR: (41) 3012-0000
>>> BA: (71) 3512-9800
>>> PE: (81) 3771-9800
>>> CE: (85) 3771-9800
>>> ______________________________**_________________
>>> caiu mailing list
>>> caiu at eng.registro.br
>>> https://eng.registro.br/**mailman/listinfo/caiu<https://eng.registro.br/mailman/listinfo/caiu>
>>>
>>>
>>> --> PARA SAIR DA LISTA SIGA AS INSTRUÇÕES em:
>>>
>>> https://eng.registro.br/**mailman/options/caiu<https://eng.registro.br/mailman/options/caiu>
>>>
>>>
>> ______________________________**_________________
>> caiu mailing list
>> caiu at eng.registro.br
>> https://eng.registro.br/**mailman/listinfo/caiu<https://eng.registro.br/mailman/listinfo/caiu>
>>
>>
>> --> PARA SAIR DA LISTA SIGA AS INSTRUÇÕES em:
>>
>> https://eng.registro.br/**mailman/options/caiu<https://eng.registro.br/mailman/options/caiu>
>>
> _______________________________________________
> 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
>



More information about the caiu mailing list