cancel
Showing results for 
Search instead for 
Did you mean: 

FOR SUPORT..Again ***** lag on dial up modem and ISDN AGAIN

mike001
Grafter
Posts: 393
Registered: 30-07-2007

FOR SUPORT..Again ***** lag on dial up modem and ISDN AGAIN

Ok at 3am this morning hardly any lag
At 4pm today ...lag VERY VERY BAD
As you can see by the ping times
Witch I pinged constantly 12-13 time
that the pings very a lot.

The trace rout show that the pings very at different
places...I would take it is a hard ware problem your end Sad

This was on the pay as you go ISDN 64k

O and thanks for sortting out my adsl probs with *%*%ing BT
Cant wait till the 20th Smiley

Pinging 194.159.164.183 with 32 bytes of data:

Reply from 194.159.164.183: bytes=32 time=89ms TTL=246
Reply from 194.159.164.183: bytes=32 time=75ms TTL=246
Reply from 194.159.164.183: bytes=32 time=75ms TTL=246
Reply from 194.159.164.183: bytes=32 time=72ms TTL=246

Ping statistics for 194.159.164.183:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 72ms, Maximum = 89ms, Average = 77ms

----------------------------------------------------------------------------------------------

Pinging 194.159.164.183 with 32 bytes of data:

Reply from 194.159.164.183: bytes=32 time=61ms TTL=246
Reply from 194.159.164.183: bytes=32 time=72ms TTL=246
Reply from 194.159.164.183: bytes=32 time=331ms TTL=246
Reply from 194.159.164.183: bytes=32 time=75ms TTL=246

Ping statistics for 194.159.164.183:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 61ms, Maximum = 331ms, Average = 134ms

---------------------------------------------------------------------------------------------------

Pinging 194.159.164.183 with 32 bytes of data:

Reply from 194.159.164.183: bytes=32 time=64ms TTL=246
Reply from 194.159.164.183: bytes=32 time=69ms TTL=246
Reply from 194.159.164.183: bytes=32 time=69ms TTL=246
Reply from 194.159.164.183: bytes=32 time=188ms TTL=246

Ping statistics for 194.159.164.183:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 64ms, Maximum = 188ms, Average = 97ms

----------------------------------------------------------------------------------------------
Pinging 194.159.164.183 with 32 bytes of data:

Reply from 194.159.164.183: bytes=32 time=78ms TTL=246
Reply from 194.159.164.183: bytes=32 time=81ms TTL=246
Reply from 194.159.164.183: bytes=32 time=135ms TTL=246
Reply from 194.159.164.183: bytes=32 time=94ms TTL=246

Ping statistics for 194.159.164.183:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 78ms, Maximum = 135ms, Average = 97ms

--------------------------------------------------------------------------------------------

Pinging 194.159.164.183 with 32 bytes of data:

Reply from 194.159.164.183: bytes=32 time=109ms TTL=246
Reply from 194.159.164.183: bytes=32 time=75ms TTL=246
Reply from 194.159.164.183: bytes=32 time=81ms TTL=246
Reply from 194.159.164.183: bytes=32 time=72ms TTL=246

Ping statistics for 194.159.164.183:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 72ms, Maximum = 109ms, Average = 84ms

---------------------------------------------------------------------------------------------------

Pinging 194.159.164.183 with 32 bytes of data:

Reply from 194.159.164.183: bytes=32 time=122ms TTL=246
Reply from 194.159.164.183: bytes=32 time=181ms TTL=246
Reply from 194.159.164.183: bytes=32 time=85ms TTL=246
Reply from 194.159.164.183: bytes=32 time=63ms TTL=246

Ping statistics for 194.159.164.183:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 63ms, Maximum = 181ms, Average = 112ms

-------------------------------------------------------------------------------------------

Pinging 194.159.164.183 with 32 bytes of data:

Reply from 194.159.164.183: bytes=32 time=315ms TTL=246
Request timed out.
Reply from 194.159.164.183: bytes=32 time=163ms TTL=246
Reply from 194.159.164.183: bytes=32 time=66ms TTL=246

Ping statistics for 194.159.164.183:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss)
Approximate round trip times in milli-seconds:
Minimum = 66ms, Maximum = 315ms, Average = 181ms

------------------------------------------------------------------------------------------
Pinging 194.159.164.183 with 32 bytes of data:

Reply from 194.159.164.183: bytes=32 time=68ms TTL=246
Reply from 194.159.164.183: bytes=32 time=316ms TTL=246
Reply from 194.159.164.183: bytes=32 time=144ms TTL=246
Reply from 194.159.164.183: bytes=32 time=328ms TTL=246

Ping statistics for 194.159.164.183:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 68ms, Maximum = 328ms, Average = 214ms

------------------------------------------------------------------------------------------

Pinging 194.159.164.183 with 32 bytes of data:

Reply from 194.159.164.183: bytes=32 time=71ms TTL=246
Reply from 194.159.164.183: bytes=32 time=75ms TTL=246
Reply from 194.159.164.183: bytes=32 time=75ms TTL=246
Reply from 194.159.164.183: bytes=32 time=72ms TTL=246

Ping statistics for 194.159.164.183:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 71ms, Maximum = 75ms, Average = 73ms

-------------------------------------------------------------------------------------------

Pinging 194.159.164.183 with 32 bytes of data:

Reply from 194.159.164.183: bytes=32 time=61ms TTL=246
Reply from 194.159.164.183: bytes=32 time=207ms TTL=246
Reply from 194.159.164.183: bytes=32 time=63ms TTL=246
Reply from 194.159.164.183: bytes=32 time=275ms TTL=246

Ping statistics for 194.159.164.183:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 61ms, Maximum = 275ms, Average = 151ms

-----------------------------------------------------------------------------------------

Pinging 194.159.164.183 with 32 bytes of data:

Reply from 194.159.164.183: bytes=32 time=206ms TTL=246
Reply from 194.159.164.183: bytes=32 time=182ms TTL=246
Reply from 194.159.164.183: bytes=32 time=153ms TTL=246
Reply from 194.159.164.183: bytes=32 time=66ms TTL=246

Ping statistics for 194.159.164.183:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 66ms, Maximum = 206ms, Average = 151ms

-------------------------------------------------------------------------------------------

Pinging 194.159.164.183 with 32 bytes of data:

Reply from 194.159.164.183: bytes=32 time=338ms TTL=246
Reply from 194.159.164.183: bytes=32 time=69ms TTL=246
Reply from 194.159.164.183: bytes=32 time=75ms TTL=246
Reply from 194.159.164.183: bytes=32 time=119ms TTL=246

Ping statistics for 194.159.164.183:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 69ms, Maximum = 338ms, Average = 150ms

---------------------------------------------------------------------------------------------

Pinging 194.159.164.183 with 32 bytes of data:

Reply from 194.159.164.183: bytes=32 time=524ms TTL=246
Reply from 194.159.164.183: bytes=32 time=297ms TTL=246
Reply from 194.159.164.183: bytes=32 time=247ms TTL=246
Reply from 194.159.164.183: bytes=32 time=85ms TTL=246

Ping statistics for 194.159.164.183:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 85ms, Maximum = 524ms, Average = 288ms

------------------------------------------------------------------------------------------

Pinging 194.159.164.183 with 32 bytes of data:

Reply from 194.159.164.183: bytes=32 time=74ms TTL=246
Reply from 194.159.164.183: bytes=32 time=60ms TTL=246
Reply from 194.159.164.183: bytes=32 time=97ms TTL=246
Reply from 194.159.164.183: bytes=32 time=66ms TTL=246

Ping statistics for 194.159.164.183:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 60ms, Maximum = 97ms, Average = 74ms

---------------------------------------------------------------------------------------
Pinging 194.159.164.183 with 32 bytes of data:

Reply from 194.159.164.183: bytes=32 time=68ms TTL=246
Reply from 194.159.164.183: bytes=32 time=432ms TTL=246
Reply from 194.159.164.183: bytes=32 time=391ms TTL=246
Reply from 194.159.164.183: bytes=32 time=275ms TTL=246

Ping statistics for 194.159.164.183:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 68ms, Maximum = 432ms, Average = 291ms

-------------------------------------------------------------------------------------------
Pinging 194.159.164.183 with 32 bytes of data:

Reply from 194.159.164.183: bytes=32 time=75ms TTL=246
Reply from 194.159.164.183: bytes=32 time=72ms TTL=246
Reply from 194.159.164.183: bytes=32 time=269ms TTL=246
Reply from 194.159.164.183: bytes=32 time=69ms TTL=246

Ping statistics for 194.159.164.183:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 69ms, Maximum = 269ms, Average = 121ms

--------------------------------------------------------------------------------------------------------------
Pinging 194.159.164.183 with 32 bytes of data:

Reply from 194.159.164.183: bytes=32 time=94ms TTL=246
Reply from 194.159.164.183: bytes=32 time=322ms TTL=246
Reply from 194.159.164.183: bytes=32 time=132ms TTL=246
Reply from 194.159.164.183: bytes=32 time=72ms TTL=246

Ping statistics for 194.159.164.183:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 72ms, Maximum = 322ms, Average = 155ms

Tracing route to mike.games.uk.demon.net [194.159.164.183]
over a maximum of 30 hops:

1 58 ms 59 ms 237 ms 192.168.53.106
2 425 ms 105 ms 59 ms vlan501.rhogan1.core.quay.plus.net [212.159.7.12
]
3 209 ms 68 ms 68 ms 249.core01.access.plus.net.uk [212.159.15.249]
4 65 ms 68 ms 68 ms bhuna.core.plus.net [212.159.15.253]
5 78 ms 68 ms 68 ms atm.core.telehouse.plus.net [212.159.1.66]
6 71 ms 87 ms 68 ms lon1-10.nildram.net [213.208.106.25]
7 72 ms 77 ms 87 ms lon1-9.nildram.net [195.149.20.130]
8 81 ms 87 ms 77 ms linx-1.router.demon.net [195.66.224.12]
9 90 ms 96 ms 265 ms anchor-service-5-fxp0.router.demon.net [158.152.
0.55]
10 78 ms 87 ms 87 ms mike.games.uk.demon.net [194.159.164.183]

Trace complete.

-----------------------------------------------------------------------------------------------------------------
Tracing route to mike.games.uk.demon.net [194.159.164.183]
over a maximum of 30 hops:

1 53 ms 59 ms 59 ms 192.168.53.106
2 272 ms 124 ms 96 ms vlan501.rhogan1.core.quay.plus.net [212.159.7.12
]
3 81 ms 68 ms 59 ms 249.core01.access.plus.net.uk [212.159.15.249]
4 59 ms 246 ms 134 ms bhuna.core.plus.net [212.159.15.253]
5 69 ms 143 ms 77 ms atm.core.telehouse.plus.net [212.159.1.66]
6 59 ms 68 ms 77 ms lon1-10.nildram.net [213.208.106.25]
7 72 ms 77 ms 77 ms lon1-9.nildram.net [195.149.20.130]
8 69 ms 77 ms 77 ms linx-1.router.demon.net [195.66.224.12]
9 72 ms 77 ms 87 ms anchor-service-5-fxp0.router.demon.net [158.152.
0.55]
10 78 ms 96 ms 87 ms mike.games.uk.demon.net [194.159.164.183]

Trace complete.

-----------------------------------------------------------------------------------------------------------------

Tracing route to mike.games.uk.demon.net [194.159.164.183]
over a maximum of 30 hops:

1 56 ms 68 ms 59 ms 192.168.53.106
2 62 ms 68 ms 59 ms vlan501.rhogan1.core.quay.plus.net [212.159.7.12
]
3 65 ms 68 ms 59 ms 249.core01.access.plus.net.uk [212.159.15.249]
4 59 ms 68 ms 68 ms bhuna.core.plus.net [212.159.15.253]
5 91 ms 124 ms 268 ms atm.core.telehouse.plus.net [212.159.1.66]
6 75 ms 77 ms 77 ms lon1-10.nildram.net [213.208.106.25]
7 297 ms 77 ms 77 ms lon1-9.nildram.net [195.149.20.130]
8 78 ms 77 ms 87 ms linx-1.router.demon.net [195.66.224.12]
9 525 ms 143 ms 96 ms anchor-service-5-fxp0.router.demon.net [158.152.
0.55]
10 166 ms 96 ms 115 ms mike.games.uk.demon.net [194.159.164.183]

Trace complete.

-----------------------------------------------------------------------------------------------------------------

Tracing route to mike.games.uk.demon.net [194.159.164.183]
over a maximum of 30 hops:

1 399 ms 105 ms 68 ms 192.168.53.106
2 59 ms 68 ms 62 ms vlan501.rhogan1.core.quay.plus.net [212.159.7.12
]
3 66 ms 59 ms 59 ms 249.core01.access.plus.net.uk [212.159.15.249]
4 422 ms 68 ms 68 ms bhuna.core.plus.net [212.159.15.253]
5 72 ms 77 ms 77 ms atm.core.telehouse.plus.net [212.159.1.66]
6 397 ms 340 ms 77 ms lon1-10.nildram.net [213.208.106.25]
7 72 ms 77 ms 77 ms lon1-9.nildram.net [195.149.20.130]
8 69 ms 77 ms 77 ms linx-1.router.demon.net [195.66.224.12]
9 272 ms 96 ms 87 ms anchor-service-5-fxp0.router.demon.net [158.152.
0.55]
10 94 ms * 166 ms mike.games.uk.demon.net [194.159.164.183]

Trace complete.

-----------------------------------------------------------------------------------------------------------------

Tracing route to mike.games.uk.demon.net [194.159.164.183]
over a maximum of 30 hops:

1 52 ms 59 ms 265 ms 192.168.53.106
2 59 ms 59 ms 68 ms vlan501.rhogan1.core.quay.plus.net [212.159.7.12
]
3 62 ms 59 ms 68 ms 249.core01.access.plus.net.uk [212.159.15.249]
4 66 ms 68 ms 68 ms bhuna.core.plus.net [212.159.15.253]
5 97 ms 87 ms 77 ms atm.core.telehouse.plus.net [212.159.1.66]
6 250 ms 68 ms 68 ms lon1-10.nildram.net [213.208.106.25]
7 62 ms 77 ms 77 ms lon1-9.nildram.net [195.149.20.130]
8 69 ms 77 ms 77 ms linx-1.router.demon.net [195.66.224.12]
9 75 ms 302 ms 77 ms anchor-service-5-fxp0.router.demon.net [158.152.
0.55]
10 72 ms 87 ms 87 ms mike.games.uk.demon.net [194.159.164.183]

Trace complete.

-----------------------------------------------------------------------------------------------------------------

Tracing route to mike.games.uk.demon.net [194.159.164.183]
over a maximum of 30 hops:

1 51 ms 59 ms 59 ms 192.168.53.106
2 66 ms 59 ms 59 ms vlan501.rhogan1.core.quay.plus.net [212.159.7.12
]
3 66 ms 68 ms 68 ms 249.core01.access.plus.net.uk [212.159.15.249]
4 59 ms 68 ms 68 ms bhuna.core.plus.net [212.159.15.253]
5 97 ms 68 ms 68 ms atm.core.telehouse.plus.net [212.159.1.66]
6 678 ms 143 ms 87 ms lon1-10.nildram.net [213.208.106.25]
7 69 ms 77 ms 77 ms lon1-9.nildram.net [195.149.20.130]
8 163 ms 77 ms 77 ms linx-1.router.demon.net [195.66.224.12]
9 69 ms 87 ms 77 ms anchor-service-5-fxp0.router.demon.net [158.152.
0.55]
10 181 ms 87 ms 96 ms mike.games.uk.demon.net [194.159.164.183]

Trace complete.

-----------------------------------------------------------------------------------------------------------------

Tracing route to mike.games.uk.demon.net [194.159.164.183]
over a maximum of 30 hops:

1 56 ms 59 ms 59 ms 192.168.53.106
2 59 ms 59 ms 59 ms vlan501.rhogan1.core.quay.plus.net [212.159.7.12
]
3 134 ms 68 ms 59 ms 249.core01.access.plus.net.uk [212.159.15.249]
4 291 ms 77 ms 68 ms bhuna.core.plus.net [212.159.15.253]
5 350 ms 77 ms 68 ms atm.core.telehouse.plus.net [212.159.1.66]
6 66 ms 77 ms 68 ms lon1-10.nildram.net [213.208.106.25]
7 72 ms 77 ms 77 ms lon1-9.nildram.net [195.149.20.130]
8 69 ms 77 ms 68 ms linx-1.router.demon.net [195.66.224.12]
9 72 ms 77 ms 77 ms anchor-service-5-fxp0.router.demon.net [158.152.
0.55]
10 69 ms 87 ms 77 ms mike.games.uk.demon.net [194.159.164.183]

Trace complete.


2 REPLIES
mike001
Grafter
Posts: 393
Registered: 30-07-2007

RE: FOR SUPORT..Again ***** lag on dial up modem and ISDN A

Just logged on With Force 9 pay as you go 64k ISDN
and getting same lag...not quiet as much but still there
Is the force 9 still the same company as plus net?

With freeserve ....no lag at all
N/A

RE: FOR SUPORT..Again ***** lag on dial up modem and ISDN A

Hi there,

Is this happening with just that server or any address? We're not aware of any service problems that would cause this, however if you raise a ticket on your account we'll be happy to investigate further.

Regards,
Rob

| Robert Kelly...............Unmetered & ADSL solutions
| Technical Support......................for Home & Business
| PlusNet Technologies Ltd............@ http://www.plus.net
+ ----- My Referrals - It pays to recommend PlusNet ----- +