A complete record of Raff service incidents and maintenance, each with a full timeline of updates from first report to resolution.
On June 24, 2026, between 16:48 and 17:45 UTC, a hardware fault caused three compute hosts in our US-East region to become temporarily unavailable, affecting a subset of instances running on them. Our team identified the issue and the affected hardware was recovered. All impacted instances were restored to normal operation by 17:45 UTC. No data was lost. All volumes are held on redundant network storage and were unaffected throughout the incident. We are following up with our datacenter provider to reduce the chance of recurrence. We apologize for the disruption.
Some virtual machines on two compute nodes experienced brief connectivity interruptions due to a network driver issue. The root cause has been identified and resolved. All services are fully restored.
We are migrating virtual machines to upgraded hardware for improved performance. VMs will experience a brief restart (~30 seconds). No data loss — all storage is unaffected.
The storage infrastructure issue has been resolved. All VM operations are functioning normally. We apologize for any inconvenience and will be conducting an internal review to prevent recurrence.
Storage node maintenance has been completed. Read/write performance on all virtual machines has returned to normal levels. We appreciate your patience during this window.
While conducting network improvement tests, we encountered an unexpected issue that caused severe performance degradation and complete downtime for all instances in the region. Service has been fully restored in 2 hours.
Our primary status and monitoring servers experienced an unexpected outage. This has resulted in a loss of visibility into our systems' health and performance metrics. The monitoring infrastructure itself is down, which means we currently have limited ability to track service status and receive automated alerts.