Featured AI Products
Compute
Build, deploy, and scale cloud compute resources
Containers and Images
Safely store and manage containers and backups
Managed Databases
Fully managed resources running popular database engines
Management and Dev Tools
Control infrastructure and gather insights
Networking
Secure and control traffic to apps
Security
Help protect your account and resources with these security features
Storage
Store and access any amount of data reliably in the cloud
Browse all products
AI/ML
CMS
Data and IoT
Developer Tools
Gaming and Media
Hosting
Security and Networking
Startups and SMBs
Web and App Platforms
See all solutions
Community
Documentation
Developer Tools
Get Involved
Utilities and Help
Become a Partner
Marketplace
Pricing

- Community
- DigitalOcean
- Community
- DigitalOcean

Is there something wrong with the DO ticket/support systems?

Posted on April 7, 2017

I have submitted a request for the “Recovery Environment” to fetch db backups I prepared. Normally response time of DO is acceptable. However this time I couldn’t even be sure that support team is getting my messages. Is something wrong with the support system?

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

muratcansoy

April 7, 2017

48 hours is an acceptable time in normal conditions. But when my droplet is closed due to security reasons I think there should be another support process here. DO should either give community, self service capabilities to retrieve their critical data or put in place a separate support process. Our service is critically damaged because of this reason. Something that can be solved in 1 hour just became 2 days… This is not how SW market works anymore.

Woet

April 7, 2017

Unless it’s been over 48 hours, no, there’s nothing wrong with it.

Jonathan Tittle

April 7, 2017

@muratcansoy

In my experience, the delay depends on the actual issue. In most cases they will simply disable the networking for the Droplet and force you to login using Console via the DigitalOcean control panel.

In other cases, there may be more to the issue which causes a delay. It’s hard to tell without the exact reasoning.

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

View all products

Start building today

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Unless it’s been over 48 hours, no, there’s nothing wrong with it.

Jonathan Tittle

April 7, 2017

@muratcansoy

In my experience, the delay depends on the actual issue. In most cases they will simply disable the networking for the Droplet and force you to login using Console via the DigitalOcean control panel.

In other cases, there may be more to the issue which causes a delay. It’s hard to tell without the exact reasoning.

Report this

Is there something wrong with the DO ticket/support systems?

Become a contributor for community

DigitalOcean Documentation

Resources for startups and AI-native businesses

The developer cloud

Start building today