Kitz Forum
Announcements => Site & Forum Discussion => Topic started by: Weaver on March 17, 2020, 12:50:08 AM
-
Was there some maintenance going on? Because I couldn’t access the server for a couple of minutes - was trying to post something and I lost my post text as it timed out on me.
-
Same here but was just browsing. Couldn't ping either.
-
It wasn't me as I was tucked up in bed, nor was I advised of any scheduled maintenance.
Saying that, Vidahost has been bought out and the service isn't quite the same as the server is just a tiny fish in now what is a very large pond.
Sorry guys :/
-
Was there some maintenance going on? Because I couldn’t access the server for a couple of minutes - was trying to post something and I lost my post text as it timed out on me.
Was that with the iPad? One advantage with PC browsers is you can usually just hit reload when that happens and it will ask to re-submit the form.
-
Browser died because it timed out and I then got an error page. I pinged and then tracerouted with a tool on the iPad, then did a remote ping, with an internet-based tool from a remote address and then the same with a different web-based tool. All were getting no response from forum.kitz.co.uk
-
Its been on and off, so I started an MTR, here is the data.
Looks like some telia transit issues. Interesting you said they been brought out kitz, as I was shocked to see godaddy in the routing, I wonder if you now on a godaddy hosting platform? O_o
Host Loss% Snt Last Avg Best Wrst StDev
1. 216.53.155.90.in-addr.arpa 0.0% 197 12.2 12.1 11.8 13.3 0.2
2. e.aimless.tch.aa.net.uk 83.2% 197 12.5 12.4 11.8 13.6 0.3
3. xe-0-1-0-3-1.r04.londen05.uk.bb.gin.ntt.net 0.0% 197 12.8 13.1 12.6 18.7 0.5
4. ae-0.r24.londen12.uk.bb.gin.ntt.net 0.0% 197 13.0 13.5 12.5 43.5 2.6
5. ae-8.r02.londen03.uk.bb.gin.ntt.net 0.0% 197 13.0 13.1 12.5 18.0 0.5
6. ldn-b7-link.telia.net 0.0% 197 13.6 14.0 12.4 50.1 4.3
7. ldn-bb4-link.telia.net 99.5% 197 13.5 13.5 13.5 13.5 0.0
8. ldn-b5-link.telia.net 67.0% 197 13.5 13.4 12.5 30.8 2.3
9. ae0.cr-sargas.lon1.bb.godaddy.com 67.0% 197 13.1 13.0 12.6 13.6 0.2
10. ae0.cr-merak.lon5.bb.godaddy.com 67.5% 197 13.4 13.6 12.8 29.5 2.2
11. 87.230.114.202 67.5% 197 13.6 14.3 13.6 24.8 1.7
12. 185.24.99.65 67.9% 196 22.1 34.6 15.2 127.1 26.6
13. kitz.servers.eqx.misp.co.uk 74.5% 196 14.0 14.2 13.9 15.9 0.3
yeah
https://www.ukbusinessforums.co.uk/threads/by-by-vidahost.387367/
-
Yup. Sad day and end of an era.
I went over to TSO but there was no noticeable change for me, as mentioned in that thread Vidahost was still run separately/independently for those with their own servers, so I didn't really notice much difference.
Not too happy about the GoDaddy merger but they seem to have left my server along as it was despite it being a bespoke build package. They probably don't even know from looking at it on the rack that Dom would do things like put extra RAM in. I did start looking around last year when my annual fees were due, but it does seem difficult to find decent UK hosting with Cpanel that doesn't cost the earth.. but then I also had my own health issues.... and don't know if I want the hassle of moving.
Vidahost were always good at informing about scheduled maintenance or even just general news.. but now there's no correspondence apart from billing.
Like I said above tiny fish in a large pond.
-
1 <1 ms <1 ms <1 ms 192.168.1.1
2 12 ms 11 ms 11 ms 252.core.plus.net [195.166.130.252]
3 12 ms 14 ms 12 ms 84.93.253.103
4 12 ms 12 ms 12 ms 195.99.125.138
5 12 ms 12 ms 13 ms 109.159.252.144
6 13 ms 13 ms 13 ms 166-49-209-132.gia.bt.net [166.49.209.132]
7 13 ms 13 ms 13 ms ldn-b9-link.telia.net [213.248.97.50]
8 * * * Request timed out.
9 12 ms 12 ms 12 ms ldn-b5-link.telia.net [213.155.132.197]
10 13 ms 15 ms 14 ms ae0.cr-sargas.lon1.bb.godaddy.com [213.248.96.78]
11 13 ms 13 ms 13 ms ae0.cr-merak.lon5.bb.godaddy.com [87.230.113.1]
12 13 ms 13 ms 13 ms 87.230.114.202
13 21 ms 29 ms 25 ms 185.24.99.65
14 14 ms 14 ms 14 ms kitz.servers.eqx.misp.co.uk [185.24.98.37]
... and that's what I kind of miss.
Vidahost knew what the site did and Dom arranged direct peering with most of the UK ISPs. Little things, but it's what made them good.
>>> I wonder if you now on a godaddy hosting platform?
Don't think so. Still eqx.misp which are the Vidahost racks.
I also continue to use the Vidahost/TSO portal for tickets/billing/domain changes.
-
Not much difference from Zen:
1 losubs.subs.bng1.th-lon.zen.net.uk (62.3.80.17) 13.356 ms 20.036 ms 12.996 ms
2 ae1-177.cr2.th-lon.zen.net.uk (62.3.80.38) 13.625 ms 21.378 ms 12.932 ms
3 vl-50.ae-5.pe2.thn-lon.zen.net.uk (51.148.73.54) 13.435 ms 22.725 ms 13.627 ms
4 51-148-73-107.dsl.zen.co.uk (51.148.73.107) 25.776 ms 23.853 ms 13.890 ms
5 ae-8.agg1.lond1.ptn.zen.net.uk (51.148.73.14) 31.579 ms 23.069 ms 13.684 ms
6 ldn-b5-link.telia.net (62.115.169.132) 14.306 ms 13.419 ms 22.332 ms
7 ae0.cr-sargas.lon1.bb.godaddy.com (213.248.96.78) 13.262 ms 18.862 ms 13.775 ms
8 ae0.cr-merak.lon5.bb.godaddy.com (87.230.113.1) 22.949 ms 15.993 ms 17.285 ms
9 87.230.114.202 (87.230.114.202) 14.593 ms 19.241 ms 14.175 ms
10 185.24.99.65 (185.24.99.65) 43.465 ms 33.445 ms 30.583 ms
11 kitz.servers.eqx.misp.co.uk (185.24.98.37) 15.107 ms 15.159 ms 19.734 ms
-
Kitz does it in 14 hops, Alex does it in 11 and someone else does it in 9 . . .
traceroute to 185.24.98.37 (185.24.98.37), 30 hops max, 60 byte packets
1 AP 3.230 ms 3.152 ms 3.112 ms
2 ae50-ner002.loh.as13285.net (78.144.1.23) 31.174 ms 34.012 ms 34.034 ms
3 ae50-scr102.loh.as13285.net (78.144.1.22) 33.996 ms 36.556 ms 36.553 ms
4 host-78-144-14-160.as13285.net (78.144.14.160) 36.522 ms host-78-144-14-166.as13285.net (78.144.14.166) 36.482 ms host-78-144-14-164.as13285.net (78.144.14.164) 38.582 ms
5 ae1.cr-sargas.lon1.bb.godaddy.com (195.66.225.173) 38.576 ms 38.542 ms 41.417 ms
6 ae0.cr-merak.lon5.bb.godaddy.com (87.230.113.1) 41.374 ms 37.914 ms 40.247 ms
7 87.230.114.202 (87.230.114.202) 40.103 ms 32.477 ms 32.243 ms
8 185.24.99.65 (185.24.99.65) 41.122 ms 41.010 ms 40.907 ms
9 kitz.servers.eqx.misp.co.uk (185.24.98.37) 34.755 ms 34.693 ms 37.352 ms
No real difference.
-
It used to be like this
From Plusnet
Tracing route to kitz.co.uk [185.24.98.37]over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 11 ms 11 ms 11 ms lo0.12.central12.ptw-bng01.plus.net [195.166.128.172]
3 11 ms 11 ms 10 ms irb.12.ptw-cr02.plus.net [84.93.249.34]
4 12 ms 12 ms 12 ms 195.66.237.228
5 12 ms 13 ms 13 ms switch-004.sl5.misp.co.uk [91.198.165.76]
6 12 ms 12 ms 12 ms kitz.servers.eqx.misp.co.uk [185.24.98.37]
From Sky
1 <1 ms <1 ms <1 ms home.gateway [192.168.1.253]
2 * * * Request timed out.
3 11 ms 11 ms 11 ms 02780842.bb.sky.com [2.120.8.66]
4 10 ms 10 ms 11 ms uk.slo.ld5.201.r1.misp.co.uk [195.66.237.228]
5 11 ms 11 ms 11 ms switch-004.sl5.misp.co.uk [185.52.26.251]
6 9 ms 9 ms 9 ms kitz.servers.eqx.misp.co.uk [185.24.98.37]
The direct peering Dom put in place for the server has gone and it now goes via telia > godaddy
Kitz does it in 14 hops
Makes little difference at the end of the day.
Plusnet uses dedicated WBMC and their own MSILs. BTr does similar and you sometimes see the bRAS and core routing hops which are always hidden using L2TP for some other ISPs that use BTw shared. ... although I notice you miss out on all the telia routing.
-
Not noticed any issues today.