Support
Support channels, status pages, ticket contents, maintenance notices and refunds.
Status pages
- RPC Status: node health, current slot and scheduled downtime for every region.
- Benchmarks: live latency, transaction landing times and gRPC results.
If one region has a problem, clients can move to another region. See Endpoints.
Contact channels
| Channel | Suits |
|---|---|
| Discord: open a ticket | Technical questions, outages, account and payment problems, suggestions |
| Contact form | General questions by email |
support@constant-k.com | Refund requests and billing questions |
What to include in a ticket
- The product and the region you use, for example "Kaldera, EU region".
- The time, in UTC, and how long the problem lasted.
- What you sent: the method or the gRPC filter, with its parameters.
- What you got back: the full error message, HTTP status or gRPC status code.
- Signatures or slots for any transaction or block involved.
- Your client and version, for example
@solana/kit8.3.0 oryellowstone-grpc-client15.0.0.
A crypto payment that did not activate a plan also needs the transaction signature.
A full API key in a ticket is exposed
Discord tickets and emails can be seen by more than one person. An account email, or the last 4 characters of the key, identifies the account; the whole key never has to appear. A key shared by mistake is replaced by a re-roll on the My Account page.
Planned maintenance
constant-k announces scheduled downtime at least 24 hours in advance, through website banners, email or Discord. RPC Status also lists it.
Refunds
Refund requests go to support@constant-k.com. The Terms of Service explain when refunds apply.