Read service status information

Purpose and scope

Interpret live indicators, planned maintenance notices and incident updates without confusing a marketing badge with a service guarantee.

Use this guide as orientation, then rely on the signed agreement, current policy or named support response where those sources set a more specific obligation.

Prepare the right information

• The product and region being checked.
• Current status or maintenance notice.
• Your observed impact and time.

Follow the controlled process

1. Frame the needState the desired outcome, affected product and accountable contact. For read service status information, avoid assumptions that have not been confirmed in writing.
2. Review and decideUse the current governed source, record material questions and obtain approval from the person who owns the decision.
3. Retain evidenceKeep the final reference, date, decision and any follow-up action together so a later reviewer can reconstruct what happened.

Expected record

• A current service interpretation.
• A decision to wait, retry or raise a case.
• A retained status reference.

Security and disclosure boundary

• Never send passwords, authentication codes, private keys or recovery codes to Obedience staff.
• Share the minimum customer, project and commercial information needed for the stated purpose.
• Public documentation explains controls and responsibilities without publishing exploitable topology, credentials or confidential implementation detail.