Subscription customers receive a dedicated support contact and escalation path as part of onboarding.
| Severity | Definition | First response |
|---|---|---|
| S1 | Optimization actions suspected of impacting network KPIs | 1 business day — guardrail rollback is automatic and immediate; the network never waits on support |
| S2 | E-RAN unavailable or not producing recommendations | 2 business days |
| S3 | Degraded functionality, workaround exists | 3 business days |
| S4 | Questions, feature requests | 5 business days |
Note: E-RAN failure modes are non-intrusive by design — if the platform stops, sites remain in their current or default configuration; the network keeps operating normally.
Please include: OpenShift version, E-RAN chart/app version (helm list -n humanis-eran),
the ingest mode and RAN vendor(s), and relevant pod logs
(oc logs -n humanis-eran deploy/<component>).