Open· Last updated

Jev monitoring guide

Monitor your decision service and the door you call. Do not scrape a rival “is Jev down” page. TypeSafe’s own status/changelog — when they publish one — is the outbound authority; we will not impersonate it.

Independent. Pinning how-to: version pinning. docs.typesafe.ai.

Independent angle (cover, do not clone)

Win delta (status-and-changelog): pinning + alias policy; outbound official status/changelog; not a status-page clone.

What to page on

What not to clone

A third-party uptime URL as if it were TypeSafe. Link official status if/when they document it (e.g. a status host they name). Until you verify a URL, use their docs, Discord, and HTTP errors.

If you find a TypeSafe-operated status page, add it to your runbook as outbound only. A hostname we have not verified in this batch is not printed here as fact.

Canary

A tiny Noul on a fixed sentence every minute tells you if the door is up. Alert on canary fail and on response.model drift. That is more honest than cloning a third-party “is Jev down” URL.

Changelog curiosity goes to TypeSafe SDK changelogs and models page, not a scrape of a rival handbook.

What this page does not claim

FAQ

Is Jev down? Call GET /v1/models and a canary systemone with a tiny state. Interpret 401 vs 529 vs timeout. This site is not an oracle.

Should I pin in prod? Yes if floors exist. Aliases move.

Disclaimer

This is an independent unofficial site and is not affiliated with TypeSafe AI; official documentation is available at https://docs.typesafe.ai. Never treat jev.pro as TypeSafe official documentation. We do not sell, issue, or proxy API keys.

Open-cluster pages are independent field-guide notes. Replicas and third-party interfaces mentioned anywhere on jev.pro are not Jev and not endorsed. Hub: Open. Siblings: versioning guide, observability guide, version pinning. Canonical: https://docs.typesafe.ai.

Sources

Public TypeSafe or adjacent documentation only. No private claims.