SLO & Availability

Enterprise procurement document — forward to IT Operations / Risk

Document
SLO-001
Version
1.0.0
Updated
9 Feb 2026
Audience
IT Operations / Risk
Status page
uptime.feedoracle.io
Contact
enterprise@feedoracle.io

Service Level Objectives

The following are operational targets (SLOs). They reflect engineering goals and observed performance, not contractual guarantees. Enterprise customers may negotiate custom SLAs with defined remedies.

MetricTargetMeasurement
API availability99.5% monthlyUptime monitor (1-min intervals)
Response time (p95)< 500msUptime monitor, measured from EU
Data freshness (on-chain)≤ 15 minutesPer-endpoint internal metric
Data freshness (risk scores)≤ 24 hoursDaily recalculation cycle
On-chain anchoring≤ 24 hoursVerifiable on Polygon / XRPL
Important: Risk scores and health signals are refreshed daily, not in real-time. Event-driven alerting is on the Enterprise roadmap.

Rate Limits

TierRequests/minBurst
Free (evaluation)1015
Developer60100
Professional300500
EnterpriseCustomCustom

Rate limit headers (X-RateLimit-Remaining, X-RateLimit-Reset) included in every response.

Maintenance Windows

TypeNoticeDurationFrequency
Planned48h via status page5–15 minMonthly target
Security patchesBest-effort< 5 minAs needed
Data source outageStatus pageVariesUncommon
Degraded mode: If an upstream source is unavailable, FeedOracle serves last-known-good values with an elevated staleness_flag.

Escalation

SeverityDescriptionResponse target
CriticalAPI unavailable, signing key compromise1 hour
HighDegraded performance, data source failure4 hours
MediumNon-critical endpoint issue1 business day
LowFeature request, cosmetic issue5 business days

Disaster Recovery

MeasureTarget
Backup frequencyDaily (automated, encrypted, EU-to-EU)
RPO≤ 24 hours
RTO≤ 4 hours (target)
FailoverManual failover to backup server (same EU region)
Negotiable SLA: Enterprise customers can negotiate contractual SLAs with defined remedies. Contact enterprise@feedoracle.io.