Support
How can we help?
For an existing service, use the support instructions supplied with your order. The resources below can help you narrow down a fault or prepare a billing request.
FAQ
Answers about bandwidth, streaming, network, and billing.
Support tickets
Open a billing or technical ticket and read replies in your client area.
Looking Glass
Check endpoint availability before planning a route test.
Service status
Check whether live monitoring is available and how to report an incident.
Report abuse
Report abuse originating from our infrastructure.
Questions & answers
Getting support
Browse all topicsWhich details help diagnose slow delivery?
Include the package or server ID, affected audience network, time window, approximate throughput and whether latency rises at the same time. Distinguish one slow client from a problem seen by multiple customers.
Which details should stay out of a support request?
Do not send passwords, private keys, recovery phrases or full payment credentials. Redact tokens and personal data from logs; keep timestamps and error messages that identify the fault.
How do I describe a storage bottleneck?
Note what was reading or writing, the time window, free space and whether the problem affects cached and uncached files. Include recent workload changes.
What belongs in a billing query?
Include the invoice reference, service identifier and disputed line item. For a crypto payment, include the asset, network and transaction ID, never the wallet recovery phrase.
How do I prepare for a maintenance request?
List the affected services, a window with time zone, who can approve interruption and how you will verify playback or delivery afterward.