Service status and incidents
Check published service health and report organization-specific impact.
The Solarius status site publishes service health, incident updates, and maintenance information. Use it when investigating an unexpected service failure.
Check an incident
Find the affected service and read the incident's latest update. Compare its impact period with the failure you observed. Record the incident reference and follow any published recovery instruction relevant to your deployment.
If the incident is resolved, retry the action that failed and inspect the product's actual result. An incident resolution notice does not by itself confirm that a previously failed customer operation completed.
Report an unlisted failure
A service can have organization-specific problems while the public status is operational. Contact support with the organization, product, region or deployment, observed failure, start time, and business impact. Include request identifiers and redacted logs when they help identify the affected operation.
For self-hosted services, compare public platform incidents with local deployment health. Use the relevant product operations guide to investigate local dependencies.
Plan around maintenance
Review the affected components, announced period, and expected impact. Share the notice with the people responsible for production changes and user communications. After the period, check service health and the business workflows that depend on it.
Use the escalation channel in your support agreement for contracted incident handling. General status notices do not replace organization-specific support cases or contractual availability reporting.