IPV4 EXCHANGE · CONTROLLED ONBOARDING

Address space needs more than a checkout button.

Renant's workflow brings resource holders and users through authority, routing, reputation, and return checks before an address can be announced.

Explore the workflow Discuss a prefix
SIGNAL PREVIEWPrefix postureILLUSTRATION
DOCUMENTATION ASNAS64512EXAMPLE
RPKI STATENot applicableCHECK
REPUTATIONNot evaluatedWAIT
LEASE EXPIRYNot active
When enabled for an active lease, signals can include BGP origin, RPKI, RDAP, blocklist changes, abuse cases, and expiry. Renant does not inspect packet contents by default.
01

Authority first

A seller must prove the right to lease the exact prefix. Subleasing is never assumed.

02

LOA with context

Holder, lessee, prefix, announcer, ASN, dates, and revocation terms are verified before issuance.

03

Monitor signals

Watch routing and reputation evidence without default inspection of customer traffic contents.

04

Human review

Alerts create a case. A single blocklist signal does not automatically suspend a legitimate user.

VERIFICATION WORKFLOW

Choose a side of the exchange.

DOCUMENTATION PREFIXTERMROUTINGSTATUS
192.0.2.0/24Documentation range · never routable3–12 monthsBring your ASNExample only
198.51.100.0/24Documentation range · never routable6–24 monthsManaged announcementExample only
203.0.113.0/24Documentation range · never routable12 monthsBYOIP reviewExample only

These RFC documentation ranges demonstrate the interface only. They are not inventory and cannot be leased or routed.

LOA PREVIEW

See what verification requires.

LEASE SAFEGUARDS / 05

Required before any address-space lease.

01 Buyer and seller KYB

02 Prefix authority evidence

03 Signed lease and acceptable-use terms

04 Valid LOA / ROA / routing plan

05 Monitoring and abuse escalation

06 Renewal, revocation, and return workflow

Availability begins only after a real prefix and both parties pass verification. This page does not offer routable inventory or issue an LOA.