Operational availability, incidents, maintenance, infrastructure health, AI service health, and service-dependency visibility for SHILP.ai.
Each service reports one of five clear states: Operational, Degraded Performance, Partial Outage, Major Outage, or Maintenance.
Coverage: SHILP.ai status reporting includes core platform access, workforce applications, candidate and employee experiences, APIs and integrations, notifications, file/document services, and customer-visible AI & Intelligence Services.
AI service status communicates operational availability and service health. It does not, by itself, represent the accuracy, suitability, fairness, legal compliance, or outcome quality of any specific AI-assisted result.
SHILP.ai AI-assisted capabilities are intended to support configured workflows and human decision-making. Employment, workforce, learning, or other consequential decisions should remain subject to applicable organizational policies, human review, and legal requirements.
An AI service may be technically available while a specific feature is limited, restricted, or unavailable for governance, quality, tenant-policy, regional, or safety reasons. When appropriate, SHILP.ai may temporarily restrict an AI-assisted capability while other platform services remain available.
Incident updates should communicate user impact and recovery progress without exposing sensitive internal engineering details.
Historical incident reporting will be available here as the public status service expands.
These metrics should be populated from real monitoring systems—not manually estimated and not replaced by marketing performance scores.
Cloudflare/CDN edge delivery and DNS resolution independent of application origin.
Governance logs, trace storage, database read/write health, and persistence services.
Aggregate user-experience and service-latency signals such as P95/P99 where measured.
External dependencies such as email gateways, identity providers, and approved third-party APIs.
Status-update delivery channels including email, SMS, RSS, Slack, or webhook integrations where enabled.
Historical availability will be published only from authoritative monitoring. SHILP.ai will not display placeholder uptime percentages or implied SLA performance before verified data is available.
Enterprise administrators and users should be able to receive incident and maintenance notifications through channels supported by the production status platform.
status.shilp.ai answers: “Is SHILP.ai working right now?”
Product Status / Roadmap answers: “What products or capabilities are Live, Beta, Planned, or regionally available?”
These should remain separate experiences so enterprise users do not confuse an operational incident with product availability or roadmap timing.
Contact SHILP.ai Support and include the service affected, your organization if applicable, approximate time, browser/device, and the exact error message. For AI-assisted services, identify the affected capability without including confidential prompts, candidate/employee data, or other sensitive content. Do not send passwords, MFA codes, or regulated personal information.
Use this page to determine whether SHILP.ai is experiencing a broader service issue. If relevant services are operational, the issue may instead involve your account, tenant, SSO, MFA, role, or product access.
If Authentication & Sign-In, Candidate Portal, Employee / Contractor Access, Enterprise Workspace, or another related service is degraded or unavailable, follow the incident updates published on this page.
If the relevant services are operational, use SHILP.ai Sign-In Help or Contact Support for password, SSO, MFA, tenant, role, permission, or entitlement assistance.
