The site will be down for maintenance on December 16 at 2:00 AM PST (2 hours after midnight). Estimated downtime is 1 hour.
(See timezone information here: http://wwp.greenwichmeantime.com/time-z ... ific-time/)
Kitely will be down for a 1 hour upgrade cycle on Dec 16
-
Ilan Tochner
- Posts: 6728
- Joined: Sun Dec 23, 2012 8:44 am
- Has thanked: 5251 times
- Been thanked: 4675 times
- Contact:
-
Graham Mills
- Posts: 1314
- Joined: Sun Dec 23, 2012 2:26 pm
- Has thanked: 1134 times
- Been thanked: 1142 times
Re: Kitely will be down for a 1 hour upgrade cycle on Dec 16
I note from the blog that you did some nice stuff for merchants again http://www.kitely.com/virtual-world-new ... ct-prices/. However, is there any way that you could avoid taking the grid down at the same time? Maybe you did some tweaking there too? Fortunately I'm not teaching at the moment but I can imagine that the shift in time (one or two hours later?) would also be more likely to disrupt teaching schedules in the UK. Just sayin'.
-
Ilan Tochner
- Posts: 6728
- Joined: Sun Dec 23, 2012 8:44 am
- Has thanked: 5251 times
- Been thanked: 4675 times
- Contact:
Re: Kitely will be down for a 1 hour upgrade cycle on Dec 16
Hi Graham,
We have customers in more than 70 countries and a significant number of them also use the system during weekends and nights. We intend to eventually roll out a solution which will enable us to make site updates without taking down the system. However, until that is available, there will always be people who are affected by maintenance downtime. As that is the case, we try to schedule maintenance cycles for midnight PST (8:00AM GMT) to minimize the effect it will have on the majority of our users. Today we had issues that delayed that start time by a couple of hours, it is not our intention to make a habit of starting this late.
As a side note, we almost always make additional changes we don't announce on our blog. We focus our blog posts on the most user-facing changes and enhancements. Doing otherwise will result in very long blog posts and a waste of both our time (writing them) and your time (reading them).
We have customers in more than 70 countries and a significant number of them also use the system during weekends and nights. We intend to eventually roll out a solution which will enable us to make site updates without taking down the system. However, until that is available, there will always be people who are affected by maintenance downtime. As that is the case, we try to schedule maintenance cycles for midnight PST (8:00AM GMT) to minimize the effect it will have on the majority of our users. Today we had issues that delayed that start time by a couple of hours, it is not our intention to make a habit of starting this late.
As a side note, we almost always make additional changes we don't announce on our blog. We focus our blog posts on the most user-facing changes and enhancements. Doing otherwise will result in very long blog posts and a waste of both our time (writing them) and your time (reading them).