API Status All systems operational
Reliability Commitment

Service Level
Agreement

Our commitment to reliability. Contractual uptime guarantees, response time targets, and support SLAs backed by wallet credits.

99.95%
Enterprise Uptime
50ms
P50 Computation
1 hr
Critical Response
50%
Max Credit
Uptime Targets

Uptime Commitments

Each plan includes a defined uptime target. If we fall short, eligible plans receive wallet credits applied to the next billing cycle.

Plan Uptime SLA Monthly Downtime Budget Downtime Credit
Starter 99.5% ~3.6 hours None
Professional 99.9% ~43 minutes 10% of monthly cost
Business 99.9% ~43 minutes 25% of monthly cost
Enterprise 99.95% ~22 minutes 50% of monthly cost
Definitions

Downtime Definition

Counts as Downtime

  • API returns 5xx errors for more than 5 consecutive minutes
  • API response time exceeds 30 seconds for more than 5 consecutive minutes
  • Complete inability to authenticate with a valid API key

Exclusions

  • Scheduled maintenance (announced 48 hours in advance)
  • Issues caused by customer code or infrastructure
  • Force majeure events (natural disasters, etc.)
  • Rate limiting responses (HTTP 429)
  • Third-party dependency outages beyond our control
Performance

Response Time Targets

Performance targets measured at the API gateway. Actual latency may vary based on query complexity and network conditions.

Endpoint Type Target P50 Target P95
Computation (birth chart, planets, panchang) 50ms 200ms
AI Chatbot (natural language query) 3s 15s
Streaming (real-time AI response) First token: 1s Complete: 15s
Batch endpoints 500ms 2s
Support

Support Response Times

Maximum initial response time by priority level. All times refer to business-hours response unless otherwise noted. Enterprise critical support operates 24/7.

Priority Starter Professional Business Enterprise
Critical (API down) 24 hours 12 hours 4 hours 1 hour
High (degraded performance) 48 hours 24 hours 8 hours 2 hours
Normal 5 business days 3 business days 1 business day 4 hours
Low Best effort 5 business days 3 business days 1 business day
Credits

Credit Process

How downtime credits are calculated and applied to your account.

Next Billing Cycle

Credits are applied to your next billing cycle as a wallet balance addition. No cash refunds.

30-Day Window

Credit requests must be submitted within 30 days of the incident. Include the date, time, and affected endpoints.

Maximum Credit

The maximum credit for any billing period is 50% of your monthly subscription cost, regardless of total downtime.

How to Request a Credit

1

Email support@vedika.io with incident details

2

Include the affected dates, times (UTC), and endpoint paths

3

We verify against our monitoring data within 5 business days

4

Approved credits are added to your wallet balance

Transparency

Monitoring & Transparency

We continuously monitor all API endpoints and provide full transparency into platform health.

Real-Time Status

Live platform health at vedika.io/status

60-Second Checks

Uptime monitored every 60 seconds from multiple geographic regions

Incident Alerts

Opt-in email notifications for outages and degraded performance

Historical Data

Historical uptime and incident reports available on request

Maintenance

Maintenance Windows

We perform most updates with zero downtime. When maintenance is required, we follow a predictable schedule.

Scheduled

Tuesdays and Thursdays, 2:00 – 4:00 AM IST. Announced at least 48 hours in advance via the status page and opt-in email.

Emergency

Announced via the status page as soon as possible. Reserved for critical security patches or infrastructure issues that cannot wait for a scheduled window.

Zero-Downtime

The majority of updates are deployed with zero downtime using rolling deployments. No maintenance window required for routine releases.

Need a Custom SLA?

Enterprise customers can negotiate custom uptime targets, dedicated support channels, and tailored credit policies. Contact our sales team to discuss your requirements.

Last Updated: February 10, 2026