At a glance
NEXT runs on redundant, AWS-hosted infrastructure with multiple load balancers, web servers, and replicated databases, monitored 24×7×365 with on-call escalation. Customers can subscribe to a public status page for live and historical uptime; routine maintenance is announced at least 5 days ahead and targeted for Sunday 00:00–03:00 GMT. Data is replicated across multiple Availability Zones with an EU-hosted default.
Architecture foundations
Multi-AZ design: Production workloads are deployed across multiple AWS Availability Zones to avoid single-AZ failures, per AWS reliability best practices.
Load balancing: Elastic Load Balancing distributes traffic across targets in one or more AZs, with health checks and automatic scaling for resilience.
Storage resilience: Object storage on Amazon S3 is designed for 99.999999999% durability and 99.99% availability over a given year.
Reliability framework: Design choices align with the AWS Well-Architected Reliability Pillar.
Operations you can expect
24×7×365 monitoring & alerting with on-call escalation; cloud telemetry via AWS monitoring services.
Status & comms: Live status and incident history are published on NEXT’s status page; customers can subscribe for updates.
Scheduled maintenance: Announced ≥5 days in advance and targeted for Sunday 00:00–03:00 GMT to minimize impact.
Cloud monitoring detail: Operational health is tracked in AWS CloudWatch/Logs (metrics, alarms, log centralization).
Uptime & status
The Service Level Agreement (SLA) defines the availability standard (monthly uptime) and associated service credits, and points to the public status page for updates.
Related topics
FAQ
Q: What uptime target does NEXT AI commit to?
See NEXT’s Service Level Agreement for the monthly availability standard and service-credit tiers.
Q: Do you deploy across multiple Availability Zones?
Yes. NEXT AI’s default hosting is in AWS EU-WEST-1 with data replicated across multiple AZs for redundancy and recovery.
Q: How do you keep the service highly available during traffic spikes or failures?
Elastic Load Balancing spreads traffic across healthy targets in one or more AZs and scales request handling automatically; health checks remove unhealthy targets.
Q: Where can I see real-time and historical uptime?
On NEXT’s public status page, where you can also subscribe to updates. (The SLA references the same page for official availability communications.)
Q: When is scheduled maintenance performed, and how much notice is given?
NEXT announces maintenance at least 5 days in advance and targets Sunday 00:00–03:00 GMT to limit impact.
Q: What monitoring do you use?
Cloud telemetry is centralized and alerted via AWS CloudWatch/Logs; on-call engineers are paged for investigation and remediation.