Website and account access
Accountable layer · RenantConfirmed issues affecting the public website, workspace previews, or access-request journey will be described as Renant service notices.
RENANTCLOUDClear updates when an issue affects customers.
This is Renant's public record for confirmed customer-impacting incidents and planned maintenance across its website, customer journeys, and coordinated services. Each notice will state the affected scope, ownership, and next update time.
No active public advisory is posted.This means Renant has not published a confirmed customer-impacting event here. It is not a blanket uptime guarantee for every provider-operated component.
How service notices are divided.
These boundaries tell customers who owns the response. They do not combine unrelated systems into one misleading platform-wide state.
Covered here
Guidance, quotes, and orders
Accountable layer · RenantCustomer-impacting interruptions in the selection, quote, checkout, or order journey will be reported with the affected step named.
Service coordination
Accountable layer · Renant with the relevant supplierWhen an order, provisioning request, billing event, or lifecycle action is affected, Renant will identify both the customer impact and the responsible layer.
Provider-hosted infrastructure
Accountable layer · Named infrastructure providerDatacenter, network, power, hardware, storage, and regional incidents remain provider-operated; Renant will relay confirmed impact and case ownership.
From first signal to a useful customer update.
Receive a signal
Observation recordedA customer report, Renant observation, provider notice, or provider case starts the record. The source and first-known time stay attached.
Verify customer impact
Scope and timing confirmedRenant separates an individual configuration problem from a wider service event and records the affected product, region, and customer journey.
Identify ownership
Responsible layer namedEach notice distinguishes Renant software and coordination from infrastructure operated by a named provider, without blurring responsibility.
Publish and resolve
Next update time statedA public notice states impact, known workaround, current owner, and the next update. Resolution includes an end time and follow-up when appropriate.
NOTICE CONTENT / 03
What every status update should make clear.
A useful service notice needs ownership, source, time, scope, and a next action—not a decorative uptime percentage.
- Timestamped observationsFirst detected, last checked, update time, and resolution time in an explicit timezone.
- Named signal sourceRenant monitor, provider status feed, provider case, or manual verification—without merging them into one claim.
- Affected ownership boundaryRenant storefront, channel layer, compute adapter, or named provider dependency.
- Impact and next actionWho is affected, what is known, the workaround if any, and who owns the next update.
Why is there no single platform-wide uptime percentage?Read methodology
Renant coordinates services across distinct ownership boundaries. A blended percentage can hide which customer journey, provider, region, or measurement source it represents. Any future uptime figure must name its scope, measurement method, and observation period.
EXPERIENCING A PROBLEM?
Report a service issue Send the details that make an issue traceable.
Include the affected service, region, approximate start time, symptoms, and any safe-to-share reference. Never send passwords, private keys, or access tokens.