Network / CDN

IXCDN CDN Acceleration

IXCDN is Wulian Network's edge acceleration and AI platform. Built around IX peering, edge cache, intelligent routing and secure edge ingress, it delivers websites, APIs, downloads, media and AI / token traffic with lower cost, clearer observability and stronger protection.

Buy or consult

IX

Peering lowers transit cost

EDGE

Cache, routing and security ingress

AI

Token-stream acceleration

Console

Logs, hit ratio and billing visibility

Unify content, security, routing and AI traffic at the edge ingress

IXCDN combines Internet Exchanges, peer networks, owned or partner edge locations and the EdgeManager control plane. It manages business domains, DNS routing, cache policy, certificates, WAF, access logs and model traffic in one path. Requests enter IXCDN edge first, then are served, forwarded, fetched from origin or blocked by domain, path, method, cache policy and inference strategy, making performance, security and cost continuously operable.

Key advantages

IX peering for cost-aware delivery

Reduce dependency on expensive transit through Internet Exchanges, peer networks and owned edge interconnect, making high-traffic websites, downloads and media delivery easier to control.

  • IX peering and peer networks
  • Owned edge interconnect
  • Fewer repeated origin fetches
  • Clear valued-traffic billing

Secure edge ingress

DDoS, WAF, TLS, access control, token validation and origin protection run at the edge first. Suspicious requests can be observed, logged and then blocked by policy.

  • L3 / L4 / L7 DDoS protection
  • OWASP WAF and bot defense
  • TLS, certificates and origin protection
  • Access control and token validation

Edge cache and intelligent routing

Multilayer cache, prefetch, directory purge, stale serving and GSLB routing reduce repeated origin fetches and steer users to suitable available edge locations.

  • Purge by URL, file or directory
  • Custom TTL and cache rules
  • Anycast and GeoDNS routing
  • Origin groups and Origin Shield

AI / token traffic acceleration

For LLM and AIGC applications, IXCDN provides edge ingress, connection reuse, token aggregation and model-service routing to reduce stream wait time and upstream pressure.

  • LLM / AIGC streaming
  • Token aggregation and connection reuse
  • Model-service routing
  • Secure AI API ingress

Typical use cases

Global websites and APIs

Use IX peering, edge cache and intelligent routing to lower cross-region access cost and improve page, API and static-asset delivery stability.

  • Static asset acceleration
  • Dynamic API origin fetch
  • Unified TLS and WAF management
  • Error tracking and logs

Media, downloads and large files

Deliver software packages, images, video and live segments with cache, prefetch, purge and stale serving to reduce repeated origin fetches.

  • Large-file delivery optimization
  • RAM cache for live
  • Micro-segment caching
  • Download speed limits

Enterprise secure edge

Run SSL/TLS, DDoS, WAF, bot defense, API security, token validation and access control at the edge ingress to reduce origin exposure.

  • WAF detect and block modes
  • API security
  • IP / geo access control
  • Origin protection

AI applications and token streams

Provide edge ingress, token aggregation, connection reuse and model-service routing for chat, search, agents, AIGC and streaming inference.

  • LLM / AIGC ingress
  • Token-stream acceleration
  • Connection reuse
  • Regional compute routing

Core platform capabilities

Smart routing across IX, carriers and edge health

Route users to suitable edge ingress by geography, carrier, ASN, line-library signals, real-time quality and edge load, reducing unnecessary cross-region and cross-carrier detours.

  • IX-peering-first policy
  • Anycast and GeoDNS
  • Edge health awareness
  • Policy review, publish and rollback

Multilayer cache aligned with business boundaries

Control cache, prefetch, purge and origin behavior by domain, method, path, suffix, MIME type, size and directory, so static content stays at the edge while dynamic requests fetch correctly from origin.

  • Custom TTL
  • Prefetch and global purge
  • Always Online / Serve Stale
  • Cache hit-ratio analytics

WAF, DDoS, TLS and origin protection before origin

Domain ownership checks, TLS, access policy and WAF inspection run at the edge ingress. WAF can start in detect mode, then move to blocking after compatibility is confirmed.

  • Domain ownership verification
  • DDoS / WAF / bot defense
  • TLS 1.3 and free SSL
  • Secure token and access control

Edge ingress for LLM and AIGC traffic

Model requests can enter IXCDN edge first. Connection reuse, token aggregation and model-service routing reduce stream wait time while security policies protect model services before traffic arrives.

  • Token aggregation
  • Connection reuse
  • Model-service routing
  • AI API security

Unified visibility for requests, bandwidth, cache, WAF and billing

IXCDN Console brings requests, egress, cache hit ratio, status codes, access logs, WAF events and operator audit into one view for troubleshooting, capacity planning, compliance and cost management.

  • Access logs and raw logs
  • WAF event viewer
  • Bandwidth, region and hit ratio
  • Usage, billing and budget boundaries

FAQ

Cost control mainly comes from IX peering, peer networks, owned edge interconnect and better cache hit ratio. Actual results depend on region, carrier, IX coverage, cache behavior and route conditions.

Websites and SaaS, APIs, downloads and media files, live segments, AI inference and token streams can all be connected. Static content is served from the edge first, while dynamic and real-time requests can be fetched or forwarded by policy.

DDoS, WAF, TLS, token validation, access control and origin protection run at the edge ingress. WAF supports detect-first then block, while scrubbing capacity, rulesets and enterprise policy should be confirmed by plan or contract.

Valued traffic means billable traffic actually delivered to end users. Peer networks, optimized routes and enterprise capabilities can be separated into different billing items instead of hidden in one blended unit price.

Start with one representative domain, complete ownership verification and CNAME onboarding, then observe latency, hit ratio, origin fetches, WAF events and cost before expanding the rollout.