Common Inter-RIR Transfer Rejections

Inter-RIR transfer rejections can be frustrating and costly, causing delays of weeks or months and potentially derailing IPv4 acquisition plans. Understanding the most common rejection reasons and how to avoid them is essential for successful transfers. This comprehensive guide covers why transfers get rejected and how to prevent or remedy these issues.

Overview of Transfer Rejections

Inter-RIR transfers can be rejected at multiple stages by either the source or destination RIR, or fail due to policy incompatibility issues.

Rejection stages:

• Source RIR initial review
• Destination RIR eligibility verification
• Needs assessment evaluation
• Policy compatibility verification
• Final approval stage

Types of rejections:

• Hard rejections: Fundamental issues requiring significant changes
• Soft rejections: Documentation or clarification issues, easily remedied
• Conditional approvals: Approved for different amount or terms

Impact of rejection:

• Timeline delay: 1-4 weeks minimum
• Additional costs: Documentation, legal review, consultant fees
• Potential deal loss: Seller may move to other buyer
• Reputational impact: Multiple rejections may trigger additional scrutiny

For background on the complete inter-RIR transfer process, see our Inter-RIR Transfer Process Explained guide.

Category 1: Hold Period and Eligibility Rejections

The most common hard rejection category involves resources not meeting minimum hold period requirements.

Rejection 1: Hold Period Not Met

Problem: Attempting to transfer resources before the required hold period has elapsed.

Why it happens:

• Seller miscalculated the hold period
• Confusion about which date starts the clock
• Resources were recently transferred to seller
• Multiple transactions created unclear timeline

Hold period requirements by RIR:

• ARIN: 12 months after any allocation, assignment, or transfer from ARIN
• RIPE: 24 months after allocation or last transfer
• APNIC: 5 years for 103/8 pool resources; otherwise variable
• LACNIC: 36 months after allocation from LACNIC

How to avoid: Before initiating transfer:

# Check ARIN registration date
whois -h whois.arin.net [IP-RANGE] | grep -i "regdate\|updated"

# Check RIPE allocation date
whois -h whois.ripe.net [IP-RANGE] | grep -i "created\|changed"

Prevention checklist:

• Verify exact allocation or transfer date from RIR WHOIS
• Calculate hold period from the correct date (most recent RIR transaction)
• Add buffer time (e.g., wait 13 months for ARIN instead of exactly 12)
• Request confirmation from source RIR if dates are unclear
• Document hold period compliance before making purchase commitment

If rejected:

• Wait until hold period is satisfied
• Consider alternative resource sources
• Negotiate extended closing date with seller
• Check if any hold period exceptions exist (rare)

Typical delay if rejected: Must wait weeks to months

Rejection 2: Source Organization Not Registered Holder

Problem: The organization requesting the transfer is not the registered holder in the RIR database.

Why it happens:

• Corporate restructuring changed legal entity
• Resources registered under different subsidiary
• Parent company vs. subsidiary confusion
• Merger/acquisition not yet reflected in RIR database
• Reseller attempting to transfer resources they don't own

How to avoid:

• Verify exact legal entity name in RIR WHOIS
• Ensure selling organization exactly matches registered holder
• Complete any necessary corporate restructuring with RIR first
• If recent merger/acquisition, update RIR records before transfer

WHOIS verification:

whois -h whois.arin.net [IP-RANGE] | grep -i "orgname\|organization"

If rejected:

• Update registration to correct legal entity
• Complete merger/acquisition process with RIR
• Establish proper authorization chain
• May require 1-4 weeks to resolve

Typical delay if rejected: 1-4 weeks

Rejection 3: Outstanding Obligations to Source RIR

Problem: Source organization has unpaid fees, overdue reports, or other outstanding obligations.

Why it happens:

• Unpaid membership fees
• Late payment of annual maintenance
• Outstanding compliance requests
• Unreturned communications from RIR
• Account holds or restrictions

How to avoid:

• Verify account status with source RIR before initiating
• Pay all outstanding fees
• Respond to any pending RIR requests
• Clear any account restrictions or holds

Checking account status:

• ARIN: Check ARIN Online account dashboard
• RIPE: Review LIR Portal for outstanding items
• APNIC: Check MyAPNIC account status
• LACNIC: Verify member portal compliance status

If rejected:

• Pay outstanding fees immediately
• Respond to compliance requests
• Clear all account holds
• Request status confirmation from RIR

Typical delay if rejected: 3-7 days to 2 weeks

Category 2: Documentation Rejections

Documentation issues are the most common soft rejections and usually the easiest to remedy.

Rejection 4: Incomplete or Missing Documentation

Problem: Required documents not submitted or incomplete.

Why it happens:

• Misunderstanding of requirements
• Checklist not consulted
• Documents partially uploaded
• Email attachments failed
• Portal submission errors

Common missing documents:

• Company registration papers
• Authorization letters
• Officer attestation (ARIN)
• Notarization (ARIN transfers)
• Confirmation letter (RIPE)
• Utilization plans
• Regional presence proof

How to avoid:

Use RIR-specific checklists:

ARIN transfers (source):

• Signed and notarized Officer Acknowledgement Letter
• Transfer agreement (if requested)
• Authorization from Tech or Admin POC
• Payment confirmation

RIPE transfers (recipient):

• Recent company registration (within 6 months)
• Signed confirmation letter from director
• 50% utilization plan (from needs-based RIRs)
• Regional presence documentation

APNIC transfers (recipient):

• Organization registration documents
• 24-month utilization plan
• Network infrastructure documentation
• Authorization letters

Prevention strategies:

• Create complete document package before submitting
• Use RIR-provided templates
• Double-check all attachments uploaded successfully
• Request confirmation of receipt
• Keep copies of everything submitted

If rejected:

• Submit missing documents immediately
• Ensure proper formatting
• Confirm successful upload
• Follow up to verify completeness

Typical delay if rejected: 3-7 days

Rejection 5: Outdated or Invalid Company Registration

Problem: Company registration documents are too old or don't match current legal entity.

Why it happens:

• Using documents more than 6-12 months old
• Company name changed since documents issued
• Registration jurisdiction incorrect
• Documents from wrong legal entity

RIR requirements:

• RIPE: Recent papers from national authorities (typically within 6 months)
• ARIN: Current company documentation
• APNIC: Recent registration certificates
• LACNIC: Current company registration, may require certified translation

How to avoid:

• Obtain fresh company registration documents before starting
• Verify legal entity name matches exactly
• Ensure jurisdiction matches organization location
• Check document expiration or age limits

Document sources by region:

• Europe: National company registries, chambers of commerce
• US: Secretary of State, articles of incorporation
• Canada: Corporate registry
• Asia-Pacific: National business registries
• Latin America: Registro Mercantil, equivalent registries

If rejected:

• Obtain current company registration documents
• Ensure exact legal name match
• Provide certified translations if needed
• Resubmit with updated documents

Typical delay if rejected: 1-2 weeks

Rejection 6: Improper Authorization or Signature

Problem: Authorization letters lack proper signatures, notarization, or authority level.

Why it happens:

• Signer doesn't have legal authority
• Missing notarization (ARIN)
• Unsigned documents submitted
• Electronic signature not accepted
• Wrong person signed

Requirements by RIR:

ARIN:

• Officer Acknowledgement Letter must be signed by corporate officer
• Notarization required
• Officer must have authority to bind organization
• Original signature (not digital)

RIPE:

• Confirmation letter signed by company director
• Must be legally authorized to act on behalf of organization
• Company letterhead required

APNIC/LACNIC:

• Authorization from legal representative
• Proper designation/title
• Company documentation

How to avoid:

• Confirm signer has proper authority (director, officer, authorized representative)
• Obtain notarization where required
• Use original signatures
• Include signer's title and authority
• Reference corporate documents establishing authority

Notarization tips:

• Use licensed notary public
• Bring proper identification
• Ensure document is complete before notarizing
• Get multiple notarized copies
• Check notary seal is clear and complete

If rejected:

• Obtain signature from properly authorized person
• Get proper notarization
• Resubmit with correct authorization
• May need board resolution establishing authority

Typical delay if rejected: 3-10 days

Rejection 7: Incorrect or Inconsistent Information

Problem: Information doesn't match across documents or RIR databases.

Why it happens:

• Legal entity name variations
• Address mismatches
• Contact information differences
• IP range errors
• Copy-paste mistakes

Common inconsistencies:

• "Company Inc." vs. "Company Incorporated"
• Different address formats
• Old vs. new addresses
• Technical contact vs. admin contact confusion
• IP address range typos

How to avoid:

• Use exact legal entity name from registration everywhere
• Use consistent address formatting
• Double-check IP address ranges
• Verify contact information matches RIR database
• Review all documents for consistency before submission

Verification steps:

1. Check exact organization name in source RIR WHOIS
2. Verify address matches company registration
3. Confirm contact details are current
4. Double-check IP ranges against WHOIS
5. Review all documents for exact matches

If rejected:

• Correct inconsistencies
• Update RIR database if needed
• Ensure exact matches across all documents
• Resubmit corrected documentation

Typical delay if rejected: 3-7 days

Category 3: Needs Assessment Rejections

Needs assessment rejections are particularly challenging as they require substantive changes to justification.

Rejection 8: Insufficient Needs Justification

Problem: Destination RIR determines the recipient doesn't adequately demonstrate need for the requested resources.

Why it happens:

• Vague or generic utilization plans
• Unrealistic deployment timelines
• Insufficient infrastructure documentation
• Over-requesting relative to demonstrated need
• Lack of specific use cases
• Poor business case support

RIR assessment standards:

ARIN (24-month):

• Must demonstrate need for up to 24-month supply
• Detailed infrastructure plans required
• Specific customer or service requirements
• Current utilization rates considered
• Conservative estimates preferred

RIPE (50% over 5 years):

• Must show plan to use 50% within 5 years
• Business case must be credible
• Growth projections should be realistic
• Supporting documentation required

APNIC (24-month):

• 24-month utilization plan required
• Infrastructure evidence needed
• Past delegation compliance checked

LACNIC (detailed):

• Comprehensive needs justification
• Historically required NAT deployment evidence
• Detailed technical plans
• Very thorough review process

How to avoid:

Develop strong justification:

1. Detailed infrastructure documentation:

• Network topology diagrams
• Server/equipment deployment plans
• Geographic deployment areas
• Service architecture

2. Specific use cases:

• Customer assignment plans: "50 web hosting customers, 2 IPs each = 100 IPs"
• Infrastructure needs: "20 servers, 5 routers, 10 network devices = 35 IPs"
• Service requirements: "Mail servers: 10 IPs, DNS: 5 IPs, CDN: 50 IPs"
• Growth projections: "Year 1: 200 IPs, Year 2: 400 IPs" with justification

3. Supporting evidence:

• Current IP utilization (if applicable)
• Customer contracts or letters of intent
• Business plan excerpts
• Revenue projections
• Market analysis

4. Realistic timelines:

• Conservative deployment estimates
• Achievable customer acquisition rates
• Reasonable infrastructure buildout schedules
• Industry-standard utilization rates

Example good justification (ARIN 24-month):

Current State:
- Existing /24 (256 IPs): 92% utilized (235 IPs in use)
- 180 web hosting customers (average 1.3 IPs each)
- 15 infrastructure IPs
- 40 IPs for internal services

Requested: /22 (1,024 IPs)

Month 0-6:
- 100 new hosting customers × 1.5 IPs = 150 IPs
- Infrastructure expansion = 25 IPs
- Total: 175 IPs

Month 6-12:
- 150 new customers × 1.5 IPs = 225 IPs
- Service diversification (VPS) = 100 IPs
- Total: 325 IPs

Month 12-18:
- 150 customers × 1.5 IPs = 225 IPs
- Infrastructure scaling = 50 IPs
- Total: 275 IPs

Month 18-24:
- 200 customers × 1.5 IPs = 300 IPs
- Geographic expansion = 75 IPs
- Total: 375 IPs

24-Month Total: 1,150 IPs needed
Buffer for efficiency: 1,024 IPs (/22) requested

Supporting: Customer contracts for 200 customers attached.
Current utilization: 92% demonstrates efficient usage.

If rejected:

• Request specific feedback on deficiencies
• Strengthen documentation with more details
• Provide additional supporting evidence
• Consider reducing requested amount
• Show higher utilization of existing resources if applicable
• Include customer contracts or commitments
• Provide market data supporting growth projections
• Work with consultant to improve justification

Resubmission tips:

• Address specific RIR concerns
• Add substantial new information
• Don't just resubmit same justification
• Consider phone call with RIR to discuss requirements
• Provide examples or case studies

Typical delay if rejected: 1-3 weeks

Rejection 9: Requested Amount Exceeds Justified Need

Problem: RIR approves transfer but for smaller amount than requested.

Why it happens:

• Justification supports only portion of request
• Conservative RIR interpretation
• Utilization rates don't support full amount
• Growth projections deemed unrealistic for full amount

Common scenarios:

• Requested /22 (1,024 IPs), approved for /23 (512 IPs)
• Requested /20 (4,096 IPs), approved for /21 (2,048 IPs)

How to avoid:

• Request amount closely aligned with strong justification
• Add modest buffer (10-20%) rather than excessive
• Ensure justification covers entire requested amount
• Use conservative estimates

If this occurs:

• Accept approved amount
• Complete transfer for approved portion
• Apply again later for additional resources with updated justification
• Negotiate with seller for partial transfer if possible

Typical delay: May extend timeline by 1-2 weeks

Rejection 10: Inadequate Infrastructure Evidence

Problem: RIR questions whether recipient has capability to utilize resources.

Why it happens:

• No evidence of existing infrastructure
• Unbelievable capacity claims
• Startup with no track record
• Mismatch between infrastructure and requested amount

How to avoid:

• Document existing infrastructure thoroughly
• Provide photos, diagrams, equipment lists
• Show current IP utilization if applicable
• Demonstrate technical capability
• Include staff expertise information
• Reference data center or hosting facilities

Strong infrastructure evidence:

• Network topology diagrams with equipment details
• Data center colocation agreements
• Server and network equipment lists
• Screenshots of infrastructure monitoring
• Current BGP routing table information (if applicable)
• Upstream provider agreements
• Technical staff resumes or certifications

If rejected:

• Provide more detailed infrastructure documentation
• Include photos of facilities and equipment
• Add technical staff information
• Show data center agreements
• Demonstrate operational capability

Typical delay if rejected: 1-2 weeks

Category 4: Regional Presence Rejections

Destination RIRs require legitimate operational presence in their service region.

Rejection 11: Insufficient Regional Presence

Problem: Cannot demonstrate adequate operational presence in destination RIR region.

Why it happens:

• Virtual office only
• No active network infrastructure in region
• Registered agent address (not real operations)
• Business primarily in different region
• Shell company setup

Regional presence requirements:

RIPE: Active network element in RIPE NCC service region ARIN: Operational presence in ARIN region (US/Canada/Caribbean) APNIC: Operations in Asia-Pacific region LACNIC: Presence in Latin America/Caribbean

How to avoid:

Establish legitimate presence:

• Physical office or operational facility (not just registered agent)
• Active network infrastructure deployed
• Real business operations in region
• Local employees or contractors
• Customer base in region
• Banking relationships in region

Strong evidence of presence:

• Office lease or property ownership documents
• Utility bills (electricity, internet, phone) showing usage
• Business registration in region
• Local business licenses or permits
• Employee contracts for regional staff
• Data center colocation agreements in region
• Customer contracts showing regional service delivery
• Bank account statements from regional banks
• Photos of physical facilities and infrastructure

Weak evidence (insufficient alone):

• Registered agent address
• Virtual office
• Plans to establish presence
• PO Box
• Serviced office with no dedicated space

If rejected:

• Establish real operational presence before applying
• Provide multiple forms of evidence
• Include photos and documentation
• Show active business operations
• Demonstrate customer base in region

Typical delay if rejected: 2-4 weeks minimum, possibly months

Rejection 12: Questionable Legitimacy of Operations

Problem: RIR questions whether the organization's operations are legitimate.

Why it happens:

• Newly formed company with no track record
• Unclear business model
• Suspicious patterns (multiple similar applications)
• Address shared with many other companies
• No web presence or minimal online footprint
• Connections to previous policy violations

How to avoid:

• Establish legitimate business operations before applying
• Develop professional web presence
• Build track record
• Provide clear, credible business case
• Show real customers and revenue
• Demonstrate industry participation

Evidence of legitimacy:

• Established company (>6 months old preferred)
• Professional website with real content
• Customer testimonials or case studies
• Industry memberships or certifications
• Social media presence
• Press coverage or announcements
• Business references
• Revenue documentation
• Tax filings
• Bank statements

If rejected:

• Provide extensive business documentation
• Show customer contracts and revenue
• Include business references
• Demonstrate established operations
• Consider working with established sponsoring LIR
• May need to wait and build track record

Typical delay if rejected: Variable, potentially months

Category 5: Policy and Compatibility Rejections

Rejection 13: Policy Incompatibility Between RIRs

Problem: Source and destination RIRs have incompatible policies.

Why it happens:

• One RIR doesn't have inter-RIR transfer policy
• Policies aren't reciprocal
• Needs-based requirements incompatible
• Special resource restrictions

Known incompatibilities:

• AFRINIC: No inter-RIR transfer policy - NO transfers to/from AFRINIC
• All RIRs prohibit transfers involving AFRINIC

How to avoid:

• Verify both RIRs support inter-RIR transfers
• Confirm compatible policies exist
• Check current RIR policy documentation
• Understand reciprocity requirements

Compatible RIR combinations:

• RIPE ↔ ARIN ✓
• RIPE ↔ APNIC ✓
• RIPE ↔ LACNIC ✓
• ARIN ↔ APNIC ✓
• ARIN ↔ LACNIC ✓
• APNIC ↔ LACNIC ✓
• Any ↔ AFRINIC ✗

If attempting incompatible transfer:

• Choose resources from compatible RIR
• No workaround for AFRINIC limitation
• Wait for policy development (AFRINIC)

Typical impact: Transfer impossible until policies change

Rejection 14: Certification Not Provided by Source RIR

Problem: Source RIR cannot certify that transfer meets destination RIR's needs-based requirements.

Why it happens:

• ARIN requires certification from source RIR
• Source RIR cannot verify needs-based compliance
• Documentation insufficient for certification
• Policy interpretation differences between RIRs

How to avoid:

• Ensure needs justification meets both RIRs' standards
• Provide comprehensive documentation to source RIR
• Allow source RIR to verify and certify compliance
• Work with both RIRs to address concerns

If rejected:

• Strengthen needs justification
• Provide additional documentation to source RIR
• Clarify how request meets needs-based policies
• May need consultation with both RIRs

Typical delay if rejected: 1-2 weeks

Category 6: Resource-Specific Rejections

Rejection 15: Special-Use or Reserved Address Space

Problem: Attempting to transfer resources that cannot be transferred.

Why it happens:

• Special-use designations (RFC defined)
• Reserved address blocks
• Multicast ranges
• Documentation-only ranges
• Resources with transfer restrictions

Non-transferrable resources:

• Private address space (RFC 1918)
• Multicast addresses
• Reserved ranges
• Documentation examples (RFC 5737)
• Some legacy resources with restrictions

How to avoid:

• Verify resources are publicly routable
• Check for special designations in WHOIS
• Confirm no transfer restrictions
• Avoid resources with unusual characteristics

Verification:

whois -h whois.arin.net [IP-RANGE] | grep -i "status\|special"

If encountered:

• Select different resources
• Confirm no restrictions before purchase commitment

Typical impact: Transfer impossible for those specific resources

Rejection 16: Resources on Blacklists or With Poor Reputation

Problem: While not typically an RIR rejection reason, resources with poor reputation can be rejected by destination organizations or fail business case.

Issues:

• Listed on spam blacklists
• History of abuse
• Poor sender reputation
• Associated with malicious activity

How to avoid:

• Check resources on major blacklists before purchase
• Review BGP history
• Check reputation databases
• Avoid resources with known issues

Checking reputation:

# Major blacklists
- Spamhaus (www.spamhaus.org)
- SpamCop (www.spamcop.net)
- SORBS (www.sorbs.net)
- Check BGP history at bgpview.io

If discovered:

• May need delisting processes
• Consider purchasing different resources
• Factor reputation cleanup into timeline
• Some blacklistings may be permanent

Impact: Not RIR rejection, but business impact

What to Do If Your Transfer Is Rejected

Immediate Steps

1. Review rejection notice carefully:

• Understand specific reasons
• Identify which RIR rejected (source or destination)
• Note what information is requested
• Check if partial approval was offered

2. Request detailed feedback:

• Contact RIR for clarification
• Ask specific questions about deficiencies
• Understand what would make resubmission successful
• Inquire about alternative approaches

3. Assess the situation:

• Determine if rejection is soft (fixable) or hard (fundamental issue)
• Estimate time needed to address issues
• Consider impact on agreement with seller
• Evaluate alternative options

Remediation Strategies

For documentation issues (soft rejections):

• Gather missing or corrected documents
• Ensure proper formatting and signatures
• Resubmit promptly
• Typically resolved in days to weeks

For needs justification issues:

• Strengthen justification with more details
• Add supporting evidence and documentation
• Consider reducing requested amount
• Provide customer contracts or business data
• May need professional assistance
• Typically requires 1-3 weeks

For regional presence issues:

• Establish legitimate presence if missing
• Provide comprehensive evidence
• May require substantial time and investment
• Consider sponsoring LIR if available
• Could take weeks to months

For hold period issues:

• Wait until hold period is satisfied
• Consider alternative resources
• Renegotiate timeline with seller
• No quick fix available

For policy incompatibility:

• Transfer may not be possible
• Select resources from compatible RIR
• No workaround available

Resubmission Best Practices

1. Address ALL rejection reasons:

• Don't just fix one issue if multiple noted
• Provide comprehensive response
• Over-deliver on documentation

2. Add substantial new information:

• Don't resubmit identical application
• Include additional supporting evidence
• Demonstrate serious effort to address concerns

3. Communicate proactively:

• Contact RIR before resubmitting
• Explain changes made
• Ask if additional information would help
• Build positive relationship with staff

4. Consider professional help:

• Transfer brokers
• LIR consultants
• Legal advisors
• Industry experts

5. Learn from rejection:

• Understand what went wrong
• Apply lessons to future transfers
• Improve documentation processes
• Build stronger applications going forward

Prevention: Best Practices to Avoid Rejection

Pre-Transfer Verification Checklist

Before initiating transfer:

Eligibility verification:

• ☐ Hold period requirements met (with buffer)
• ☐ Source organization is registered holder
• ☐ No outstanding obligations to source RIR
• ☐ Resources are transferrable (not special-use)
• ☐ Both RIRs have compatible inter-RIR policies

Documentation preparation:

• ☐ Recent company registration obtained (within 6 months)
• ☐ Authorization letters with proper signatures
• ☐ Notarization obtained where required (ARIN)
• ☐ All information consistent across documents
• ☐ Contact information current in RIR databases

Needs justification:

• ☐ Detailed utilization plan developed
• ☐ Infrastructure documentation prepared
• ☐ Supporting business evidence gathered
• ☐ Realistic timelines and projections
• ☐ Specific use cases documented

Regional presence:

• ☐ Legitimate operational presence established
• ☐ Multiple forms of proof available
• ☐ Active network infrastructure in region
• ☐ Business operations documented

Professional review:

• ☐ Documentation reviewed by expert
• ☐ Legal review completed if needed
• ☐ RIR requirements verified
• ☐ Compliance confirmed

When to Seek Professional Help

Consider professional assistance for:

• First inter-RIR transfer
• Large transfers (≥/16)
• Complex justifications
• Previous rejections
• Tight timelines
• Legacy resources
• Multiple-party transactions
• Unfamiliar RIRs
• Critical business need

Professional services available:

• Transfer brokers and facilitators
• Sponsoring LIRs
• RIR consultants
• Legal advisors specializing in IP transfers
• Documentation preparation services

Via-Registry Rejection Prevention and Resolution

Via-Registry helps prevent and resolve inter-RIR transfer rejections:

Prevention services:

• Pre-transfer eligibility verification
• Complete documentation preparation
• Needs justification development
• Regional presence establishment assistance
• RIR policy compliance review

Professional expertise:

• Experience with thousands of successful transfers
• Relationships with all RIRs
• Understanding of common rejection reasons
• Templates and best practices
• Proactive issue identification

Rejection resolution:

• Detailed analysis of rejection reasons
• Strategy development for resubmission
• Enhanced documentation preparation
• Direct RIR communication and advocacy
• Alternative approach identification

Success rate:

• 95%+ first-time approval rate for Via-Registry managed transfers
• Quick resolution of rejected transfers
• Expert guidance through complex situations

Get started with our Inter-RIR Transfer Service to minimize rejection risk and ensure successful transfers.

Summary

Common inter-RIR transfer rejections fall into six categories:

Hold period and eligibility (hard rejections):

• Hold period not met
• Not registered holder
• Outstanding obligations

Documentation (soft rejections):

• Missing documents
• Outdated company registration
• Improper authorization
• Inconsistent information

Needs assessment:

• Insufficient justification
• Requested amount exceeds justified need
• Inadequate infrastructure evidence

Regional presence:

• Insufficient presence in destination region
• Questionable operational legitimacy

Policy compatibility:

• Incompatible RIR policies
• Certification not provided

Resource-specific:

• Special-use or reserved space
• Reputation issues

Prevention strategies:

• Verify eligibility thoroughly before starting
• Prepare complete, accurate documentation
• Develop strong needs justification
• Establish legitimate regional presence
• Use professional services when appropriate
• Learn from any rejections

If rejected:

• Review rejection reasons carefully
• Request detailed feedback
• Address all issues comprehensively
• Add substantial new information
• Consider professional assistance
• Resubmit when fully prepared