__ ___ ____ __ ___ ___ __/ /____ ___ ___ __ _ / _ | / __/ ___ ___ / /_ / _ `/ // / __/ _ \/ _ \/ _ \/ ' \/ __ |_\ \_ / _ \/ -_) __/ \_,_/\_,_/\__/\___/_//_/\___/_/_/_/_/ |_/___(_)_//_/\__/\__/
fair use policy this policy defines reasonable usage limits for autonomAS.net services. bandwidth and traffic our service provides ipv6 unnumbered peering with both ipv4 and ipv6 connectivity on a fair use basis. fair use means: - typical network operations, routing, and legitimate traffic are acceptable - sustained high bandwidth usage that impacts network performance may be subject to rate limiting or service review - we reserve the right to implement traffic shaping during network congestion - abusive traffic patterns (dos attacks, scanning, spam) are prohibited reasonable use examples: ✓ hosting websites and services ✓ development and testing ✓ legitimate network operations ✓ routing traffic for connected networks unacceptable use examples: ✗ sustained bandwidth saturation ✗ network scanning or attack traffic ✗ spam or malicious content distribution ✗ cryptocurrency mining via tunneled traffic ✗ bittorrent or mass file distribution without prior approval bgp operations bgp features are provided on a fair use basis: prefix announcements: - prefix updates should be stable and infrequent - excessive flapping or route changes may be rate-limited - we may deny or slow down abnormally high prefix ticket updates - prefix lists must be valid and properly registered in IRR route quality: - all announced prefixes must have valid ROAs (RPKI) - route objects must be maintained in IRR databases - invalid or unverifiable prefixes will be filtered - AS-SET must be kept current and accurate downstream management downstream support is provided as a fair-use feature: we may withdraw support if: - RPKI and route6 objects are repeatedly missing or invalid - AS-SET is not maintained or contains incorrect entries - required information is not provided when requested - prefix leaks occur from your downstream - fair-use terms are abused resource allocation resources are allocated based on fair use principles: asn assignments: - private ASN: automatic assignment (4200000000-4294967294) - public ASN: must be properly registered, requires approval ipv6 prefixes: - PA (/48): automatic allocation from our block - PI (/48): must be properly registered with RIR, requires approval ipv4 addresses: - single ipv4 addresses are not available during the beta - when we add them, they are subject to availability and justification service modifications we reserve the right to: - modify fair use limits based on network capacity - implement rate limiting during congestion - request usage justification for high-volume users - terminate service for policy violations customers will be notified of changes when feasible, but we may take immediate action to protect network integrity. reporting and appeals if you believe your service has been restricted in error: - contact us at hello@autonomas.net with details - include your ASN and description of usage - we will review and respond within 2 business days service is free during beta within fair use limits. we announce prices before the beta ends. ← back to home