Websites taken ages - Bad Latency

[RichardG]

Anyone using Neotel experiencing bad latency..
Just pinged Neotel website.
Sites taken ages to load - even disconnected and re-connected to the network makes no difference


C:\>ping -n 10 www.neotel.co.za

Pinging www.neotel.co.za [196.34.133.113] with 32 bytes of data:

Reply from 196.34.133.113: bytes=32 time=1168ms TTL=56
Reply from 196.34.133.113: bytes=32 time=946ms TTL=56
Reply from 196.34.133.113: bytes=32 time=1411ms TTL=56
Reply from 196.34.133.113: bytes=32 time=1593ms TTL=56
Reply from 196.34.133.113: bytes=32 time=215ms TTL=56
Reply from 196.34.133.113: bytes=32 time=1435ms TTL=56
Reply from 196.34.133.113: bytes=32 time=1559ms TTL=56
Reply from 196.34.133.113: bytes=32 time=1638ms TTL=56
Reply from 196.34.133.113: bytes=32 time=1876ms TTL=56
Reply from 196.34.133.113: bytes=32 time=269ms TTL=56

Ping statistics for 196.34.133.113:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 215ms, Maximum = 1876ms, Average = 1211ms

[HavocXphere]

I would have thought that they fixed the latency issues by now.

When they put up their website it also had a mad ping...but now it appears to be fine (via ADSL).

Maybe post a tracert output...that would probably be more helpful in identifying the problem.

[orin76]

Just pinged them on neoconnect prime:



Pinging www.neotel.co.za [196.34.133.113] with 32 bytes of data:
Reply from 196.34.133.113: bytes=32 time=9ms TTL=55
Reply from 196.34.133.113: bytes=32 time=9ms TTL=55
Reply from 196.34.133.113: bytes=32 time=10ms TTL=55
Reply from 196.34.133.113: bytes=32 time=8ms TTL=55

Ping statistics for 196.34.133.113:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 10ms, Average = 9ms


Looks OK to me.

[RichardG]

on my mobile nothing seems to be operational my side. Contacted their support department. I am not even getting any ping near there. sites taken like over 5minutes to load.... Please do a tracert. u getting around 9ms, I do not even get that

[orin76]

on my mobile nothing seems to be operational my side. Contacted their support department. I am not even getting any ping near there. sites taken like over 5minutes to load.... Please do a tracert. u getting around 9ms, I do not even get that

Here's the output of tracert:



Tracing route to www.neotel.co.za [196.34.133.113]
over a maximum of 30 hops:

1 * * * Request timed out.
2 8 ms 8 ms 7 ms rrba-ip-lir-1-gig-0-0-0.telkom-ipnet.co.za [196.43.8.198]
3 7 ms 8 ms 8 ms 196.43.25.138
4 7 ms 8 ms 8 ms internet-solutions-gw.telkom-ipnet.co.za [196.25.127.182]
5 8 ms 9 ms 8 ms cp3-rba-gi0-2.ip.isnet.net [168.209.86.165]
6 8 ms 18 ms 8 ms core2a-rba-gi0-1.ip.isnet.net [196.26.0.8]
7 9 ms 9 ms 9 ms core2a-bry-gi0-3-216.ip.isnet.net [168.209.100.201]
8 10 ms 9 ms 9 ms 168.209.217.251
9 9 ms 9 ms 9 ms 196.34.191.14
10 9 ms 9 ms 10 ms croixian.cambrient.com [196.34.133.113]

Trace complete.

[RichardG]

that is not new connect Prime that is dsl. Please do not make me excited for nothing. Average ms 200-300.... Waits patiently for my internet connection to be restored

[orin76]

that is not new connect Prime that is dsl. Please do not make me excited for nothing. Average ms 200-300.... Waits patiently for my internet connection to be restored

You are absolutely right. I'm still on my last month of ADSL and I was using route sentry to split local over ADSL and international over Neotel. The ping stats of Neotel are:



Pinging www.neotel.co.za [196.34.133.113] with 32 bytes of data:
Reply from 196.34.133.113: bytes=32 time=813ms TTL=56
Reply from 196.34.133.113: bytes=32 time=1103ms TTL=56
Reply from 196.34.133.113: bytes=32 time=959ms TTL=56
Reply from 196.34.133.113: bytes=32 time=416ms TTL=56

Ping statistics for 196.34.133.113:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 416ms, Maximum = 1103ms, Average = 822ms


and the tracert is:



Tracing route to www.neotel.co.za [196.34.133.113]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 1054 ms 661 ms 952 ms 41.174.0.1
4 1047 ms 666 ms 568 ms 41.160.0.242
5 918 ms 442 ms 249 ms is.jinx.net.za [198.32.142.10]
6 1133 ms 943 ms 226 ms core1a-rba-gi0-1.ip.isnet.net [196.26.0.7]
7 1063 ms 1292 ms 811 ms core1a-bry-gi0-3-215.ip.isnet.net [168.209.0.98]
8 890 ms 1155 ms 1008 ms 168.209.218.251
9 548 ms 490 ms 683 ms 196.34.191.14
10 1077 ms 401 ms 442 ms croixian.cambrient.com [196.34.133.113]

Trace complete.


Looks like there is a problem. Please accept my apologies for previous incorrect data. I feel like a real idiot :o

[RichardG]

Do not feel like an idiot mate
Mistakes do happen.
Just things do happen was checking at your ms, and Neotel doesn't even have that close..
Finally back on the internet for how long. I wonder...

Thank you for your input as well :)
Seems there is a problem, glad I am not the only one having the same issues.

Pinging www.neotel.co.za [196.34.133.113] with 32 bytes o

Reply from 196.34.133.113: bytes=32 time=1737ms TTL=56
Reply from 196.34.133.113: bytes=32 time=1680ms TTL=56
Reply from 196.34.133.113: bytes=32 time=1256ms TTL=56
Reply from 196.34.133.113: bytes=32 time=648ms TTL=56

Ping statistics for 196.34.133.113:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 648ms, Maximum = 1737ms, Average = 1330ms

Still issues :(