Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Latency problem
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Plusnet Community
- :
- Forum
- :
- Help with my Plusnet services
- :
- Broadband
- :
- Latency problem
Latency problem
09-03-2014 11:35 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Kyle>ping google.co.uk
Pinging google.co.uk [173.194.41.151] with 32 bytes of data:
Reply from 173.194.41.151: bytes=32 time=572ms TTL=57
Reply from 173.194.41.151: bytes=32 time=536ms TTL=57
Reply from 173.194.41.151: bytes=32 time=500ms TTL=57
Request timed out.
Ping statistics for 173.194.41.151:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 500ms, Maximum = 572ms, Average = 536ms
C:\Users\Kyle>ping google.co.uk
Pinging google.co.uk [173.194.41.151] with 32 bytes of data:
Reply from 173.194.41.151: bytes=32 time=102ms TTL=57
Reply from 173.194.41.151: bytes=32 time=154ms TTL=57
Reply from 173.194.41.151: bytes=32 time=148ms TTL=57
Reply from 173.194.41.151: bytes=32 time=163ms TTL=57
Ping statistics for 173.194.41.151:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 102ms, Maximum = 163ms, Average = 141ms
C:\Users\Kyle>ping google.co.uk
Pinging google.co.uk [173.194.34.191] with 32 bytes of data:
Reply from 173.194.34.191: bytes=32 time=368ms TTL=57
Reply from 173.194.34.191: bytes=32 time=341ms TTL=57
Reply from 173.194.34.191: bytes=32 time=294ms TTL=57
Request timed out.
Ping statistics for 173.194.34.191:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 294ms, Maximum = 368ms, Average = 334ms
C:\Users\Kyle>ping 192.168.0.1
Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Users\Kyle>
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Kyle>ping google.co.uk
Pinging google.co.uk [173.194.41.151] with 32 bytes of data:
Reply from 173.194.41.151: bytes=32 time=572ms TTL=57
Reply from 173.194.41.151: bytes=32 time=536ms TTL=57
Reply from 173.194.41.151: bytes=32 time=500ms TTL=57
Request timed out.
Ping statistics for 173.194.41.151:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 500ms, Maximum = 572ms, Average = 536ms
C:\Users\Kyle>ping google.co.uk
Pinging google.co.uk [173.194.41.151] with 32 bytes of data:
Reply from 173.194.41.151: bytes=32 time=102ms TTL=57
Reply from 173.194.41.151: bytes=32 time=154ms TTL=57
Reply from 173.194.41.151: bytes=32 time=148ms TTL=57
Reply from 173.194.41.151: bytes=32 time=163ms TTL=57
Ping statistics for 173.194.41.151:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 102ms, Maximum = 163ms, Average = 141ms
C:\Users\Kyle>ping google.co.uk
Pinging google.co.uk [173.194.34.191] with 32 bytes of data:
Reply from 173.194.34.191: bytes=32 time=368ms TTL=57
Reply from 173.194.34.191: bytes=32 time=341ms TTL=57
Reply from 173.194.34.191: bytes=32 time=294ms TTL=57
Request timed out.
Ping statistics for 173.194.34.191:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 294ms, Maximum = 368ms, Average = 334ms
C:\Users\Kyle>ping 192.168.0.1
Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Users\Kyle>
Message 1 of 4
(1,918 Views)
3 REPLIES 3
Re: Latency problem
09-03-2014 11:46 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Is there any problem at PN's end
Message 2 of 4
(393 Views)
Re: Latency problem
10-03-2014 1:29 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Not from here -
Which gateway are you connected to? - http://usertools.plus.net/@gateway/
Which gateway
You are currently connected to gateway pcl-ag02.
This is located in City Lifeline House.
C:\Users\Brian>ping google.co.uk
Pinging google.co.uk [173.194.41.151] with 32 bytes of data:
Reply from 173.194.41.151: bytes=32 time=42ms TTL=56
Reply from 173.194.41.151: bytes=32 time=42ms TTL=56
Reply from 173.194.41.151: bytes=32 time=41ms TTL=56
Reply from 173.194.41.151: bytes=32 time=41ms TTL=56
Ping statistics for 173.194.41.151:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 42ms, Average = 41ms
Which gateway are you connected to? - http://usertools.plus.net/@gateway/
Which gateway
You are currently connected to gateway pcl-ag02.
This is located in City Lifeline House.
Message 3 of 4
(393 Views)
Re: Latency problem
10-03-2014 9:20 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Hi BigTabs,
I've taken a look at your line and it's not looking all that healthy. Your line has been automatically banded due to the amount of drops registered on your line.
I can see you've got a Fault ticket open on your account, so our Faults Team will be back in touch as soon as they can to provide you with further information.
I've taken a look at your line and it's not looking all that healthy. Your line has been automatically banded due to the amount of drops registered on your line.
I can see you've got a Fault ticket open on your account, so our Faults Team will be back in touch as soon as they can to provide you with further information.
Message 4 of 4
(393 Views)
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page