Check the scope and age of each observation. Unknown is not operational. This page does not certify uptime or substitute for a staffed incident service.
Current observations
These checks cover only the stated scope. They do not run paid AI inference. A successful API liveness check or deployment does not prove that a customer workflow works. Missing or expired observations and failed status refreshes show Unknown.
Public assistant: Unknown
Measured scope
No current observation is available from the public assistant endpoint.
Latest observation (UTC)
Not observed
Stale threshold
No valid observation or expiry received.
AI answers: Unknown
Measured scope
No current observation is available from the public assistant endpoint.
Latest observation (UTC)
Not observed
Stale threshold
No valid observation or expiry received.
Employer pricing lookup: Unknown
Measured scope
No current observation is available from the public assistant endpoint.
Latest observation (UTC)
Not observed
Stale threshold
No valid observation or expiry received.
Assistant page links: Unknown
Measured scope
No current observation is available from the public assistant endpoint.
Latest observation (UTC)
Not observed
Stale threshold
No valid observation or expiry received.
Chat email summaries: Unknown
Measured scope
No current observation is available from the public assistant endpoint.
Latest observation (UTC)
Not observed
Stale threshold
No valid observation or expiry received.
Workflows without public measurements
Sign-in and workspace access: Unknown. No public end-to-end check or observation time is connected here.
Checkout and billing: Unknown. No public end-to-end check or observation time is connected here.
Record exports: Unknown. No public end-to-end check or observation time is connected here.
Notification delivery: Unknown. No public end-to-end check or observation time is connected here.
History and coverage
Public history policy adopted 20 October 2026. Read the owner-reviewed incident historyfor its prospective scope and selected retrospective entry. No measured uptime is established. The absence of an entry is not evidence that no incidents have occurred.
This page is served with the marketing website and is not an independent status network. If its API check fails, the page and direct contact links remain usable while observations show Unknown. A failure of the website itself may also prevent this page from loading.
Public incident history
SafeGora maintains an owner-reviewed public incident history on this page from the policy adoption date shown below. We include confirmed material production availability or data/workflow integrity disruptions, and release defects that make public terms or prices inconsistent with checkout. A deployment failure without production impact may be recorded as a release event rather than described as a customer outage.
The publication owner is Prabhakar Reddy. The owner aims to post an initial factual summary within two business days after confirming a qualifying event and checking what can safely be disclosed. While a published incident remains active, the owner records the next intended update date and posts a dated update on that date or explains the delay. These are operating aims, not guaranteed response or restoration times, and they do not establish continuous monitoring or round-the-clock staffing. Existing security, contractual and legally required notifications follow their own requirements.
Each entry records the affected scope, known event times in UTC, what users could experience, current state, evidence limits, mitigation and next action. Unknown facts remain Unknown. We correct entries through dated updates and retain their earlier factual history. We exclude credentials, private injury records, customer identifiers and exploit details that would create further risk.
This history starts prospectively when adopted. Selected older events are explicitly labeled retrospective and show their publication date separately from their event dates. The absence of an entry is not evidence that no incident occurred. This history does not calculate uptime, certify end-to-end availability, or provide an independently hosted status network.
This is a retrospective entry based on the release review dated 18 October 2026, not proof of continuous historical monitoring.
New Terms, Privacy and Refund text reached the public website before the corresponding checkout catalog activation completed. A production migration had failed; a corrective migration subsequently approved the intended catalog and closed the mismatch. The reviewed window lasted approximately 1 hour 34 minutes.
The review found zero checkout offers, acceptances and attempts across the seven production tenant records examined during that window. It did not establish that the website had no visitors or that no other activity occurred. We have no observed customer checkout impact from that review.
The rollout process allowed the website and API to proceed after the dependent migration failed. A corrective build dependency has been implemented for review so production API, app and website canaries wait for successful candidate migrations. Its deployment and traffic ordering still require verification. We will add a dated update when that verification is complete.
Report a problem or ask for status
When something looks wrong in production, email Ollie@safegora.com with the workspace, the time you first saw the issue, and what you were trying to do. Do not include credentials or private injury records. This page does not measure support acknowledgement or resolution time, and does not establish round-the-clock coverage.
What this page does not claim
A whole-product health check or complete incident coverage before policy adoption.
A public monthly uptime percentage or service-credit schedule.
SOC 2 certified, ISO certified, VPAT complete, or trust center complete.
An independently hosted status network or a verified on-call commitment.