Contact
Email us directly. Each channel has its own address for fast routing.
Support and response expectations
Set clear operational trust signals.
-
Support hours and timezone
Mon–Fri 09:00–17:00 CET. Email support with ticket tracking.
-
Typical response windows per category
Urgent: within 4 hours. Standard: within 24 hours. General: within 48 hours.
-
What qualifies as urgent
Complete outage, data loss risk, or security incident. Mark ticket as urgent when applicable.
-
Where status updates are posted
Incidents and maintenance are published on our status page. Subscribe for real-time updates.
Status page
View status pageSeperate contact
Abuse and security reporting
-
Abuse reporting instructions
Send abuse reports to abuse@buyvps.net. Include the nature of the abuse, affected service, and your contact details. Do not use the general contact form.
-
Evidence requirements
Include timestamps (UTC), source IP addresses, relevant log excerpts, and a brief description of the incident. Incomplete reports may delay processing.
-
Acknowledgement expectations
You receive an automated confirmation upon receipt. A human response follows within 48 hours. Further updates depend on investigation progress.
-
Security contact for responsible disclosure
Report vulnerabilities to security@buyvps.net. We follow coordinated disclosure. Do not disclose publicly before we have addressed the issue.
Report abuse
abuse@buyvps.netReport security vulnerability
security@buyvps.netCommon Questions
Questions.
Clear answers.
The following FAQ section provides answers to typical questions users have about regional deployment, infrastructure consistency, and operational policies.
How fast will a reply come?
The team responds to all messages that they receive during their established business operating schedule (normally within one business day). The speed at which you process urgent requests becomes faster when you give them full details about their final results.
What details should be included for technical presales?
The specification requires users to define target vCPU and RAM values, storage size requirements, expected I/O patterns, estimated traffic amounts, preferred region selection, and a summary of the workload. The system produces automatic recommendations, which users can access right away during this process.
Where can benchmark results and raw logs be found?
Benchmark results, test configuration, methodology, and raw logs are published on the Benchmarks page. The test suite requires a particular scenario for discussion.
I am blocked by network policy. What should be shared?
The system should record all relevant information which includes IP address, error messages, timestamps, and details about the attempted operation. The system enables users to check policy triggers and lets them quickly solve false positive alerts.
How are additional IPv4 requests handled?
Additional IPv4 is available on order/request and reviewed to protect network quality. The review is usually quick when the use case is clear.
Can a short technical call be scheduled for agencies or SaaS teams?
Yes. Share the goal, preferred region, and workload details, and a time slot can be proposed based on availability.