Home / Compute
4vps.su
vc.ru/claim/2739295-4vps-su-obzor-problem-s-vds-v-yaponiiCloud VMcompute/4vps-suJSONcomparereport an errorprovider JSON
- Free allowance
- A VDS was paid for in a Japanese location and never worked; the provider did not return the money, did not answer the ticket, and removed the buyer from its chat.
- Verdict
- deadthe offer or the service no longer exists
- Cost
- no price stated
- Identity
- card?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- noneno named constraint binds
- Evidence
- reported1 source; a third party said so
- Freshness
- checked 2026-10-22checked 2026-10-22 (live)
| Free tier | A VDS was paid for in a Japanese location and never worked; the provider did not return the money, did not answer the ticket, and removed the buyer from its chat. A separate refund request sent to the same payment details went unanswered for more than 15 days. Nothing was delivered, so there is no capacity to price. unit none; metered on wall-clock; none |
|---|
| Price | none stated |
|---|
| Binding | none The order never produced a machine, so no quota or rate binds: the failure is delivery rather than a limit, and the record exists so that the name is not tried again. |
|---|
| Identity | card (placeholder) unverified: no page stating the signup requirement was read; the record's evidence covers a paid Japanese VDS order that never started, an unanswered ticket, and a refund request sent to "the same payment details", which shows a payment was taken but names no rail, no card requirement, no hold and no debit or prepaid answer |
|---|
| Egress | not stated |
|---|
| Interface | unknown inferred from the tooling the provider documents; not probed |
|---|
| Tooling | not stated |
|---|
| Composes with | It composes with nothing, and its value is negative: a paid Japanese location looks like the foreign-reachable shape is hunting, which is exactly why the failure is worth a record. |
|---|
| Reliability | no reliability event recorded |
|---|
| Notes | A reader who wants to overturn it needs one delivered server from this provider, which nobody produced. |
|---|
| Parsed numbers | |
|---|
Evidence 1
| date | source | what it proved |
|---|
| 2026-10-22 | vc.ru/claim/2739295-4vps-su-obzor-problem-s-vds-v-yaponii | a published complaint states the VDS was paid for and did not start, the money was not returned, the ticket went unanswered, the buyer was removed from the chat, and a refund request to the same payment details went unanswered for more than 15 days |
More fields 1
| facets | {"class": "delivery-failure","free_tier_kind": "none","shape": {"vcpu": null,"ram_gib": null,"gpu_class": null,"gpu_count": 0}} |
|---|
Unknown values 7
- egress metered: egress metering was not published
- egress terms: a source was read and is silent on this field
- interface: the access interface was not established
- per object cap stated: the field does not apply to this kind of offer
- reliability note: nothing of this kind was observed
- retention stated: the field does not apply to this kind of offer
- tooling: a source was read and is silent on this field