Service Availability

DanubeData runs on enterprise-grade dedicated hardware in Hetzner's Falkenstein (Germany) datacenter and is engineered for high availability. This page explains how we approach availability, maintenance, and support — and what you can do to maximize uptime for your own workloads.

Availability commitments

DanubeData does not currently offer a contractual SLA with uptime percentages or service credits. We focus on transparency and engineering instead:

  • Public status page — status.danubedata.ro with real-time component status, incident history, and maintenance schedules
  • Proactive monitoring — the platform is continuously monitored with automated alerting
  • Incident communication — significant incidents are posted to the status page as they unfold, with post-incident summaries for major events
  • Support — via the dashboard ticket system and support@danubedata.ro

If your use case requires contractual availability guarantees, contact support@danubedata.ro to discuss your requirements before onboarding.

Scheduled maintenance

  • Maintenance that may impact customer workloads is announced in advance on the status page and via dashboard notifications
  • Windows are scheduled during off-peak hours and designed for minimal or no impact
  • Emergency maintenance (e.g. critical security patches) is performed with as much notice as circumstances allow and documented afterwards

Building for availability

Maximize the availability of your own workloads:

  1. Use replicas — managed databases and caches support read replicas
  2. Run multiple instances — spread stateless workloads across several VPS or serverless containers
  3. Enable snapshots — automated snapshots for VPS, databases, caches, and queues
  4. Monitor proactively — use Uptime Checks and Metric Alerts to catch problems early
  5. Keep backups — snapshot before risky changes and test your restore path

Data protection

  • Object storage is replicated across multiple physical servers
  • Automated snapshots with configurable retention are available for VPS, databases, caches, and queues
  • Managed services are additionally backed up at the platform level

Incident response

  1. Detection — automated monitoring and alerting
  2. Communication — status page updated as the incident unfolds
  3. Mitigation and resolution — worked continuously until service is restored
  4. Post-incident review — significant incidents receive a public summary

Support

  • Dashboard tickets — the fastest route; tickets are tied to your account and resources
  • Email — support@danubedata.ro
  • Phone support is not offered