Status

Service status

Live checks against every public Oprex service, run the moment you loaded this page.

All systems operational

Checked 2026-08-06 05:27 UTC · this page probes each service when you load it

APIREST API at api.oprex.id — every lifecycle object
96 ms Operational
MCP EndpointModel Context Protocol for coding agents
90 ms Operational
Memory & Lifecycle DataRequirements, tests, releases, bugs, notes, memory
94 ms Operational
Web Appmember.oprex.id — the workspace UI
162 ms Operational
Websiteoprex.id — marketing and documentation
94 ms Operational
Support Portalsupport.oprex.id — tickets and knowledge base
110 ms Operational
Communitycommunity.oprex.id — public discussion
251 ms Operational

What these mean

Operational

The service answered within two seconds.

Degraded

It answered, but slowly. Usually load on the shared host — things work, they just feel heavy.

Down

No answer within four seconds, or an error response. If you see this and we have not said anything, tell us.

Why there is no uptime percentage here

Because we do not yet store the history that would make one true. Publishing "99.9%" without the measurements behind it would make this page decoration rather than information — and a status page exists precisely for the moment when you need to trust something.

Historical uptime, incident timelines, and subscribable notifications are planned. Until they exist, this page tells you what is true right now, and the changelog records what changed.

Reporting a problem

If something is broken for you but green here, that is worth knowing — it usually means the problem is regional, account-specific, or in a code path this page does not probe.

Open a ticket Ask the community

Scheduled maintenance

Oprex is in beta and deploys continuously; individual services may restart briefly during a release. Anything longer or riskier than that is announced in the community ahead of time.