Public status visibility for Core-Intel service availability, uptime evidence, incident history, planned maintenance and monitoring policy.
Review technical assuranceCurrent status
Operational
Last checked
Current deployment uptime
5d 16h 58m
Since Jul 12, 2026, 8:24 PM UTC
Core-Intel public pages and contact flows.
Live application health response at /api/health.
Company profile and tender due-diligence documents.
Public-sector and enterprise service information.
Availability percentages are only shown when they are backed by recorded monitoring checks. This page publishes the live health endpoint, current runtime uptime and the recorded incident and maintenance log.
Current deployment
Measured directly from the running application process and refreshed when this status page is requested. Current measured runtime is 5d 16h 58m, started Jul 12, 2026, 8:24 PM UTC.
Latest health check
The health endpoint returns service name, timestamp, runtime uptime and deployed version with no-store caching.
Published incident log
No public production incident has been recorded in the published incident history below.
No public outage, degraded-service event or data-impacting incident is currently recorded for the public website.
Monitoring continues through the health endpoint, runtime checks and manual operational review.
Scheduled before production changes
Low impact where possible
Maintenance windows should be communicated before material downtime, security updates or infrastructure changes.
As needed for urgent stability or security issues
Communicated according to severity
Critical fixes may be applied immediately, followed by incident notes and follow-up actions when relevant.
The public health endpoint reports current status, timestamp, runtime uptime and deployed version.
Production projects can include uptime checks, API checks, page checks and alerting for critical workflows.
Incidents can be logged with severity, affected services, user impact, timeline, resolution and follow-up notes.
Planned maintenance can define timing, expected impact, owner, rollback plan and communication requirements.
Monthly service reports can include uptime, incidents, maintenance, support activity and recommended improvements.