Author Topic: A response from my ISP technical support... (Read 902 times)

Skuzzy · « **Reply #15 on:** July 11, 2007, 06:21:20 AM »

Thank you for the update Cavalear. Hope the shoulder is doing well.

kilz, I do not know what options are available to you. If you ISP is stonewalling fixing those problems at Level3, then if it were me, I would be looking for a new ISP.

Dowding · « **Reply #16 on:** July 11, 2007, 11:44:00 AM »

Thanks for that Cavalier. Recover soon mate.

Would be great to see a pingplot from Zen - will be definitely moving to them at the end of the month.

NDO (my ISP) were bought by Namesco, and I think they have gone down hill. It seems to be the pattern - smaller ISPs that are successful with a smaller customer base are swallowed by the big boys and service suffers. Consolidation seems destined to offer only mediocrity.

Only thing is that I've seen rumours about Zen being bought out themselves (still privately owned by one individual).

Let's hope that doesn't come true.

214thCavalier · « **Reply #17 on:** July 15, 2007, 04:04:09 AM »

Here you go, sorry not pingplot format that would require me to set up my homespace, one day i might get off my bellybutton and do it

They seem to be using sprintlink which is the only bug on the horizon.
I am sure routing was totally different before, will power down router and see if it alters later.
Also this was taken at approx 10:00 am on a sunday.

Target Name: viborgDHCP-39.216-16-60.iw.net
IP: 216.16.60.39
Date/Time: 15/07/2007 09:59:05 to 15/07/2007 09:59:20

1 3 ms 3 ms 3 ms 3 ms 3 ms 3 ms 3 ms [192.168.0.1]
2 13 ms 13 ms 14 ms 14 ms 13 ms 14 ms 13 ms gandhi-dsl1.wh.zen.net.uk [62.3.83.5]
3 13 ms 13 ms 16 ms 14 ms 13 ms 14 ms 15 ms erazmus-ge-0-0-1-3.wh.zen.net.uk [62.3.80.197]
4 20 ms 23 ms 21 ms 20 ms 20 ms 23 ms 21 ms lorenz-so-0-1-0-0.te.zen.net.uk [62.3.80.45]
5 23 ms 20 ms 23 ms 20 ms 23 ms 20 ms 27 ms lorenz-ge-0-0-0-0.te.zen.net.uk [62.3.80.41]
6 23 ms 23 ms 23 ms 22 ms 23 ms 23 ms 23 ms sl-gw22-lon-2-1.sprintlink.net [213.206.158.57]
7 24 ms 21 ms 21 ms 21 ms 20 ms 21 ms 23 ms sl-bb22-lon-9-0.sprintlink.net [213.206.128.104]
8 89 ms 91 ms 88 ms 89 ms 88 ms 88 ms 88 ms sl-bb20-nyc-2-0.sprintlink.net [144.232.9.163]
9 88 ms 90 ms 91 ms 89 ms 87 ms 87 ms 90 ms sl-bb26-nyc-6-0.sprintlink.net [144.232.13.9]
10 88 ms 90 ms 88 ms 105 ms 116 ms 158 ms 90 ms sl-bb25-nyc-8-0.sprintlink.net [144.232.13.189]
11 114 ms 114 ms 110 ms 113 ms 113 ms 114 ms 110 ms sl-bb24-chi-13-0.sprintlink.net [144.232.20.118]
12 109 ms 110 ms 111 ms 110 ms 110 ms 161 ms 117 ms sl-bb22-chi-9-0.sprintlink.net [144.232.26.110]
13 120 ms 120 ms 120 ms 121 ms 123 ms 120 ms 123 ms sl-bb21-kc-3-0.sprintlink.net [144.232.20.129]
14 123 ms 120 ms 120 ms 120 ms 120 ms 123 ms 120 ms sl-gw9-kc-9-0.sprintlink.net [144.232.23.66]
15 130 ms 127 ms 130 ms 127 ms 130 ms 129 ms 127 ms [144.232.239.242]
16 131 ms 130 ms 131 ms 130 ms 131 ms 131 ms 130 ms 66-115-218-58.nextlevel.santel.net [66.115.218.58]
17 128 ms 128 ms 129 ms 131 ms 127 ms 128 ms 129 ms 66-115-196-186.hosts.sdnet.net [66.115.196.186]
18 129 ms 131 ms 128 ms 128 ms 129 ms 130 ms 129 ms L3two.bb2.iw.net [216.16.40.6]
19 131 ms 133 ms 131 ms 134 ms 133 ms 131 ms 134 ms viborg1.iw.net [216.16.29.91]
20 140 ms 142 ms 138 ms 145 ms 138 ms 138 ms 150 ms viborgDHCP-39.216-16-60.iw.net [216.16.60.39]

Ping statistics for viborgDHCP-39.216-16-60.iw.net
Packets: Sent = 7, Received = 7, Lost = 0 (0.0%)
Round Trip Times: Minimum = 138ms, Maximum = 150ms, Average = 141ms

Dowding · « **Reply #18 on:** July 15, 2007, 08:22:43 AM »

Cheers Cav!

Yeah, I seem to remember Skuzzy mentioning sprintlink being bad to have in your routing, some time ago. Will check that out.

There doesn't seem to be any packet loss in your trace though.

{edit} After doing a quick search around the BBS for discussions on Sprint, the number of hops involving Sprint in your route is starting to put me off moving!