Skip to main content

​
Live status & uptime

Current availability, 90-day uptime history, and incident post-mortems are public at status.generect.com — subscribe there for incident notifications. Contractual SLAs are available on Enterprise agreements — contact sales.

​
What to expect from each mode

  • Database (cached) operations answer from Generect’s own infrastructure — sub-second, independent of live sources.
  • Real-time operations depend on live upstream sources: latency is seconds to a minute (see recommended timeouts), and under exceptional upstream load they can return 429 — back off and retry.

​
Failure semantics

  • Errors use one JSON envelope with predictable status codes — see Errors.
  • 429 and 5xx are transient: retry with exponential backoff. Other 4xx mean the request must change.
  • Credits are reserved when a request or bulk job is accepted — a failed request is refunded automatically, and an accepted bulk job always runs to completion even if your balance later hits $0 (see Pricing).
  • Bulk jobs report error status instead of hanging; results are retained for 24 hours.