search

Support

We are here to help you get the most out of ShredStream.com. Here is how to reach us.

hashtag
Discord (Preferred)

Discord is the fastest way to get technical support.

  1. Join the ShredStream.com Discord server: ShredStream Discordarrow-up-right

  2. Navigate to the #ticket channel.

  3. Open a new ticket describing your issue.

A team member will respond as soon as possible. Discord tickets are our primary support channel and typically have the fastest response times.

Tip: Include your stream ID, server region, and a brief description of the problem when opening a ticket. This helps us diagnose the issue faster.

hashtag
Telegram

If you prefer Telegram over Discord, you can reach us there as well.

Send a message describing your issue and we will get back to you. Telegram is a great alternative for quick questions and support conversations.

hashtag
Email

Email is best for:

  • Partnership inquiries

  • Business development

  • General information requests

  • Press and media

Note: For technical support and troubleshooting, please use Discord or Telegram instead. Those channels are monitored more frequently and are better suited for back-and-forth debugging.

hashtag
X / Twitter

Follow us on X for:

  • Product updates and new feature announcements

  • Performance benchmarks and comparisons

  • Solana ecosystem news relevant to ShredStream.com users

  • Maintenance notices and status updates

DMs are open, but for support requests we recommend Discord or Telegram for a faster response.

hashtag
GitHub

Visit our GitHub for open-source resources and technical references.

hashtag
Medium

Read our blog for in-depth articles, tutorials, and product updates.

hashtag
When Contacting Support

To help us resolve your issue quickly, please include:

  • Stream ID -- found on your stream detail page in the dashboard

  • Region -- the region your stream is configured in

  • Description -- what you expected to happen versus what actually happened

  • Relevant logs or screenshots -- kernel drop counters, error messages, or packet captures if applicable

  • Timestamp -- when the issue started, including your timezone

PreviousFAQ

Last updated

Was this helpful?