Contact 922 S5 Support

Before you write

Include the account email, the plan involved and — for payment questions — the transaction hash. Payments are matched by hash and account, so that single line usually resolves the ticket immediately.

What support can do

• Set up targeting, sessions and endpoints for a specific workload
• Match a crypto payment that under- or over-shot the invoice
• Replace addresses that stopped behaving
• Explain which product line fits a job before you buy

Response times

Live chat is typically answered within minutes during active hours. Written requests are handled in order, and payment issues are prioritised because they block access.

Questions that resolve in one message

• Payment confirmed, balance empty. Send the transaction hash — that is the only thing needed to reconcile it.
• Wrong amount sent. Send the difference to the same address or write in with the hash; nothing is lost either way.
• An IP stopped working. Report the address instead of moving it to another profile. Replacements are issued after review.
• Exit shows the wrong country. Check DNS first — socks5h:// rather than socks5:// fixes most of these before a ticket is needed.

Before you buy

Pre-sale questions are welcome and answered without a sales process. Describe the workload — how many identities, which platforms, what volume — and support will say which line fits, including when the answer is metered traffic rather than owned IPs. Buying the wrong unit is the most common way people overspend here, and it is entirely avoidable.

Response expectations

Live chat is the fastest channel and is normally answered within minutes while the desk is staffed. Written requests are worked in order of arrival, with payment problems pulled to the front because they block access to something already paid for. Replacement requests for addresses that stopped behaving are reviewed the same day they are reported.

If a message goes unanswered longer than expected, resend it in the same thread rather than opening a new one — duplicate threads split the history and slow the answer down.