RENANTCLOUDChoose the route that matches your relationship and request. Public web forms are not emergency channels, and response commitments apply only when they are written into your service terms.
Current boundary: Public forms collect context for later review and are not emergency channels. Do not rely on them for urgent safety, law-enforcement, production-incident, or time-sensitive abuse response.
View service-status informationA project question, a customer service issue, a provider fault, and an IPv4 report need different context. Choose the closest route so the first review starts with the right information.
Describe a workload, desired region, budget, migration, or preferred configuration. This starts a conversation; it does not reserve capacity or create an order.
Public project form · response time is not guaranteedSend access, invoice, configuration, lifecycle, or service-impact context with a Renant order or service reference when available.
Renant verifies account ownership before sharing private detailsFor a Renant order, the service reference identifies the supplying provider and the correct path for compute, network, storage, facility, or address-space issues.
Provider owns the underlying fix · Renant owns the handoffProspective lessees and resource holders can describe a legitimate need, authority basis, routing model, intended term, and abuse-response capability.
No prefix, LOA, routing authorization, or lease is issued by this formFor a Renant order, Renant owns the customer-facing intake, context, and communication. The supplying provider remains responsible for its facility, network, and infrastructure.
Understand provider responsibilitiesAddress-space onboarding, an operational network report, and a security issue affecting Renant's own website have different evidence and different owners.
Use the IPv4 intake to describe the prefix size, RIR context, ASN or host relationship, intended use, region, term, and abuse-response process. Do not upload identity or registry evidence publicly.
Open IPv4 intakeIdentify the affected IP or service, timestamp and timezone, observable behavior, redacted evidence, and a safe reply route. Attribution alone is not proof that a resource belongs to Renant.
Record an abuse notice No emergency response, response time, or takedown outcome is guaranteed.Use the trust route for a responsible notice about this website or Renant's own application surface. The first message must omit credentials, exploit payloads, private keys, and customer data.
Start a responsible noticeIf there is an immediate threat to life or safety, contact the appropriate local emergency service. For abuse on infrastructure operated by another network today, contact the actual hosting provider or network owner shown in routing and registry records.
Read the IPv4 safeguards