IYABOKO Science & TechnologyTechnology Infrastructure · Software + Hardware + AI + Assurance
System Status · Operational Transparency · Service Notices

Operational information should be based on verified service evidence.

System Status is the public notice point for IYABOKO digital services. It is designed to communicate confirmed availability issues, maintenance and incident impact without fabricating uptime or implying monitoring that does not exist.

Verified noticesMaintenanceIncident updatesNo fabricated uptime
Status Components

Track the services users actually depend on.

This template intentionally does not assign live status labels. Operational labels should be populated only from current verified information.

Component

Public Website

Homepage, technology pages, Domain OS, public evidence and general navigation.

Component

Member Portal

Login, registration, account, membership and entitlement-dependent access.

Component

AI Workspace

Public/member AI interfaces, workspace availability and membership-protected assistants.

Component

C3 Live Computer

Public C3 demonstrator, computational interface and selected simulation pathways.

Component

Sentinel Services

Sentinel readiness, assurance and related assessment workflows.

Component

Forms & Support

Consultation intake, contact forms, help resources and support channels.

Important: This static page does not monitor infrastructure. Do not change a component to “Operational” solely because the page itself loads.
Status Labels

Use a small set of explicit labels consistently.

Status language should describe user impact, not marketing confidence.

Operational

Available

Current verified information supports normal service availability within known limits.

Degraded

Degraded Performance

The service is accessible but a material feature, performance or reliability issue is confirmed.

Partial

Partial Outage

A defined part of the service is unavailable or materially impaired.

Major

Major Outage

Core service access is broadly unavailable or unusable.

Maintenance

Planned Maintenance

Planned work may affect availability, performance or behaviour during a defined window.

Incident Communication

A useful status notice explains impact and evidence—not just a colour.

Each incident or maintenance notice should make the affected component, impact, timing and next verified update clear.

Affected Service

Name the product, component, feature or user pathway involved.

User Impact

Explain what users may be unable to do or what behaviour is degraded.

Confirmed Timing

Publish verified start, update and resolution times where those times are actually known.

Workaround / Next Update

Provide a safe alternative only when one exists, and state when the next confirmed update is expected if known.

Do not publish “all systems operational” unless current verified checks support that statement.Operational transparency should follow the same evidence discipline used elsewhere in IYABOKO.
Closure rule: An incident should move to resolved only after the affected service has been checked and the reported user impact is no longer present. Restoration claims should be evidence-based.

Experiencing a service problem?

Check published status information first. If no relevant notice exists or the issue is account-specific, use the Help Centre or contact support.