Services

JZWSite Dash

Operational

60-day uptime

99.92%

Avg response

204ms

Today

100.00%

Total downtime

1.1h

Uptime history

30 days agoToday
OperationalDegradedOutageNo data
500msavg 148ms · peak 231ms
Oct 5, 8:00 AMNov 4, 8:00 AM

Recent incidents

JZWSite Dash Backend Outage

JZWSite Dash
◕major
Resolved·Jul 8, 2026, 10:53 PMLatest

The incident has been resolved.

Monitoring·Jul 8, 2026, 10:50 PM

Backend services are recovering. We are monitoring the situation closely.

Identified·Jul 8, 2026, 10:38 PM

We have identified an issue affecting backend services and are working to restore normal operation. Some pages may remain stuck loading or fail to display data.

JZWSite Dash Not Accessible

JZWSite Dash
◐minor
Resolved·Jun 3, 2026, 05:09 PMLatest

The incident has been resolved.

Monitoring·Jun 3, 2026, 05:04 PM

JZWSite Dash is now accessible. We are monitoring the situation closely.

Investigating·Jun 3, 2026, 05:00 PM

We are aware of this issue and are currently investigating.

[Major Outage] JZWSite & JZWSite Dash Inaccessible

JZWSiteJZWSite Dash
●critical
Resolved·May 20, 2026, 10:42 AMLatest

The issue has been resolved. All services are back in full operation.

Monitoring·May 20, 2026, 10:20 AM

JZWSite and login with JZWSite SSO is now accessible and possible. We are closely monitoring the recovery of the services.

Update·May 20, 2026, 09:49 AM

JZWSite Dash is now accessible. However, JZWSite remains inaccessible and login with JZWSite SSO is not possible currently. We apologise for the inconvenience.

Identified·May 20, 2026, 09:44 AM

Timeline of the incident: On May 19, 22:29 UTC, upstream provider started to experience some minor outage. On May 19, 22:43 UTC, upstream provider identified the issue and worked on fixing the issue. However on May 19, 23:37 UTC, upstream provider began to experience a major outage, causing JZWSite and JZWSite Dash inaccessible until now.

Identified·May 20, 2026, 09:36 AM

Due to upstream provider outage, JZWSite and JZWSite Dash are not accessible. We apologise for the inconvenience.

Investigating·May 20, 2026, 09:35 AM

We are aware of this incident and are currently investigating.