Major incident

InterServer: Teb4 / H5 Elevated Temperatues

Jul 2, 2026, 20:25 UTC
started
20:38 UTC
resolved July 3, 2026
24 h 13 min
duration

Affected: TEB4

Current status of InterServer: Operational — live InterServer status

Timeline

  1. Jul 2, 2026, 20:25 UTC
    investigating
    We are currently investigating elevated temperatures affecting the TEB4 data center. Due to a heatwave advisory in New Jersey, the facility is experiencing an air conditioning issue that is impacting cooling within the data center. The facility team is actively working to restore normal cooling operations as quickly as possible. At this time, some services may experience degraded performance while we closely monitor the environment and take appropriate measures to protect customer equipment. We will provide additional updates as more information becomes available.
  2. Jul 2, 2026, 21:22 UTC
    investigating
    h5 has updated: Additional temporary cooling equipment is being mobilized to the site to support remediation efforts while repairs are underway. Site Operations and Engineering teams are actively monitoring conditions and managing the response. However: InterServer staff will move some affected systems to Teb8
  3. Jul 2, 2026, 21:36 UTC
    investigating
    h5 has updated: Temporary cooling is enroute Our mechanical vendor is currently on-site evaluating the situation and performing remediation activities. Additional temporary cooling equipment is enroute to the facility to support cooling capacity while corrective actions are underway.
  4. Jul 2, 2026, 23:14 UTC
    investigating
    Two batches of systems are in process of being racked in Teb8 from Teb4. Temperatures are coming down, and it is expected no further systems will be moved to teb8.
  5. Jul 3, 2026, 01:17 UTC
    monitoring
    The H5 New Jersey facilities temperatures have returned to normal and have stabilized at this time. No further systems are being moved to Teb8 at this time.
  6. Jul 3, 2026, 20:38 UTC
    resolved
    This incident has been resolved.

Updates as published by InterServer (original).

Other services with incidents at the same time

More InterServer incidents