Status & Uptime

Edge has maintained 100% network uptime since inception. That's not a marketing claim — it's a track record built on distributed architecture, global redundancy and an engineering culture that treats availability as non-negotiable.

Live Status

Real-time service status is available at:

edge.network/status

The status page covers all Edge products and infrastructure components:

  • Compute — VM provisioning and management
  • CDN — content delivery network
  • DNS — authoritative DNS service
  • Storage — object storage gateway
  • Control Panel — account and management interface
  • API — platform and agent APIs

Why 100%?

Edge's architecture is inherently resilient. There is no single point of failure:

  • Distributed by design — infrastructure spans 2,000+ locations across 80+ countries. Losing any individual node or location has no impact on service.
  • Anycast routing — DNS and CDN queries are automatically routed to the nearest healthy point of presence. If one location goes down, traffic seamlessly shifts to the next closest.
  • Redundant master infrastructure — core services run across multiple independent systems with automatic failover.
  • No centralised data centres — unlike traditional cloud providers, Edge doesn't depend on a handful of massive facilities. The network's strength is in its distribution.

SLA Commitments

PlanUptime SLA
Dev / Startup / ScaleupBest effort (100% track record)
Business99.9% SLA
Enterprise99.99% SLA (contractual)

Enterprise SLA agreements include defined credit policies for any downtime. For details on SLA terms, escalation procedures and credits, contact support@edge.network.

Subscribing to Updates

Stay informed about service status, maintenance windows and incident reports:

Planned Maintenance

Edge performs maintenance with zero downtime wherever possible. In the rare event that maintenance requires a service interruption, advance notice is given through the status page and community channels. Maintenance windows are scheduled during low-traffic periods and communicated at least 48 hours in advance.

Incident Response

In the event of a service disruption:

  1. Detection — 24/7 automated monitoring detects issues in real time
  2. Triage — the on-call engineering team investigates and classifies severity
  3. Communication — the status page is updated and affected customers are notified
  4. Resolution — the team works to restore service as quickly as possible
  5. Post-mortem — a review is conducted and findings are shared with the community where appropriate