Viper Scheduling Screens Unavailable Across Multiple Plants

Løst 5. Mar 2026 kl. 07:45 EST

Incident Resolved: CTIM-2398
Support Teams have contained or resolved the issue. Please contact MIS PBM or see ticket for more details.

Opdateret 5. Mar 2026 kl. 07:41 EST

UPDATE:

Team has reverted a recent TLS version change and we are seeing positive responses that services are returning to normal. Next update when all plants have confirmed or in max 30 minutes.

Opdateret 5. Mar 2026 kl. 07:28 EST

UPDATE:

Teams are actively investigating this unknown Authorization issue with high priority. Next update when we get more information or max in 30 minutes.

Opdateret 5. Mar 2026 kl. 06:56 EST

UPDATE:
Escalation sent to: Access Domain

Requesting Access team to help investigate this further. Next update in max 30 minutes

Opdateret 5. Mar 2026 kl. 06:40 EST

UPDATE:
Escalation sent to: Vista: Networking

The team tried restarting the service after the child token rotation but is still facing the issue. They are actively working to resolve it. Adding another team to help investigate. Next update in max 30 minutes

Opdateret 5. Mar 2026 kl. 06:05 EST

UPDATE:

Team is rotating the child Akeyless tokens and no ETA has been shared yet. Next update will be in max 30 minutes.

Opdateret 5. Mar 2026 kl. 05:37 EST

UPDATE:

Team is still investigating the issue with high priority. Adding additional members to help the investigation. Next update in max 30 minutes.

Opdateret 5. Mar 2026 kl. 05:13 EST

UPDATE:
Escalation sent to: Fulfillment: Infrastructure Dev Ops (UFI)

Adding additional team to investigate this viper scheduling screen error issue.

Opdateret 5. Mar 2026 kl. 05:04 EST

UPDATE:

The relevant team is online and is actively looking into the issue with high priority. Next update in max 30 minutes.

Undersøgelse 5. Mar 2026 kl. 05:01 EST

New Incident: CTIM-2398
Plant: ALL PLANTS (Viper)
Priority: Critical
Escalation sent to: Fulfillment: Infrastructure Database (Muninn) for review.
Multiple users reported errors while accessing Viper, including failures to load scheduling and other screens. Users are encountering system errors related to SSL/TLS secure channel creation, which is preventing Viper from retrieving required settings and loading screens. As a result, production scheduling activities are currently impacted. Requesting team to investigate potential issues related to connectivity, authentication, or infrastructure dependencies.