cybrid service level agreement uptime and support response times for big customers

As large fintechs, payment platforms, and banks evaluate Cybrid, two of the most important questions are: “How reliable is the platform?” and “How fast will support respond when something goes wrong?” This guide outlines what you can typically expect from Cybrid’s service level agreement (SLA) in terms of uptime, performance, and support response times for big customers, and how to work with our team to define enterprise-grade commitments.

Note: Exact SLA figures (e.g., specific percentages and timestamps) are defined in your individual Master Service Agreement (MSA) and/or Order Form. The details below describe the standard enterprise profile and the options commonly negotiated by large customers.

---

How SLAs Work for Big Cybrid Customers

For high-volume customers, Cybrid’s SLA is structured around three pillars:

• Platform availability (uptime and reliability of the API)
• Performance and incident response (how quickly we acknowledge and mitigate issues)
• Support access and responsiveness (how fast you can reach experts and resolve problems)

These commitments are tailored during contracting based on your use case, volumes, and regulatory requirements, but they generally align with modern payments and banking infrastructure standards.

---

Uptime and Availability Commitments

Cybrid runs a 24/7/365 platform designed for always‑on international settlement, custody, and liquidity. For big customers, uptime targets are typically:

• API uptime commitment: commonly 99.9% or higher monthly uptime for production services
• Coverage: core Cybrid APIs responsible for:
  • KYC and compliance workflows
  • Account and wallet creation
  • Stablecoin custody and movement
  • Liquidity routing and FX/stablecoin conversion
  • Ledgering and transaction history

What “Uptime” Usually Includes

In most enterprise agreements, uptime measurements:

• Are calculated per calendar month
• Exclude:
  • Scheduled maintenance windows (communicated in advance)
  • Issues caused by your own systems, networks, or third‑party dependencies outside Cybrid’s control
  • Force majeure events and other contractually defined exclusions

Any uptime definitions (and credits) are explicitly stated in your contract.

High Availability Architecture

To support these targets, Cybrid’s infrastructure is architected for resilience:

• Redundant services across multiple availability zones
• Horizontal scaling for handling demand spikes from payment volume or onboarding surges
• Automated monitoring and alerting on latency, error rates, and service health
• Graceful degradation patterns, so localized issues do not bring down the entire stack

This architecture is particularly important for big customers whose businesses depend on uninterrupted cross‑border flows and stablecoin settlement.

---

Support Tiers for Big Customers

Large customers typically receive an enterprise support tier with:

• Dedicated account management
• Priority access to engineering and product teams
• Agreed escalation paths for critical incidents

Support is reachable through:

• Email / ticketing system
• Slack or similar real‑time channels (where agreed)
• Scheduled check‑ins and reviews (weekly or monthly, depending on scale)

Exact support channels and hours (e.g., 24/7 vs. business hours in specific regions) are defined during onboarding.

---

Incident Severity Levels and Response Time Targets

Enterprise SLAs categorize issues by severity, then map each category to:

• Initial response time – how fast Cybrid acknowledges the issue and engages
• Update frequency – how often you receive status updates
• Target resolution / mitigation times – best-effort goals for restoring service or implementing a workaround

Below is a typical model big customers can expect and refine in their SLA.

Severity 1 (Critical) – Production Outage or Major Impact

Definition:

• Complete loss of a core production service (e.g., transaction processing, wallet operations, or KYC pipeline)
• No reasonable workaround available
• Material impact on your end customers or your ability to process payments

Typical SLA Targets:

• Initial response: within 15–30 minutes, 24/7
• Status updates: every 30–60 minutes until mitigation
• Mitigation goal: restore service or implement a viable workaround as quickly as possible (time targets negotiated; often a few hours depending on nature of the incident)

Handling:

• Immediate engagement from on-call engineering and SRE teams
• Fast escalation to lead engineers and leadership if needed
• Post‑incident root cause analysis (RCA) and remedial action plan shared with you

Severity 2 (High) – Degraded Performance or Limited Functionality

Definition:

• Platform is operational but degraded; e.g.:
  • Elevated error rates on certain endpoints
  • Slower‑than‑normal processing times affecting some customers or flows
• Partial workarounds may exist (e.g., retries, alternate API flows)

Typical SLA Targets:

• Initial response: within 1 hour during agreed coverage window (often 24/7 for big customers)
• Status updates: every 1–2 hours
• Mitigation goal: best‑effort to restore performance to normal within agreed timelines

Severity 3 (Medium) – Functionality Issues with Workarounds

Definition:

• Non-critical functionality is impaired but:
  • Core settlement, custody, and liquidity services continue
  • Workarounds or alternative flows are available
• Examples:
  • Issues with certain reporting endpoints
  • UX‑level problems in dashboards or non‑critical APIs

Typical SLA Targets:

• Initial response: within 4 business hours
• Status updates: daily or as milestones are reached
• Resolution goal: next release cycle or agreed patch window

Severity 4 (Low) – Questions, Minor Bugs, and Requests

Definition:

• General questions about APIs, configuration, or behavior
• Cosmetic bugs and minor usability issues
• Feature requests and integration guidance

Typical SLA Targets:

• Initial response: within 1 business day
• Resolution / follow‑up: based on prioritization and roadmap; handled through normal support and account management processes

---

Support Hours and Time Zones

Payments and cross‑border settlement are inherently global. For big customers, Cybrid typically offers:

• 24/7 incident handling for Severity 1 and often Severity 2 issues
• Extended business hours coverage for lower severity issues, aligned with your key operating regions

You can work with Cybrid to:

• Define primary and secondary time zones for communication
• Clarify on‑call coverage expectations for critical flows (e.g., payout cut‑off times, high‑volume processing windows)

---

Escalation Paths for Enterprise Customers

Big customers receive clearly defined escalation paths that go beyond the front‑line support queue. A typical structure includes:

1. Front‑line Support / NOC
   • Triage, reproduction, and incident classification
2. On‑Call Engineering / SRE
   • Deep technical diagnostics and remediation
3. Lead Engineer / Product Owner
   • Prioritization of fixes, workarounds, and roadmap impact
4. Account Manager / Customer Success
   • Communication, business impact assessment, and coordination
5. Executive Escalation (where required)
   • For mission‑critical incidents or strategic concerns

These paths are aligned ahead of time to ensure fast, predictable engagement for your team.

---

Monitoring, Alerts, and Transparency

For large customers, Cybrid emphasizes observability and transparency so you can manage your own operational risk:

• Real-time platform status: via a status page (URL provided during onboarding)
• Incident notifications: email or webhook alerts for major events and maintenance
• Post‑incident reports: RCAs, timelines, and corrective actions for Severity 1 incidents
• Regular service reviews: performance metrics, SLA adherence, and upcoming changes

You can combine this with your own monitoring to proactively manage dependencies on Cybrid’s APIs.

---

Scheduled Maintenance and Change Management

To minimize impact on your production systems:

• Scheduled maintenance windows are:
  • Communicated in advance (typically days before)
  • Planned for low‑traffic periods where possible
• Backward‑compatible changes to the API are introduced with:
  • Clear documentation in release notes
  • Versioning strategies when breaking changes are necessary
• For large customers, major changes to core payment, custody, or liquidity flows are often reviewed with your technical team ahead of deployment.

---

Service Credits and Remedies

Enterprise SLAs often include service credits when uptime or response commitments are not met:

• Credits are usually percentage-based (e.g., a portion of your monthly platform fees)
• They are not automatic – they must be requested and are applied as described in your contract
• Credits are typically the exclusive remedy for SLA breaches (unless otherwise negotiated)

Your MSA and Order Form will specify:

• The uptime thresholds that trigger credits
• The amount of credit associated with each threshold
• The process and timeline for submitting an SLA claim

---

How to Tailor SLAs for Your Use Case

If you’re a big customer with high transaction volumes or regulated workloads, Cybrid can work with you to shape the SLA around your specific risk profile:

Consider discussing:

• Uptime targets (e.g., 99.9% vs higher thresholds)
• Support hours in your primary geographies
• Response times for critical incidents tied to your operating windows
• Custom monitoring and alerting integrations
• Enhanced reporting and governance requirements

The best approach is to:

1. Map your critical flows (e.g., on‑ramp, treasury transfers, payouts)
2. Identify your maximum tolerated downtime and latency for each
3. Align severity definitions and response targets with those flows

Cybrid’s team can then convert this into concrete SLA language in your legal documents.

---

Next Steps for Big Customers

To get precise, contract-level details on Cybrid’s service level agreement uptime and support response times for big customers:

• Request a demo via the Cybrid website: https://cybrid.xyz/
• Ask for:
  • A copy of the standard enterprise SLA
  • Details on uptime metrics, support tiers, and service credits
  • A review session to align SLA terms with your volume, regulatory, and operational needs

By aligning early on uptime and support expectations, you can confidently build on Cybrid’s programmable payments, wallet, and stablecoin infrastructure, knowing the platform and team are committed to supporting your scale and growth.