Public reachability
HTTP, HTTPS, DNS and mail protocols can be checked independently of an internal VPN.
Check an endpoint →Measured evidence / 28 August 2026
Performance and infrastructure
Current service state, dated measurements and the limits of each result. We publish what was measured, where it was measured and what it does not guarantee.
OperationalHTTP, HTTPS and TLS checked at publication
168 msAverage full HTTPS request from Athens office, 12 samples
30-day historyCollection begins 28/08/2026
Live service summary
Current state and measured history
The live state is separate from the contractual SLA target. No historical percentage is shown until a complete measurement window exists.
Current public stateOperationalHTTP, HTTPS and certificate checks.
Measured uptimeCollectingMeasurement started 28/08/2026
Athens office HTTPS168 ms12 samples, average total request time, 28/08/2026.
TLS certificate04/11/2026Let's Encrypt certificate validity at the time of publication.
Methodology
Numbers with a boundary
The office probe requested https://fastvps.gr/ twelve times over IPv4 from an Athens business connection. Average DNS was 43.3 ms, TCP connect 59.4 ms, TLS complete 91.6 ms, time to first byte 110.7 ms and total request time 168.2 ms.
This is a route-and-application snapshot. It is not a universal latency promise: geography, ISP peering, browser, cache and current load all matter.
- All 12 HTTPS requests returned HTTP 200
- Probe date: 28/08/2026
- Probe origin: Athens office connection
- Target: active FastVPS public web edge
- Figures include DNS, TCP, TLS and HTTP
- Raw method can be repeated in the browser latency tool
Storage sample
Direct-I/O sample on the active web node
A 128 MiB low-priority direct-I/O sample was run and removed immediately. It describes this web-node path at that moment, not every VPS plan.
Sequential write16.1 MB/s128 MiB, direct I/O, idle priority.
Sequential read78.2 MB/s128 MiB, direct I/O, idle priority.
Web node root free43.0%Zabbix sample at 13:36 EEST on 28/08/2026.
Web node CPU5.2%Zabbix sample at 13:36 EEST on 28/08/2026.
The storage sample is disclosed for transparency and capacity work. A customer VPS benchmark is supplied only for the actual destination platform because storage pools and contention profiles differ.
Operating model
What is monitored
Checks are selected by service. A product page never replaces the written monitoring and recovery scope.
Resource telemetry
CPU, memory, filesystem use and storage latency are monitored on agreed systems.
See managed VPS →Backup and replication
Backup, replication and restore readiness are separate states and must be defined per service.
Read the SLA →Measure from the network that matters to you.
Run the latency tool from your office and include the result with the workload requirements.