Widget Settings
Widget settings form goes here
YOU ARE HERE
- Support
Support
How can we help you?
Open Tickets
Too many down times
Ticket #456- Created on 10/29/13 at 06:33 - Last reply About 1 Month ago by alex ALERT
Hi I have installed agent to monitor the usage of the droplet done via Anturis
and lately there was a lot of down time. One that caught my eye was this
Incident report
New Critical Incident started at 13:10 MST on Monday, October 28
Critical Incident started at 13:10 MST on Monday, October 28 with ace has ended at 13:51 MST on Monday, October 28.
Incident duration was 41 minutes.
The server did not respond for 41 minutes.As you see 41 minutes is a big deal for us as we are going to lose alot of revenue we need you guys to check if these records are correct and if so why and will this happen again? or do we need to purchase some sort of cluster ? this is a very critical situation
Waiting for your reply
and lately there was a lot of down time. One that caught my eye was this
Incident report
New Critical Incident started at 13:10 MST on Monday, October 28
Critical Incident started at 13:10 MST on Monday, October 28 with ace has ended at 13:51 MST on Monday, October 28.
Incident duration was 41 minutes.
The server did not respond for 41 minutes.As you see 41 minutes is a big deal for us as we are going to lose alot of revenue we need you guys to check if these records are correct and if so why and will this happen again? or do we need to purchase some sort of cluster ? this is a very critical situation
Waiting for your reply
Hi,
Thank you for reaching us, We are looking into this issue and will update you.
Alex
Thank you for reaching us, We are looking into this issue and will update you.
Alex
Posted on 10/29/13 at 07:21
Sub domain to point to a different droplet
Ticket #569- Created on 11/02/13 at 06:33 - Last reply About 1 Month ago by William
Hi I have installed agent to monitor the usage of the droplet done via Anturis
and lately there was a lot of down time. One that caught my eye was this
Incident report
New Critical Incident started at 13:10 MST on Monday, October 28
Critical Incident started at 13:10 MST on Monday, October 28 with ace has ended at 13:51 MST on Monday, October 28.
Incident duration was 41 minutes.
The server did not respond for 41 minutes.As you see 41 minutes is a big deal for us as we are going to lose alot of revenue we need you guys to check if these records are correct and if so why and will this happen again? or do we need to purchase some sort of cluster ? this is a very critical situation
Waiting for your reply
and lately there was a lot of down time. One that caught my eye was this
Incident report
New Critical Incident started at 13:10 MST on Monday, October 28
Critical Incident started at 13:10 MST on Monday, October 28 with ace has ended at 13:51 MST on Monday, October 28.
Incident duration was 41 minutes.
The server did not respond for 41 minutes.As you see 41 minutes is a big deal for us as we are going to lose alot of revenue we need you guys to check if these records are correct and if so why and will this happen again? or do we need to purchase some sort of cluster ? this is a very critical situation
Waiting for your reply
Hi,
Thank you for reaching us, We are looking into this issue and will update you.
Alex
Thank you for reaching us, We are looking into this issue and will update you.
Alex
Posted on 10/29/13 at 07:21
Closed Tickets
Too many down times
Ticket #456- Created on 10/29/13 at 06:33 - Last reply About 1 Month ago by alex ALERT
Hi I have installed agent to monitor the usage of the droplet done via Anturis
and lately there was a lot of down time. One that caught my eye was this
Incident report
New Critical Incident started at 13:10 MST on Monday, October 28
Critical Incident started at 13:10 MST on Monday, October 28 with ace has ended at 13:51 MST on Monday, October 28.
Incident duration was 41 minutes.
The server did not respond for 41 minutes.As you see 41 minutes is a big deal for us as we are going to lose alot of revenue we need you guys to check if these records are correct and if so why and will this happen again? or do we need to purchase some sort of cluster ? this is a very critical situation
Waiting for your reply
and lately there was a lot of down time. One that caught my eye was this
Incident report
New Critical Incident started at 13:10 MST on Monday, October 28
Critical Incident started at 13:10 MST on Monday, October 28 with ace has ended at 13:51 MST on Monday, October 28.
Incident duration was 41 minutes.
The server did not respond for 41 minutes.As you see 41 minutes is a big deal for us as we are going to lose alot of revenue we need you guys to check if these records are correct and if so why and will this happen again? or do we need to purchase some sort of cluster ? this is a very critical situation
Waiting for your reply
Hi,
Thank you for reaching us, We are looking into this issue and will update you.
Alex
Thank you for reaching us, We are looking into this issue and will update you.
Alex
Posted on 10/29/13 at 07:21
Domain Propergation
Ticket #885- Created on 10/19/13 at 06:33 - Last reply About 1 Month ago by support ALERT
Hi I have installed agent to monitor the usage of the droplet done via Anturis
and lately there was a lot of down time. One that caught my eye was this
Incident report
New Critical Incident started at 13:10 MST on Monday, October 28
Critical Incident started at 13:10 MST on Monday, October 28 with ace has ended at 13:51 MST on Monday, October 28.
Incident duration was 41 minutes.
The server did not respond for 41 minutes.As you see 41 minutes is a big deal for us as we are going to lose alot of revenue we need you guys to check if these records are correct and if so why and will this happen again? or do we need to purchase some sort of cluster ? this is a very critical situation
Waiting for your reply
and lately there was a lot of down time. One that caught my eye was this
Incident report
New Critical Incident started at 13:10 MST on Monday, October 28
Critical Incident started at 13:10 MST on Monday, October 28 with ace has ended at 13:51 MST on Monday, October 28.
Incident duration was 41 minutes.
The server did not respond for 41 minutes.As you see 41 minutes is a big deal for us as we are going to lose alot of revenue we need you guys to check if these records are correct and if so why and will this happen again? or do we need to purchase some sort of cluster ? this is a very critical situation
Waiting for your reply
Hi,
Thank you for reaching us, We are looking into this issue and will update you.
Alex
Thank you for reaching us, We are looking into this issue and will update you.
Alex
Posted on 10/29/13 at 07:21
How to access via Putty
Ticket #152- Created on 10/09/13 at 06:33 - Last reply About 1 Month ago by support
Hi I have installed agent to monitor the usage of the droplet done via Anturis
and lately there was a lot of down time. One that caught my eye was this
Incident report
New Critical Incident started at 13:10 MST on Monday, October 28
Critical Incident started at 13:10 MST on Monday, October 28 with ace has ended at 13:51 MST on Monday, October 28.
Incident duration was 41 minutes.
The server did not respond for 41 minutes.As you see 41 minutes is a big deal for us as we are going to lose alot of revenue we need you guys to check if these records are correct and if so why and will this happen again? or do we need to purchase some sort of cluster ? this is a very critical situation
Waiting for your reply
and lately there was a lot of down time. One that caught my eye was this
Incident report
New Critical Incident started at 13:10 MST on Monday, October 28
Critical Incident started at 13:10 MST on Monday, October 28 with ace has ended at 13:51 MST on Monday, October 28.
Incident duration was 41 minutes.
The server did not respond for 41 minutes.As you see 41 minutes is a big deal for us as we are going to lose alot of revenue we need you guys to check if these records are correct and if so why and will this happen again? or do we need to purchase some sort of cluster ? this is a very critical situation
Waiting for your reply
Hi,
Thank you for reaching us, We are looking into this issue and will update you.
Alex
Thank you for reaching us, We are looking into this issue and will update you.
Alex
Posted on 10/29/13 at 07:21