Past 24 Hours
99.99%
No incidents
Past 7 Days
99.98%
1 minor incident
Past 30 Days
99.95%
2 minor incidents
Past 90 Days
99.93%
3 incidents resolved

System Components

View all 24 components →
Compute & Hosting
Cloud Compute (VPS) Virtual private servers & bare metal instances
Operational
Managed Kubernetes K8s cluster management & orchestration
Operational
Container Registry Docker image storage & distribution
Operational
Networking
Global CDN Content delivery network — 300+ edge locations
Operational
Load Balancer Global load balancing & traffic routing
Operational
DNS DNS resolution & management
Operational
Storage & Databases
Object Storage (S3) Scalable object storage service
Operational
Managed PostgreSQL Managed relational database service
Operational
Managed Redis In-memory data store & caching
Operational
Platform & Security
CloudNexus Console Web dashboard & management portal
Operational
API Gateway REST & GraphQL API endpoints
Operational
DDoS Protection Network-layer attack mitigation
Operational

Scheduled Maintenance

🔧
APAC Region — Database Engine Upgrade
Managed PostgreSQL & MySQL — Tokyo, Sydney, Singapore
Jan 18, 2025
02:00 – 05:00 UTC
Scheduled
🛡️
DDoS Protection — Firmware Update
Network edge appliances — All regions
Jan 22, 2025
04:00 – 06:00 UTC
Scheduled
✅
EU-West Region — Hardware Replacement
Cloud Compute nodes — Frankfurt
Jan 10, 2025
01:00 – 03:00 UTC
Completed

Incident History

Resolved
Elevated Latency on Managed Kubernetes in US-East
January 14, 2025 — 03:22 UTC – 04:45 UTC
Managed Kubernetes
▼
✓
Resolved
The issue has been fully resolved. All Kubernetes clusters in US-East are operating normally. Latency metrics have returned to baseline.
04:45 UTC
🔍
Monitoring
A fix has been deployed to affected clusters. We are actively monitoring latency and pod scheduling metrics to confirm full restoration.
04:10 UTC
🔍
Identified
Root cause identified: a network routing table misconfiguration on a subset of worker nodes caused packet retransmission and elevated pod-to-pod latency.
03:55 UTC
⚠
Investigating
We are investigating reports of elevated latency (150–400ms) for pod-to-pod communication in US-East region (Virginia). API and ingress traffic unaffected.
03:22 UTC
Resolved
CloudNexus Console — Intermittent Login Failures
January 8, 2025 — 18:10 UTC – 19:05 UTC
Console, API Gateway
▼
✓
Resolved
Authentication service has been fully restored. All users can now log in without issues. We apologize for the inconvenience.
19:05 UTC
🔄
Update
Our engineering team has rolled back a recent configuration change to the session management service that caused the issue. Services are recovering.
18:50 UTC
🔍
Identified
We have identified the root cause as a session cache inconsistency following a deployment update. A fix is being prepared.
18:35 UTC
⚠
Investigating
We are investigating reports of intermittent 503 errors when logging into the CloudNexus Console. API Gateway status endpoint is also experiencing delays.
18:10 UTC
Resolved
CDN — Cache Miss Rate Spike in EU-West
January 3, 2025 — 11:40 UTC – 12:55 UTC
Global CDN
▼
✓
Resolved
Cache miss rates have returned to normal levels across all EU-West edge nodes. No further customer impact expected.
12:55 UTC
🔄
Update
A cache warming process has been triggered across affected edge locations. Miss rates are decreasing — currently at 12% (normal is <2%).
12:20 UTC
⚠
Investigating
We have detected an unusual spike in CDN cache miss rates (up to 35%) for content served from EU-West edge nodes (Amsterdam, Dublin, Paris). Page load times may be temporarily affected.
11:40 UTC
Resolved
Object Storage — Intermittent PUT Request Timeouts
December 28, 2024 — 08:15 UTC – 09:30 UTC
Object Storage (S3)
▼
✓
Resolved
PUT request latency has stabilized. All storage operations are performing within normal parameters.
09:30 UTC
🔍
Identified
Issue traced to a storage node firmware bug in the SA-East region causing write request queuing. Automated failover has been initiated.
09:00 UTC
⚠
Investigating
Monitoring systems detected elevated PUT request latencies (2–8s, normal <200ms) on Object Storage API. GET requests unaffected.
08:15 UTC