---
title: "ZENTRA Cloud 2.0 Uptime"
description: "View the current uptime status and service availability for ZENTRA Cloud 2.0."
url: "https://docs.zentracloud.io/l/en/article/y4ajemtk18-uptime-monitor-zentra-cloud-2-0"
category: "Uptime & Incidents"
updated_at: "2026-09-09T23:22:27Z"
language: "en"
---

# ZENTRA Cloud 2.0 Uptime

#### Uptime

[Full page view →](https://status.zentracloud.io/)

[Embedded object](https://status.zentracloud.io/)

#### Incident Reports

| Date                    | Description                                                                                                                                                                                                                                                                         | Type            | Severity | Status   | Report                                                                                            |
|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|----------|----------|---------------------------------------------------------------------------------------------------|
| Sept 06, 2026 00:29 UTC | On September 5, a time zone handling issue affecting data processing for devices in Chile was discovered. Devices showed a data gap. A fix was deployed and all queued messages were successfully replayed by 00:30 UTC on September 6. Devices in other regions were not affected. | Data Processing | SEV3     | Resolved | [Incident Report](https://docs.zentracloud.io/l/en/article/pc05vc2a2j-september-6-2026-00-29-utc) |
| July 15, 2026 21:12 UTC | Between approximately 10:20 and 16:40 UTC on July 15, a network issue temporarily prevented our data processing services from reaching part of our cloud infrastructure. During this window, data and alerts were delayed, and incoming messages were queued.                       | Network         | SEV3     | Resolved | [Incident Report](/l/en/article/vozz5qwajl-july-15-2026-21-12-utc)                                |
