Service Level Agreements & Support

Uptime objectives

Reliability grounded in AWS RDS Multi-AZ and redundant compute clusters.

BlackShield is delivered as a highly available SaaS platform. We use AWS managed services with Multi-AZ configurations to ensure your security findings and compliance data are always accessible. Our 10x increased SLA targets reflect the underlying resilience of our cloud-native architecture.

生效日期

March 18, 2026

最近更新

May 31, 2026

Support Response Targets

Our support tiers are defined by the severity of the incident. P1 issues trigger immediate internal escalation and 24/7 coverage.

Severity	Priority	Response Target	Hours	Typical Coverage
P1	Critical	15 Minutes	24/7	Full Platform Outage or Critical Breach
P2	High	1 Hour	Business Hours	Core Feature Degraded or Ingestion Halted
P3	Normal	1 Business Day	Business Hours	Minor Bugs or Config Issues
P4	Low	2 Business Days	Business Hours	General Questions or Feature Requests

Service Availability & Uptime Guarantee

We guarantee the availability of the BlackShield platform through redundant architecture across multiple availability zones. Uptime is calculated monthly, excluding planned maintenance windows.

Enterprise Tier: 99.99% Guaranteed Monthly Uptime.

Professional/Shared Tier: 99.95% Guaranteed Monthly Uptime.

Planned Maintenance: Announced at least 48 hours in advance via the status page and email.

Exclusions: Downtime caused by customer-managed network configurations, misconfigured API keys, or third-party cloud provider outages (e.g., AWS Region failures) are excluded from the SLA calculation.

SLA Credits

If we fail to meet our availability guarantee in a given billing month, eligible customers may request a service credit applied to their next invoice.

99.9% to < 99.99% (Enterprise): 10% Service Credit.

99.0% to < 99.9%: 20% Service Credit.

< 99.0%: 50% Service Credit.

Credit requests must be submitted to our support team within 30 days of the end of the impacted month.

Support Response Target SLAs

Our global support team provides guaranteed response times based on incident severity. P1 incidents receive 24/7 attention until mitigation is achieved.

P1 (Critical): Total platform outage or critical security breach. Initial response: 15 minutes (24/7/365).

P2 (High): Major feature degraded, ingestion halted, or significant performance impact. Initial response: 1 hour (business hours).

P3 (Normal): Minor bugs, dashboard UI issues, or general configuration inquiries. Initial response: 1 business day.

P4 (Low): Feature requests and general feedback. Initial response: 2 business days.

Escalation & Incident Management

All P1 and P2 incidents follow a strict internal escalation path to engineering leadership. Customers receive continuous updates throughout the incident lifecycle.

Status Page: Real-time updates posted immediately upon P1/P2 detection.

Continuous Updates: For P1 incidents, updates are provided every 30 minutes until resolution.

Root Cause Analysis (RCA): A detailed technical RCA report is provided within 5 business days of incident resolution.

Escalation Path: Tickets breaching response SLAs are automatically paged to the Director of Engineering.