Service Level Targets
What this page is for
This page publishes the service-level targets Oxford Ledge holds itself to. They are targets, not contractual guarantees — the legal terms live in the Terms of Service. Targets are useful because they tell you what to expect on a normal day, what counts as a degraded day, and what we owe you when we miss.
If you operate on Oxford Ledge data and need an SLA stronger than what’s here, email support@oxfordledge.com and we’ll talk. We won’t over-promise on this page to avoid that conversation.
1. Uptime targets
| Surface | Target | Measured how |
|---|---|---|
| SSR landing pages (/, /stocks/, /bdcs/, /learn/, /glossary/) | 99.9% monthly | Cloudflare edge availability + Render web-service health |
| JSON API (/api/*) | 99.5% monthly | Synthetic probe on /api/health/deep every 5 min |
| WebSocket feed (real-time prices) | 99.0% monthly | Client reconnect rate; degraded if median session disconnects > 3×/hr |
| Background data jobs (cron freshness) | Best-effort | Per-job heartbeat; see § 2 for dataset targets |
An hour of unavailability on /api/* in a 30-day month is roughly 99.86% — comfortably above the 99.5% target. A four-hour outage in a month would breach. We track via the deep health probe and surface incidents on the Trust Dossier’s drift-catches log.
2. Data freshness targets
| Dataset | Source | Freshness target |
|---|---|---|
| Insider transactions (Form 4) | SEC EDGAR | Within 4 hours of EDGAR drop |
| Institutional holdings (13F) | SEC EDGAR | Within 1 business day of filing |
| Macro series (rates, inflation, unemployment) | FRED | Within 1 hour of FRED publish |
| Treasury yield curve | treasury.gov | Same business day, by 18:00 ET |
| FINRA TRACE bond prints | FINRA Data API | T+1 by 09:00 ET (when API access is provisioned) |
| Company fundamentals | Financial Modeling Prep | Within 1 business day of vendor publish |
| End-of-day equity prices | FMP / SEC for missing | Within 1 hour of NYSE/Nasdaq close |
| Intraday equity prices (Researcher+) | FMP | 15-minute delayed (free tier); near-real-time on the relevant tier |
| BDC portfolio holdings (Schedule of Investments) | SEC EDGAR via parser | Within 2 business days of 10-Q / 10-K filing |
| LEARN content with REFRESH_BY markers | internal | Reviewed at or before the marker date; CI fails if past due |
Freshness against these targets is auditable on the Trust Dossier and through the X-Data-Age response header on every /api/data call.
3. Incident communication
Active incidents that affect the API or SSR pages are posted on our status surface within 30 minutes of detection. Subscribed users (Researcher tier and above) receive a follow-up email digest after the incident is resolved with the root cause and the remediation.
If an incident’s root cause is something a careful reader should know about — a parser silently rejecting a class of filings, a data vendor changing a field name, a cron job missing a window — we add it to the drift-catches log on the Trust Dossier. The 57-entry baseline at launch covers all of 2026; new entries land within a week of the incident.
4. When we miss
If we breach a target in a given month and the breach materially affected your use of the platform, contact support@oxfordledge.com. Our default remediation is a credit equivalent to the affected days’ share of your subscription. The exact remedy is at our discretion and is laid out in the Terms of Service; this page describes the intent.
What we don’t do: silently absorb a breach without acknowledging it. If you spot one we missed, please tell us.
5. Scope
These targets cover the platform we operate. They do not cover:
- The underlying data vendors (FMP, FINRA, Tradier when active). When a vendor has an incident we surface it as a freshness-degraded chip; we don’t assume liability for vendor uptime.
- Third-party authentication providers (Google, GitHub) during their own outages.
- Any user-supplied AI provider API key (when you bring-your-own to Ask AI). Anthropic, OpenAI, and Google’s service levels apply to those calls.
Contact
Support: support@oxfordledge.com · Active incidents: see the banner on Trust Dossier · This page is subject to and should be read alongside our Terms of Service.