Everything operational. And you can check it, not just take our word.
This page isn't a green banner: on load, your browser tests the site's components and shows the result. For anything that depends on third parties, we point straight to their own status page. Managed services for clients have their own status channel, per contract.
- Site…okamiops.com · checking now
- Agent layer…llms.txt · sitemap · 4 JSON feeds
- Open incidents0none recorded since launch
- Checked at…your device's clock · reload to check again
Six components, each checked its own way.
What's ours, your browser tests right now. What's a third party's, we link to the official source: we'd rather you see Cloudflare's status on Cloudflare than take our word for it.
- operational
- Your browser made a request to the component just now and got a 200 response. The time shown is measured by your device.
- degraded
- It responded, but slowly (over 2 s) or with an error on part of the feeds.
- down
- No response, or a 5xx error. If you see this and this page loaded, the problem is partial — let us know.
- third-party status
- We don't test this for you; the link goes to the provider's own status page.
Static, at the edge, no database: little that can go down.
The site is prerendered at build time and served over Cloudflare's global network. There's no application server, no database and no session. Only four dependencies can affect you, and all of them have a public status page.
Cloudflare: serves the pages, the feeds and the forms from hundreds of points of presence. If it goes down, the whole site goes down.
cloudflarestatus.comResend: delivers the contact, waitlist and Baseline messages. If it goes down, the form warns you and direct email still works.
resend-status.comGitHub: hosts the products' repositories and releases. Doesn't affect the site, affects anyone wanting to clone or download.
githubstatus.comApple: distributes Okami Tally. Doesn't affect the app once installed, which has no backend.
developer.apple.com/system-statusVerified build
Every deploy goes through build, tests and a check that verifies the 87 pages, the feeds, llms.txt and the sitemap before going live. A broken deploy doesn't publish.
No window
Deploys are atomic and never bring the site down. If a maintenance window with impact is ever needed, it will show here in advance.
Status by contract
Gateway, monitor and infrastructure we operate for clients have their own SLA, incident channel and status, defined by contract. This page covers okamiops.com only.
When something goes down, you read here what broke, why and what changed.
Every incident logs a start, an end, a cause and a fix. Blameless post-mortems, the same standard we ask of our clients.
- Sep 2026Site v3 live: new design, agent layer, status page with in-browser verification.
- Jun 2026Migrated to Cloudflare Workers with automatic deploy from the repository.
- since thenNo incident with impact recorded.
Detection
Worker observability is on, with alerts for 5xx errors. You can also let us know: an email with the URL and time is enough.
Communication
Incidents with impact go on this page while they're open. Affected clients are notified through their contract's channel.
Post-mortem
Cause, timeline and corrective action published here within 5 business days of the incident ending.
Security
An incident involving personal data follows the privacy policy: notice to data subjects and the authority within the legal deadlines.
Saw something down?
Send the URL, the time and what appeared on screen. If it's a security issue, use the disclosure channel instead.