Connection slow when accessing particular IP

[#1]

A large part of my problem is that after I ran a trace route I noted that each time it seems to drop off when accessing the below mentioned IP address…and always happens near the same time span around the same days - weekdays between 9 pm and 1 am Eastern standard.

I am familiar that sometimes there being remote servers that exist within some ISP providers that may have routing issues, sometimes even unbeknown to Verizon if not given any specific customers feedback to go on.
I can connect, but very slow transmission speeds and times with occasional dropped packets. One of the addresses I have tried to access with very slow connection is as follows…

https://pacsdb.lmcmc.com

Name: pacsdb.lmcmc.com
Address: 108.176.23.141

Hope Verizon can look into this matter.

Look forward to reply.

Thanks
Dishant

[#2]

Do you have a traceroute  from the time frame that it is slow?

[#3]

Hi,

Thanks for the reply. Here's the traceroute when connection it slow to the particular server:

C:\Users\ust>tracert 108.176.23.141

Tracing route to pascdb.lmcmc.com [108.176.23.141]

over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]

  2     1 ms     1 ms     1 ms  L100.RCMDVA-VFTTP-15.verizon-gni.net

  3     4 ms     3 ms     3 ms  G0-4-4-7.RCMDVA-LCR-22.verizon-gni.net [100.41.1

94.100]

  4    63 ms    27 ms     8 ms  ge-4-2-0-0.ATL01-BB-RTR2.verizon-gni.net [130.81

.29.112]

  5     8 ms     7 ms     7 ms  0.xe-10-1-1.XL2.IAD8.ALTER.NET [152.63.40.142]

  6     8 ms     7 ms     7 ms  0.xe-11-0-0.GW12.IAD8.ALTER.NET [152.63.35.90]

  7    21 ms    20 ms     *     tba.customer.alter.net [204.148.11.86]

  8    30 ms    30 ms    30 ms  bu-ether33.asbnva1611w-bcr00.tbone.rr.com [66.10

9.6.182]

  9    30 ms    33 ms    29 ms  bu-ether32.vinnva0510w-bcr00.tbone.rr.com [107.1

4.19.165]

10    31 ms    27 ms    27 ms  bu-ether22.nwrknjmd67w-bcr00.tbone.rr.com [66.10

9.9.31]

11    28 ms    30 ms    31 ms  66.109.6.79

12    30 ms    28 ms    28 ms  24.29.148.74

13    30 ms    29 ms    30 ms  rdc-69-193-225-25.nyc.bc.twcable.com [69.193.225

.25]

14    28 ms    29 ms    29 ms  rrcs-108-176-17-46.nyc.biz.rr.com [108.176.17.46

]

15     *        *        *     Request timed out.

16     *        *        *     Request timed out.

17     *        *        *     Request timed out.

18     *        *        *     Request timed out.

19     *        *        *     Request timed out.

20     *        *        *     Request timed out.

21     *        *        *     Request timed out.

22     *        *        *     Request timed out.

23     *        *        *     Request timed out.

24     *        *        *     Request timed out.

25     *        *        *     Request timed out.

26     *        *        *     Request timed out.

27     *        *        *     Request timed out.

28     *        *        *     Request timed out.

29     *        *        *     Request timed out.

30     *        *        *     Request timed out.

Trace complete.

Thanks,

Dishant

[#4]

The trace does not look bad.. What part are you complaining about?

[#5]

doesnt look bad?

[#6]

As this thread is now over two years old, it will be locked in order to keep discussions current. If you have the same or a similar question/issue we invite you to start a new thread on the topic.