DOCSEARCHbyAlgolia
Submit Docs

Sunyz Network Documentation

website·Indexed 32 days ago

https://sunyz.net/docs/

Technical documentation for Sunyz Network (AS150289), covering peering policies, interconnection methods via IXP, routing security, community control for prepend and learned routes, and legal terms of service.

Tokens
2.8K
Snippets
6
Records
27
Agent score
62%

What's inside Sunyz

  1. Sunyz Network infrastructure overview

    Sunyz Network (AS150289) provides a high-performance global network built on a pure IPv6 backbone and intelligent BGP routing. The infrastructure is designed for minimal latency and high reliability, featuring 15+ Global PoPs, 10+ Upstreams, 10+ Internet Exchanges, and a backbone capacity exceeding 20Gbps.

  2. Engineer BGP architecture for network resilience

    Ensure high availability and uninterrupted connectivity by operating a self-managed, multi-homed BGP architecture. Use advanced BGP traffic engineering and dynamic path selection algorithms to automatically route traffic around upstream failures or network congestion.

  3. Establish a direct BGP session over an IXP fabric

    Direct BGP sessions over a shared IXP fabric are supported. To initiate the setup process for a direct session, you must contact the network's NOC.

  4. Meet operational and traffic requirements for peering

    Beyond technical specifications, peering partners must adhere to the following:

    • Operational: Maintain an up-to-date PeeringDB entry, which must include a 24x7 NOC Contact.
    • Traffic: There are currently no minimum traffic requirements for establishing bilateral peering sessions.

  5. Report network abuse to Sunyz Network

    To report malicious, illegal, or abusive activities (such as DDoS, malware distribution, phishing, network scanning, spam, copyright infringement, or intrusion attempts) involving Sunyz Network (AS150289) infrastructure, send an email to the Security and Abuse Response Team.

    For the best chance of processing, use a corporate or work email address associated with your network (ASN) or organization. Reports from public providers like @163.com, @126.com, and @qq.com are gray-listed, and domains containing 'tsinghua' are ignored.

    Email: abuse@sunyz.net

  6. Operational requirements for BGP peering with Sunyz Network

    Networks establishing BGP sessions with Sunyz Network (AS150289) must adhere to the following operational standards to maintain connectivity:

    • Maintain an accurate and up-to-date PeeringDB record.
    • Provide a responsive 24x7 NOC contact.
    • Ensure all routing announcements are strictly valid according to IRR and RPKI databases. Invalid route announcements are automatically dropped.

  7. Establish peering via IXP Route Servers

    The network announces routes to Route Servers (RS) at all participating Internet Exchange Points (IXPs) by default. Using the Route Server is the strongly recommended method for peer networks to exchange routes, as it minimizes configuration overhead and administrative complexity.

  8. Exercise privacy rights and data requests for Sunyz Network

    Depending on the jurisdiction, users and peering partners may exercise the following rights regarding their data:

    • Access: Request a copy of personal data.
    • Correction: Update inaccurate NOC or peering information.
    • Deletion: Request deletion of personal data, subject to legal and operational retention requirements.

    To exercise these rights or update peering contact details, users should contact Sunyz Network directly.

  9. Follow security best practices for submitting abuse evidence

    When reporting abuse to Sunyz Network, follow these guidelines to ensure prompt investigation:

    • Evidence Format: Attach raw plain-text logs, packet captures, or screenshots. Do not use PDF or Word documents.
    • Specificity: Provide exact metrics and indicators of compromise (IoCs).
    • Organization: Submit one email per distinct incident to ensure correct categorization in the ticketing system.

  10. Sunyz Network IPv6 implementation

    The Sunyz Network is architected on a native IPv6 backbone. This design eliminates legacy NAT overhead and is intended to support next-generation connectivity requirements.

  11. Meet technical requirements for peering with sunyz.net

    To establish a peering interconnection, networks must meet the following technical criteria:

    • Operate a publicly routable and visible Autonomous System Number (ASN).
    • Possess at least one publicly routable /24 IPv4 prefix and/or one /48 IPv6 prefix.
    • Register routes in a public Internet Routing Registry (IRR) database (supported: APNIC, RIPE, ARIN, AFRINIC, LACNIC, and RADb). For other databases like AltDB, contact the NOC for review.
    • Register routes in the Resource Public Key Infrastructure (RPKI) repository using Route Origin Authorization (ROA) objects. Prefixes with an 'invalid' status (validated via Cloudflare) will be dropped.
    • Have no adverse record and not be on the internal blacklist.
    • Implementation of MANRS (Mutually Agreed Norms for Routing Security) is strongly encouraged.

  12. Service termination and notice periods

    Termination of services or peering is handled as follows:

    • Standard Termination: Requires 30 days written notice. The peer must migrate services and remove routing dependencies within this window.
    • Immediate Termination: Sunyz Network may terminate immediately for material breaches of the AUP, illegal activity, security threats, or non-payment exceeding 30 days.