Skip to main content
LARUS
Discuss your IPv4 needs
Explore

LARUS Support Center

Get your request to the team that owns it.

Choose the operational route, include the facts that matter, and create one trackable LARUS support request.

Find the right route

Seven specialist queues. Clear ownership from the start.

Use the routing guide before you submit. Direct email remains available when your own workflow requires it.

01

Customer and technical operations

Existing accounts, service use and live network operation.

  • Customer ServiceAccount, order, product information and general customer questions.cs@larus.help
  • Technical SupportProduct configuration, service behaviour and technical troubleshooting.support@larus.help
  • Network Operations CenterRouting, reachability, network incidents and outage investigation.noc@larus.help
02

Trust and official requests

Evidence-led abuse reports and requests from law enforcement authorities.

  • Abuse ReportingReports of abusive activity involving LARUS-operated address resources.abuse@larus.help
  • Law Enforcement InquiriesOfficial requests from identifiable law enforcement authorities.lawenforcement@larus.help
03

Commercial and IPv4 supply

New buying requirements and IPv4 portfolios offered to LARUS.

  • SalesIPv4 availability, commercial options, pricing and new purchase decisions.sales@larus.help
  • IPv4 SourcingIPv4 portfolios, direct sale and potential sell-and-leaseback discussions.sourcing@larus.help

Make the first reply useful

Bring the facts that move the work forward.

The right evidence reduces clarification loops and helps the receiving team begin with the actual issue.

  1. 01

    Identify the service

    Add the account, company, order, lease or existing ticket reference that anchors the request.

  2. 02

    Bound the impact

    For technical cases, provide prefixes, ASN, systems, locations and exact UTC times.

  3. 03

    Attach the evidence in context

    Describe what happened, what you expected, what changed and which records support the report.

Create a support ticket

Route once. Explain clearly. Keep one reference.

Select the responsible team first. The form will show the details that help that team start work.

All marked fields are required. Do not submit passwords, private keys or authentication tokens.

Responsible team *

Customer and technical operations

Trust and official requests

Commercial and IPv4 supply

Slide right to verify.