For incidents and real-time service information, check status.blockdb.io. For access, billing, or technical issues email [email protected].
Ticket Content Guidelines
Include the following details to help BlockDB engineers diagnose quickly and accurately:Issue Description
Explain what you were doing when the issue occurred and how to reproduce it. Include the affected dataset(s) or endpoint(s) — for example:
POST /evm/logs, dataset: 0103_logs.Error Messages
Paste exact errors from responses, logs, or UI. Include HTTP status, error codes, and any response values if present.
Timing Information
Provide the time window (with timezone) when the issue occurred. Example:
2025-11-11 14:15-14:20 UTC.User Impact
Clarify scope: single user, team, or production pipeline. Note whether it’s blocking or degraded.
Document Reference
Link to the relevant docs page or object identifiers (addresses, pool UIDs, tx hashes) that illustrate the problem.
Visual Evidence
Add screenshots or short screen recordings showing the failure and settings used.
cURL
Understanding Priority Levels
Select the appropriate priority so we can triage effectively:Low Priority
Low Priority
Non-critical, no impact on daily work.
- General questions
- Feature requests
- Future roadmap inquiries
Normal Priority
Normal Priority
Partial impact or inconvenience.
- Minor bugs
- Intermittent issues
- Workarounds available
High Priority
High Priority
Significant impact on usage or timelines.
- Production job degradation
- Critical queries failing for a subset of inputs
- No viable workaround
Urgent Priority
Urgent Priority
Immediate, business-critical impact.
- Outage or complete stop of production workloads
- Data corruption risk
- Security concerns
Accurate priority helps the team triage efficiently. Over-escalation may delay truly critical responses across the queue.