[Merged] Manchester Issues - Page 5

13-12-2005, 00:33

Quote:

Originally Posted by Florence

Pinging kittysworld.co.uk [195.62.28.9] with 32 bytes of data:

Reply from 195.62.28.9: bytes=32 time=16ms TTL=52
Reply from 195.62.28.9: bytes=32 time=17ms TTL=52
Reply from 195.62.28.9: bytes=32 time=21ms TTL=52
Reply from 195.62.28.9: bytes=32 time=17ms TTL=52

Ping statistics for 195.62.28.9:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 21ms, Average = 17ms

Tracing route to kittysworld.co.uk [195.62.28.9]
over a maximum of 30 hops:

1 13 ms 9 ms 14 ms 10.9.0.1
2 115 ms 18 ms 21 ms oldh-t2cam1-b-ge-wan51-129.inet.ntl.com [80.5.16
5.109]
3 12 ms 11 ms 14 ms manc-t3core-1b-ge-011-0.inet.ntl.com [213.104.24
2.169]
4 11 ms 11 ms 12 ms man-bb-b-so-400-0.inet.ntl.com [213.105.242.245]

5 21 ms 17 ms 17 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]

6 18 ms 18 ms 19 ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130]

7 20 ms 22 ms 19 ms redb-ic-1-as0-0.inet.ntl.com [213.105.174.138]
8 20 ms 19 ms 22 ms xchangepoint-gw1.aexiomus.net [217.79.160.25]
9 22 ms 28 ms 19 ms peer8.rbl-mer.aexiomus.net [80.82.128.46]
10 31 ms 31 ms 29 ms 84-45-244-6.no-dns-yet.enta.net [84.45.244.6]
11 30 ms 18 ms 21 ms mars.miniserve.net [195.62.28.9]

Trace complete.

This one from South Manchester for comparison

Tracing route to kittysworld.co.uk [195.62.28.9]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ipcop.localdomain [10.0.0.1]
2 7 ms 8 ms 7 ms 10.15.16.1
3 10 ms 8 ms 9 ms bagu-t2cam1-b-ge-wan52-121.inet.nt
2.213]
4 8 ms 18 ms 8 ms bagu-t2core-b-ge-wan64.inet.ntl.co
1]
5 9 ms 9 ms 10 ms lee-bb-b-so-200-0.inet.ntl.com [21

6 10 ms 9 ms 10 ms lee-bb-a-ae0-0.inet.ntl.com [62.25
7 14 ms 14 ms 14 ms nth-bb-b-so-000-0.inet.ntl.com [62

8 14 ms 25 ms 13 ms nth-bb-a-ae0-0.inet.ntl.com [62.25
9 17 ms 15 ms 16 ms gfd-bb-b-so-400-0.inet.ntl.com [62
10 34 ms 20 ms 18 ms redb-ic-1-as0-0.inet.ntl.com [213.
11 18 ms 18 ms 18 ms xchangepoint-gw1.aexiomus.net [217
12 18 ms 18 ms 19 ms peer8.rbl-mer.aexiomus.net [80.82.
13 18 ms 17 ms 18 ms 84-45-244-6.no-dns-yet.enta.net [8
14 34 ms 16 ms 18 ms mars.miniserve.net [195.62.28.9]

Connection 10 meg

Florence · 13-12-2005, 00:54

Thank you Bill I know the proxy you go through is wqorking well but my problem seems to be I need to specify a proxy sometimes to surf then returning to some forums I have to unspecify to get back in.

I did notice the very high over 100 on the tracert I completed and a rerun also brought over 100 in the same space.

I still cannot log into my webspace and have sent screenshots to the hostoing company to make sure I have cleared that part before I call tech support @ NTL

Ignition · 13-12-2005, 04:13

As stated elsewhere a fair amount of times, proxies don't have any influence over pings.

Occasional spikes on traces especially on the same nodes if they are busy doing other things is par for the course as previously stated many times elsewhere.

Florence · 13-12-2005, 18:08

Well tonight I can access the website plesk panel the modems config and ftp my website without altering anything on my pc. Also webpages are back loading quicker also nothing has been rebooted.

marky · 13-12-2005, 19:39

I lost my broadband alltogether about midnight last night, today it seems full steam ahead. may just have been a Manchester problem.
I take it day by day now

DavidC · 14-12-2005, 05:27

I lost my broadband last night too about midnight (i live nr bolton) then it came back about 2 AM

i had loads of probs last month..i lost my connection for about 4 days..that really sucked, like you i take it day by day now

Still waiting for 10 MB too..still got 3 MB speeds

th'engineer · 14-12-2005, 07:24

Target Name: mars.miniserve.net
IP: 195.62.28.9
Date/Time: 14/12/2005 06:23:38
1 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms [192.168.123.254]
2 6 ms 6 ms 6 ms 5 ms 8 ms 6 ms 5 ms 6 ms 5 ms 6 ms [10.23.48.1]
3 16 ms 6 ms 5 ms 6 ms 6 ms 29 ms 6 ms 6 ms 10 ms 6 ms oldh-t2cam1-a-v115.inet.ntl.com [80.5.164.61]
4 7 ms 7 ms 7 ms 6 ms 7 ms 8 ms 7 ms 7 ms 8 ms 7 ms manc-t3core-1a-ge-111-0.inet.ntl.com [213.104.242.77]
5 37 ms 7 ms 8 ms 7 ms 8 ms 8 ms 9 ms 31 ms 7 ms 7 ms man-bb-a-so-400-0.inet.ntl.com [213.105.172.241]
6 7 ms 10 ms 7 ms 8 ms 7 ms 7 ms 8 ms 7 ms 13 ms 9 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
7 14 ms 18 ms 13 ms 13 ms 18 ms 14 ms 13 ms 17 ms 14 ms 36 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]
8 14 ms 15 ms 14 ms 13 ms 14 ms 14 ms 14 ms 13 ms 13 ms 14 ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130]
9 18 ms 17 ms 16 ms 15 ms 14 ms 16 ms 15 ms 16 ms 15 ms 15 ms redb-ic-1-as0-0.inet.ntl.com [213.105.174.138]
10 16 ms 16 ms 15 ms 15 ms 16 ms 15 ms 15 ms 17 ms 14 ms 15 ms xchangepoint-gw1.aexiomus.net [217.79.160.25]
11 15 ms 14 ms 16 ms 15 ms 16 ms 16 ms 15 ms 16 ms 16 ms 17 ms peer8.rbl-mer.aexiomus.net [80.82.128.46]
12 14 ms 15 ms 14 ms 14 ms 15 ms 14 ms 15 ms 14 ms 14 ms 15 ms 84-45-244-6.no-dns-yet.enta.net [84.45.244.6]
13 17 ms 14 ms 20 ms 15 ms 14 ms 15 ms 14 ms 16 ms 15 ms 15 ms mars.miniserve.net [195.62.28.9]

Just did this trace to kittys server if its of use to Bill or Ignition for comparing

Rone · 14-12-2005, 17:53

Mine appears to have settled down, only one disconnection last friday.
Since then its been fine, touch wood.

Damn its running slow now tho, less than my old 3meg.

Wed, 14 Dec 2005 17:30:30 UTC
1st 128K took 407 ms = 322044 Bytes/sec = approx 2679 kbits/sec
2nd 128K took 437 ms = 299936 Bytes/sec = approx 2495 kbits/sec
3rd 128K took 344 ms = 381023 Bytes/sec = approx 3170 kbits/sec
4th 128K took 9281 ms = 14123 Bytes/sec = approx 118 kbits/sec

altis · 15-12-2005, 16:15

Although things are a bit better now, I'm still seing some very slow sites. In particular, eBay is very unresponsive and I often have to repeat clicks - which makes sniping a bit risky! I'm not certain, but I'm gaining the impression that the problem sites are accessed through the Manchester internet exchange (Minx?) as opposed to the London one.

Code:

Tracing route to wildsnow.com [70.98.111.42]
over a maximum of 30 hops:
  1     7 ms     8 ms     7 ms  10.15.80.1 
  2    10 ms    10 ms    11 ms  bagu-t2cam1-b-ge-wan52-122.inet.ntl.com [80.5.162.217] 
  3    10 ms     8 ms    11 ms  bagu-t2core-b-ge-wan63.inet.ntl.com [80.5.161.137] 
  4    10 ms    18 ms     9 ms  lee-bb-b-so-300-0.inet.ntl.com [62.253.188.29] 
  5    27 ms    14 ms    10 ms  man-bb-a-so-700-0.inet.ntl.com [62.253.185.193] 
  6    19 ms    19 ms    18 ms  212.187.137.1 
  7    18 ms    18 ms    40 ms  so-6-0-0.mp2.manchesteruk1.level3.net [4.68.113.114] 
  8    18 ms    18 ms    27 ms  so-1-1-0.bbr1.london1.level3.net [4.68.128.73] 
  9    18 ms    28 ms    18 ms  ge-1-1.core2.london1.level3.net [212.187.131.134] 
 10    19 ms    18 ms    19 ms  bcr1-so-4-0-0.londonlnx.savvis.net [206.24.169.29] 
 11    20 ms    17 ms    19 ms  bcs1-so-1-1-0.londonlnx.savvis.net [204.70.193.114] 
 12    91 ms    91 ms    92 ms  bcs2-so-0-0-0.newyork.savvis.net [204.70.192.121] 
 13   102 ms   102 ms   102 ms  bcs2-so-4-0-0.washington.savvis.net [204.70.192.1] 
 14   102 ms   103 ms   101 ms  cpr2-pos-0-0.virginiaequinix.savvis.net [206.24.238.218] 
 15   102 ms   102 ms   102 ms  208.173.50.242 
 16   103 ms   103 ms   103 ms  so-2-0-0--0.cr01.mcln.eli.net [207.173.114.129] 
 17   119 ms   116 ms   115 ms  so-0-0-0--0.cr02.chcg.eli.net [207.173.114.250] 
 18   182 ms   168 ms   169 ms  so-1-0-0--0.cr01.slkc.eli.net [207.173.115.237] 
 19   167 ms   320 ms   167 ms  ge-0-0-0--0.gw02.slkc.eli.net [207.173.115.246] 
 20   170 ms   169 ms   171 ms  70.97.59.22 
 21   172 ms   171 ms   183 ms  wildsnow.com [70.98.111.42] 
Trace complete.

Tracing route to ebay.co.uk [66.135.192.41]
over a maximum of 30 hops:
  1     8 ms     7 ms     8 ms  10.15.80.1 
  2     8 ms     8 ms    11 ms  bagu-t2cam1-a-v122.inet.ntl.com [80.5.162.89] 
  3    10 ms    17 ms     9 ms  bagu-t2core-a-ge-wan61.inet.ntl.com [80.5.161.5] 
  4    44 ms    26 ms    10 ms  man-bb-a-so-100-0.inet.ntl.com [62.253.188.25] 
  5    17 ms    17 ms    17 ms  212.187.137.1 
  6    17 ms    16 ms    21 ms  so-6-1-0.mp2.manchesteruk1.level3.net [4.68.113.118] 
  7   167 ms   167 ms   168 ms  ae-0-0.bbr2.sanjose1.level3.net [64.159.1.130] 
  8   167 ms   175 ms   168 ms  ge-11-2.ipcolo2.sanjose1.level3.net [4.68.123.170] 
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 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.

Baguley to Manchester via Leeds eh!!

Florence · 16-12-2005, 07:36

ping to kittysworld
Pinging kittysworld.co.uk [195.62.28.9] with 32 bytes of data:

Reply from 195.62.28.9: bytes=32 time=2143ms TTL=53
Request timed out.
Reply from 195.62.28.9: bytes=32 time=1776ms TTL=53
Reply from 195.62.28.9: bytes=32 time=1785ms TTL=53

Ping statistics for 195.62.28.9:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 1776ms, Maximum = 2143ms, Average = 1901ms
Tracer to kittysworld.
Tracing route to kittysworld.co.uk [195.62.28.9]
over a maximum of 30 hops:

1 1588 ms 1534 ms 1683 ms 10.9.0.1
2 1977 ms * 1574 ms oldh-t2cam1-b-ge-wan51-129.inet.ntl.com [80.5.16
5.109]
3 1498 ms * 2337 ms manc-t3core-1b-ge-011-0.inet.ntl.com [213.104.24
2.169]
4 2288 ms 2394 ms 2079 ms man-bb-b-so-400-0.inet.ntl.com [213.105.242.245]

5 1981 ms 2607 ms 2247 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]

6 2417 ms 1609 ms 1687 ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130]

7 1570 ms 2159 ms 1905 ms redb-ic-1-as0-0.inet.ntl.com [213.105.174.138]
8 1578 ms 1396 ms 1831 ms xchangepoint-gw1.aexiomus.net [217.79.160.25]
9 2140 ms 2102 ms 1596 ms peer8.rbl-mer.aexiomus.net [80.82.128.46]
10 1455 ms * 1626 ms aexiomus-gw.rbl-mer.misp.co.uk [80.82.143.210]
11 1581 ms 1291 ms 1817 ms mars.miniserve.net [195.62.28.9]

ping to router
Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time<1ms TTL=150
Reply from 192.168.1.1: bytes=32 time<1ms TTL=150
Reply from 192.168.1.1: bytes=32 time<1ms TTL=150
Reply from 192.168.1.1: bytes=32 time<1ms TTL=150

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

Rebooted modem
ping kittysworld
Pinging kittysworld.co.uk [195.62.28.9] with 32 bytes of data:

Reply from 195.62.28.9: bytes=32 time=991ms TTL=53
Reply from 195.62.28.9: bytes=32 time=784ms TTL=53
Reply from 195.62.28.9: bytes=32 time=1015ms TTL=53
Reply from 195.62.28.9: bytes=32 time=791ms TTL=53

Ping statistics for 195.62.28.9:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 784ms, Maximum = 1015ms, Average = 895ms
tracer kittysworld

Tracing route to kittysworld.co.uk [195.62.28.9]
over a maximum of 30 hops:

1 1563 ms 1949 ms 1452 ms 10.9.0.1
2 1403 ms 1674 ms 1583 ms oldh-t2cam1-b-ge-wan51-129.inet.ntl.com [80.5.16
5.109]
3 1274 ms 1452 ms 1375 ms manc-t3core-1b-ge-011-0.inet.ntl.com [213.104.24
2.169]
4 1262 ms 1358 ms 2497 ms man-bb-b-so-400-0.inet.ntl.com [213.105.242.245]

5 2561 ms 2448 ms 1383 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]

6 1757 ms 1318 ms 1476 ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130]

7 2113 ms 2205 ms 1328 ms redb-ic-1-as0-0.inet.ntl.com [213.105.174.138]
8 600 ms 913 ms 1537 ms xchangepoint-gw1.aexiomus.net [217.79.160.25]
9 1346 ms 1718 ms 2166 ms peer8.rbl-mer.aexiomus.net [80.82.128.46]
10 2451 ms 2156 ms 1496 ms aexiomus-gw.rbl-mer.misp.co.uk [80.82.143.210]
11 2053 ms 2256 ms 1504 ms mars.miniserve.net [195.62.28.9]

Trace complete.

ping router
Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time<1ms TTL=150
Reply from 192.168.1.1: bytes=32 time<1ms TTL=150
Reply from 192.168.1.1: bytes=32 time=1ms TTL=150
Reply from 192.168.1.1: bytes=32 time<1ms TTL=150

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
__________________________________________________ __________

So what is causing the high pings?

Florence · 16-12-2005, 11:51

the latest one nothing altered since the last one exceept the modem lights are not constantly flashing faster than christmas lights.

Tracing route to kittysworld.co.uk [195.62.28.9]
over a maximum of 30 hops:

1 12 ms 13 ms 9 ms 10.9.0.1
2 10 ms 57 ms 97 ms oldh-t2cam1-b-ge-wan51-129.inet.ntl.com [80.5.16
5.109]
3 12 ms 20 ms 12 ms manc-t3core-1b-ge-011-0.inet.ntl.com [213.104.24
2.169]
4 14 ms 11 ms 10 ms man-bb-b-so-400-0.inet.ntl.com [213.105.242.245]

5 39 ms 24 ms 26 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]

6 31 ms 17 ms 17 ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130]

7 19 ms 23 ms 19 ms redb-ic-1-as0-0.inet.ntl.com [213.105.174.138]
8 19 ms 28 ms 18 ms xchangepoint-gw1.aexiomus.net [217.79.160.25]
9 20 ms 19 ms 20 ms peer8.rbl-mer.aexiomus.net [80.82.128.46]
10 20 ms 19 ms 18 ms 84-45-244-6.no-dns-yet.enta.net [84.45.244.6]
11 18 ms 17 ms 18 ms mars.miniserve.net [195.62.28.9]

Trace complete.

C:\Documents and Settings\Florence>ping www.kittysworld.co.uk

Pinging kittysworld.co.uk [195.62.28.9] with 32 bytes of data:

Reply from 195.62.28.9: bytes=32 time=17ms TTL=52
Reply from 195.62.28.9: bytes=32 time=21ms TTL=52
Reply from 195.62.28.9: bytes=32 time=18ms TTL=52
Reply from 195.62.28.9: bytes=32 time=16ms TTL=52

Ping statistics for 195.62.28.9:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 21ms, Average = 18ms

Rone · 17-12-2005, 09:55

And again:
Sat, 17 Dec 2005 08:53:04 UTC
1st 128K took 984 ms = 133203 Bytes/sec = approx 1108 kbits/sec
2nd 128K took 609 ms = 215225 Bytes/sec = approx 1791 kbits/sec
3rd 128K took 594 ms = 220660 Bytes/sec = approx 1836 kbits/sec
4th 128K took 1266 ms = 103532 Bytes/sec = approx 861 kbits/sec

Oi mr NTL, can i at least have the 3meg i pay for?
I know its "up to 10 meg" it didnt say anywhere "often less than you had".

th'engineer · 18-12-2005, 11:21

Working very well here

no problems here must be south manchester

Sun, 18 Dec 2005 10:20:55 UTC
1st 128K took 531 ms = 246840 Bytes/sec = approx 2054 kbits/sec
2nd 128K took 531 ms = 246840 Bytes/sec = approx 2054 kbits/sec
3rd 128K took 532 ms = 246376 Bytes/sec = approx 2050 kbits/sec
4th 128K took 547 ms = 239620 Bytes/sec = approx 1994 kbits/sec

Florence · 18-12-2005, 11:44

Th'eng I go through Oldham and on tracers my second hop is the same as yours

Quote:

2 10 ms 57 ms 97 ms oldh-t2cam1-b-ge-wan51-129.inet.ntl.com [80.5.16
5.109]

that was the last one and working well.

When I get the warning my pings have exceeded 4 secs I get this

Quote:

1 1588 ms 1534 ms 1683 ms 10.9.0.1
2 1977 ms * 1574 ms oldh-t2cam1-b-ge-wan51-129.inet.ntl.com [80.5.16
5.109]
3 1498 ms * 2337 ms manc-t3core-1b-ge-011-0.inet.ntl.com [213.104.24
2.169]
4 2288 ms 2394 ms 2079 ms man-bb-b-so-400-0.inet.ntl.com [213.105.242.245]

at present I am not getting the warning so I know the network is working as its ment to.

th'engineer · 18-12-2005, 21:03

It is all over the place wonder if Ignition or BB could shed light on it

Target Name: kittysworld.co.uk
IP: 195.62.28.9
Date/Time: 18/12/2005 20:01:58
1 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms [192.168.123.254]
2 13 ms 6 ms 6 ms 6 ms 6 ms 8 ms 13 ms 8 ms 8 ms 6 ms [10.23.48.1]
3 7 ms 8 ms 7 ms 6 ms 9 ms 97 ms 7 ms 10 ms 6 ms 7 ms oldh-t2cam1-a-v115.inet.ntl.com [80.5.164.61]
4 10 ms 14 ms 7 ms 7 ms 7 ms 8 ms 8 ms 6 ms 7 ms 7 ms manc-t3core-1a-ge-111-0.inet.ntl.com [213.104.242.77]
5 10 ms 6 ms 10 ms 7 ms 8 ms 7 ms 8 ms 8 ms 7 ms 8 ms man-bb-a-so-400-0.inet.ntl.com [213.105.172.241]
6 22 ms 7 ms 9 ms 45 ms 9 ms 8 ms 7 ms 9 ms 8 ms 8 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
7 13 ms 21 ms 42 ms 13 ms 20 ms 14 ms 14 ms 28 ms 14 ms 14 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]
8 21 ms 15 ms 15 ms 14 ms 14 ms 14 ms 14 ms 16 ms 14 ms 14 ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130]
9 15 ms 19 ms 15 ms 15 ms 22 ms 15 ms 16 ms 15 ms 14 ms 16 ms redb-ic-1-as0-0.inet.ntl.com [213.105.174.138]
10 24 ms 16 ms 16 ms 15 ms 15 ms 16 ms 15 ms 16 ms 27 ms 16 ms xchangepoint-gw1.aexiomus.net [217.79.160.25]
11 16 ms 16 ms 16 ms 24 ms 16 ms 15 ms 16 ms 16 ms 20 ms 17 ms peer8.rbl-mer.aexiomus.net [80.82.128.46]
12 16 ms 18 ms 17 ms 16 ms 14 ms 15 ms 15 ms 14 ms 16 ms 24 ms 84-45-244-6.no-dns-yet.enta.net [84.45.244.6]
13 17 ms 17 ms 16 ms 15 ms 15 ms 15 ms 19 ms 23 ms 22 ms 15 ms mars.miniserve.net [195.62.28.9]