FP is Back Online Officially.

[Cam]

Out of courtesy, why the abrupt move to a new host? SiteGround is bound by SLAs and depending on the criticality of the incident, it's not going to be treated with the upmost priority. I work in an environment with constant SLA and OLA monitoring, so this isn't new to me.

In the future, if I knew I would need better support than what is offered, I would work work the provider to draft up an SLR (Service Level Requirement) from which they will draft up an SLA based on your requirements.

I don't know if it's really fair to up and leave a host just because the ticket didn't get that quick of resolution if they were still well within their described SLA for your service agreement. Now, if they beached an SLA, that's different and then that's cause for concern. I know this is a little more technical, but coming from someone that works in an SLA driven environment and holds ITIL certifications, this is second nature for me.

Due to the abrupt move to a new host, further downtime was experienced than what would have been caused just due to the SSL certificate. I don't know the timeline of events, but I feel like a day and a half of downtime could have been avoided.

Well, they do advertise that they have 24/7 support, with a ticket response time of less than 10 minutes. Obviously I didn't review the SLA prior to changing hosts, but that's one thing that they were promoting that did not occur with this ticket. And this was the only time I've ever needed help since I took over FP, so I didn't have a good first impression. Then there's the factor of cost. FP was on a server based in the UK (though SiteGround does have US-based servers), and I was paying an amount in GBP each month. There would then be a currency conversion in USD as far as what was actually charged to my account. Plus, I was paying a small fee of like $2 each month to my credit card company, due to it being an international transaction.

 

[mav3n]

Snip...

Well, they do advertise that they have 24/7 support, with a ticket response time of less than 10 minutes. Obviously I didn't review the SLA prior to changing hosts, but that's one thing that they were promoting that did not occur with this ticket. And this was the only time I've ever needed help since I took over FP, so I didn't have a good first impression. Then there's the factor of cost. FP was on a server based in the UK (though SiteGround does have US-based servers), and I was paying an amount in GBP each month. There would then be a currency conversion in USD as far as what was actually charged to my account. Plus, I was paying a small fee of like $2 each month to my credit card company, due to it being an international transaction.

That makes sense. If they failed to uphold their SLA, then that's an issue and I would be looking to seek a refund for whatever loss there was as a prorated amount during the downtime. The other factors matter too. I don't care too much about the host, just wondering. Thanks for the solid answer

 

[Deleted member 25872]

Glad we are back online. Thank you @Cameron for your hard work and time for restoring the community.

 

[Further]

I am glad things came to resonance for you.

 

[Carlos X]

Out of courtesy, why the abrupt move to a new host? SiteGround is bound by SLAs and depending on the criticality of the incident, it's not going to be treated with the upmost priority. I work in an environment with constant SLA and OLA monitoring, so this isn't new to me.

In the future, if I knew I would need better support than what is offered, I would work work the provider to draft up an SLR (Service Level Requirement) from which they will draft up an SLA based on your requirements.

I don't know if it's really fair to up and leave a host just because the ticket didn't get that quick of resolution if they were still well within their described SLA for your service agreement. Now, if they beached an SLA, that's different and then that's cause for concern. I know this is a little more technical, but coming from someone that works in an SLA driven environment and holds ITIL certifications, this is second nature for me.

Due to the abrupt move to a new host, further downtime was experienced than what would have been caused just due to the SSL certificate. I don't know the timeline of events, but I feel like a day and a half of downtime could have been avoided.

You know, there's something called common sense. When a host is un-willing to help you via tickets, which Cameron said happened - quoted below...

I apologize for the downtime everyone. All of this started with a SSL license that wasn't set to autorenew, and it just happened to expire at the worst possible time. I just started my new job and I flew out to Arkansas for training, so I've been extremely busy. I wouldn't have even noticed that FP was offline if a number of individuals had not messaged me on Skype, Discord, Facebook, etc. Anyways, a number of issues seemed to come up, and I wasn't getting too much assistance from the ticket I had opened up with our hosting provider. Ultimately, we decided that this was an opportunity go ahead and change hosts while we're at it, as I had been planning on us changing hosts for a while.

It's been a hectic last few days, and I am hopeful that there won't be any more hiccups! Thanks for your continued support of Forum Promotion. 🙂

...That means it's time to pack your bags and move to a new host. Siteground sounds like a very incompetent host. Other reasons can also be that server moves means server upgrades. I'm not too keen or sure what the specs were before the move, but most server moves are about increasing the hard drive space, speed improvements, better CPU, etc. You need to be on a good, reliable host. You need to have a good hosting environment to be able to upgrade your software to the latest version to do various things. XF2 speeds pageloads up, it also raises the requirements of the server. If you are on an ancient forum that is stuck in PHP5.6, don't be crying when you get hacked.

Those are good reasons to move to a new host.

EDIT: I'd seen the second page where Cam answered your question, but it seems to me that you skipped his original reasoning, which is the same as the second explanation.

Wow, this thread went to shit real quick...

That would've been a perfect time for you to join in their lighthearted joking fun...

 

[Jason76]

Not sure if a British or US location is needed specifically as it's an international thing. Note, in SEO, if you want to rank more in a certain nation, then hosting location seems to be a thing.

 

[Page]

Not sure if a British or US location is needed specifically as it's an international thing. Note, in SEO, if you want to rank more in a certain nation, then hosting location seems to be a thing.

True but with FP, it's based worldwide. Then again FP tends to get more traffic from USA. There are British people here but not allot

 

[Van1lla ™]

The creators of FP were British, so clearly it’s just remained on our shores till now. That’s all it originally came down to from the start, nothing to do with traffic at first.

 

[Mushmellow]

How is the new hosting better?

Well, it's hosted in the North Pole and Rudolf the Reindeer is the head of Customer Support. How can it not be better?

 

[Deleted member 1609]

Wow, this thread went to shit real quick...

That would've been a perfect time for you to join in their lighthearted joking fun...

Absolutely no fun or jokes are allowed on Forum Promotion. This forum is a high-tier business, and only serious posts and users are welcome. Below is a picture of what you should look like when you browse this forum:

 

[Bryn]

Even so, we can have a bit of fun here, can't we?

 

[Bluezone777]

Fun like all things has its place. Lucky had genuine questions and concerns he wanted answered and probably didn't appreciate the parade of jokes that followed because they were burying his serious post. It doesn't mean Lucky doesn't like jokes and whatnot but would probably rather they stay where they belong which is not in a serious announcement regarding the website's downtime and other uptime issues especially when there are people namely Lucky in here who had actual questions that they wanted answered.