# Support FAQ ## Who is eligible to receive Support? Customers who have an active, paid subscription or who pay for on-demand use of SingleStore and/or a SingleStore self-hosted License are eligible to receive SingleStore Support during the subscription or License Term. ## What are the different Support Tiers available? Information on our SingleStore Support Tiers and the differences between them are listed on [www.singlestore.com/support](https://www.singlestore.com/support/). Existing customers may have Standard, Silver, or Platinum Support as defined in their SingleStore Agreement. ## Can I upgrade my Support Tier? Yes, please reach out to your Account Executive or contact team\@singlestore.com to upgrade your Support Tier. ## Where can I go for help if I do not have access to paid support? 1. **SingleStore Forums**. To ask questions and share knowledge with other members of the community, join our public forums at [www.singlestore.com/forum](https://www.singlestore.com/forum). SingleStore employees will also monitor the forums during business hours in California. 2. **Ask StackOverflow**. We and other SingleStore experts are active on the StackOverflow community. If you can’t find what you’re looking for in our documentation, [just ask a question](http://stackoverflow.com/questions/ask). Make sure to tag it with `#singlestore`! ## When should I use SingleStore Support? You may file a support ticket if you encounter the following: * A SingleStore cluster outage and you need help recovering * A critical error that impedes your workload or use of SingleStore * An issue that you believe is caused by a product bug or deficiency * Unexpected behavior that requires further explanation * Questions on product functionality or you would like to file a feature request ## How do I sign up for an account on SingleStore’s Support Portal? 1. Navigate to [support.singlestore.com](https://support.singlestore.com). 2. Click **Sign In** at the top of the page. 3. In the modal window, click the **Sign up** link to create a new account. ![](https://images.contentstack.io/v3/assets/bltac01ee6daa3a1e14/bltb9335c4ac5adc157/6a2c4314724dc3f94781c68d/16083b57a0167b-65mNEx.png) 4. Fill in your information and click **Sign Up**. ![](https://images.contentstack.io/v3/assets/bltac01ee6daa3a1e14/blt92ce57e45bf5a44d/6a2c43290fc2f449663f06a8/16083b57a098fe-LVq7c2.png) If successful, a confirmation message will direct you to check your email account for a welcome email with an account verification link. Check your junk/spam folder if you do not receive your welcome email within a few minutes. ![](https://images.contentstack.io/v3/assets/bltac01ee6daa3a1e14/blt6e0eb2fbbb7c1098/6a2c431303b373329d90816a/16083b57a10b97-Mj17vH.png) 5. After clicking on the verification link, you will be directed back to the support portal. Confirm your name and set a password for your account. ![](https://images.contentstack.io/v3/assets/bltac01ee6daa3a1e14/blta4f6d962cb98cf40/6a2c432d41a3108063004deb/16083b57a17f79-n3RSGd.png) ## How do I file a support ticket? 1. Navigate to [support.singlestore.com](https://support.singlestore.com). 2. Click **Sign In** at the top of the page and enter your credentials. 3. After signing in, click **Submit a Support Request** at the top of the page. 4. Fill out the request form by following the guidelines in this FAQ. Also please indicate whether you are using SingleStore or are running SingleStore in a self-hosted environment. 5. After you have finished filling out the form, click **Submit**. You will see your current ticket and its replies, ticket ID for your communication with SingleStore Support, as well as the ability to add more information or additional CC email addresses. ## What does each ticket severity level mean? ## Summary This incident escalation process guides customer-reported issues from initial report to resolution. Customer-submitted issues are triaged and prioritized. Critical incidents (P1) are escalated and managed collaboratively in a dedicated communication channel. If unresolved, additional teams and management are notified. After mitigation, the Support team communicates the solution to the customer, performs a Root Cause Analysis, and implements preventive measures to avoid future issues. ## Urgency Level The urgency level defines the timeframe in which the incident must be addressed. | Urgency Level | Description | | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **U1** | **Critical**These are issues that require immediate action, often involving major system outages, security breaches, or critical business disruptions.Needs resolution immediately. | | **U2** | **High**These issues are important and require prompt attention, but not necessarily as immediately as critical issues. Examples include major product bugs or service disruptions that impact a significant number of users.Needs to be addressed within 1 business day. | | **U3** | **Medium**These issues require attention within a reasonable timeframe, such as a bug that affects a small number of users or a general service issue that doesn't require immediate action.Needs to be addressed within 5 business days. | | **U4** | **Low**These are general inquiries, minor issues, or questions that don't require immediate attention or action.Needs to be addressed within 30 business days. | ## Severity Level The severity level defines the footprint of the incident's overall severity / impact. | Severity Level | Description | | -------------- | -------------------------------------------------------------- | | **S1** | Critical production outage / emergency | | **S2** | Major impact / Cluster degradation without workaround | | **S3** | Moderate impact / Cluster largely unaffected or has workaround | | **S4** | Minimal impact / General product questions | ## Priority Level The priority level can be assessed by cross-referencing an incident's urgency level with its severity level. | **Urgency Level** | **Severity Level** | | | | | ----------------- | ------------------ | ------ | ------ | -- | | **S1** | **S2** | **S3** | **S4** | | | **U1** | P1 | P1 | P2 | P3 | | **U2** | P1 | P2 | P3 | P4 | | **U3** | P2 | P2 | P3 | P4 | | **U4** | P3 | P3 | P4 | P4 | When submitting an issue, use a priority level that best matches the scenario that you are experiencing. | **Priority Level** | **Description** | | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **P1** | **Critical**Production system outageSevere production problem preventing customer or workgroup from performing critical business functions. | | **P2** | **High**Job function impaired; no workaroundCustomer or workgroup able to perform job function, but performance of job function degraded or severely limited. Non-production environment outage. | | **P3** | **Medium**Moderate impact; with workaroundCustomer or workgroup performance or job function is largely unaffected. | | **P4** | **Low**Minimal impactMinimal system impact; includes feature requests and other non‐critical questions | ## Definitions | **Term** | **Description** | | ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Outage** | A period whenSingleStore Heliosor another customer-facing application ([singlestore.com](https://www.singlestore.com),[Forums](https://www.singlestore.com/forum), etc.) is not available and/or not operational resulting in a disruption of production service for customers orSingleStore. | | **Non-Outage** | Everything not an outage, and may include a period whenSingleStore Heliosor another customer-facing application ([singlestore.com](https://www.singlestore.com),[Forums](https://www.singlestore.com/forum), etc.) is severely degraded and/or not operating at full capacity. | | **Production System** | A live environment where systems are actively supporting business operations and serving end-users. It processes real data or transactions, meaning any failure or downtime can lead to business impact or disruption. | | **Non-Production System** | Everything not a production system. | ## What should I include in my Support ticket? 1. One of Support’s most useful tools is the SingleStore cluster report. If you are a customer running self-hosted SingleStore, generate and upload a SingleStore cluster report in your first submission to Support so that you provide Support with as much initial information as possible. For more information on how to do this, see [Generating a Cluster Report](https://docs.singlestore.com/db/v9.1/reference/troubleshooting-reference/generating-a-cluster-report.md). 2. Provide a detailed description of the issue and include all steps/actions which led you to the issue or error you have experienced. Error messages are helpful, but please also provide the actions you took when you encountered the error, if known. 3. Include screenshots if you believe they may be helpful to our support engineers. 4. Do not include passwords, login credentials or personally identifiable information. ## How do I share files with SingleStore Support? You may attach files as large as 20MB directly into the support ticket. Please upload any files larger than 20 MB to a shared folder on services such as Google Drive, OneDrive or DropBox, and share the link with the support engineering team within your support ticket. Additionally, customers may be granted FTP access to file share upon request. If this is the case, please use the credentials provided by the support engineer to upload necessary files. ## When can I expect a response to my Support ticket? Response time Service-Level Agreements (SLAs) for SingleStore Support vary based on your Support Tier and ticket severity level. Please refer to your SingleStore Agreement and our Support Terms and Conditions for details. ## Why am I not getting emails from SingleStore Support? Please ensure that the **@memsql.com** and **@singlestore.com** email domains are whitelisted as our ticketing system may use these domains for messaging. *** Modified at: February 13, 2026 Source: [/db/v9.1/support/support-faq/](https://docs.singlestore.com/db/v9.1/support/support-faq/) (An index of the documentation is available at /llms.txt)