All Systems Operational

Website Operational
90 days ago
99.99 % uptime
Today
India Cluster [AWS] Operational
90 days ago
99.99 % uptime
Today
Gateway Operational
90 days ago
100.0 % uptime
Today
Workflow Operational
90 days ago
100.0 % uptime
Today
Webhooks Operational
90 days ago
100.0 % uptime
Today
APIM Gateway Operational
90 days ago
99.99 % uptime
Today
Polling Operational
90 days ago
100.0 % uptime
Today
Job History Operational
90 days ago
100.0 % uptime
Today
Databases by Quickwork Operational
90 days ago
100.0 % uptime
Today
Embedded Journeys Operational
90 days ago
100.0 % uptime
Today
Content Template Operational
90 days ago
100.0 % uptime
Today
Job Processor - Default Operational
90 days ago
100.0 % uptime
Today
Job Processor - Tier 1 Operational
90 days ago
100.0 % uptime
Today
Job Processor - Tier 2 Operational
90 days ago
100.0 % uptime
Today
Job Processor - Tier 3 Operational
90 days ago
100.0 % uptime
Today
Japan Cluster [AWS] Operational
90 days ago
100.0 % uptime
Today
Gateway Operational
90 days ago
100.0 % uptime
Today
Workflow Operational
90 days ago
100.0 % uptime
Today
Webhooks Operational
90 days ago
100.0 % uptime
Today
Germany Cluster [Open Telekom Cloud] Operational
90 days ago
99.99 % uptime
Today
Gateway Operational
90 days ago
99.99 % uptime
Today
Workflow Operational
90 days ago
100.0 % uptime
Today
Webhooks Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Jun 26, 2025

No incidents reported today.

Jun 25, 2025

No incidents reported.

Jun 24, 2025

No incidents reported.

Jun 23, 2025

No incidents reported.

Jun 22, 2025

No incidents reported.

Jun 21, 2025

No incidents reported.

Jun 20, 2025

No incidents reported.

Jun 19, 2025

No incidents reported.

Jun 18, 2025
Resolved - Issue Summary:

On 18th June 2025, Users experienced a 404 Not Found error when accessing the history section of the application in Japan Region

Incident Duration:

Started at 1:11 PM JST
Resolved at 3:03 PM JST

Impact:

1. History data was temporarily inaccessible.
2. No data loss occurred.
3. All data was visible and accessible after resolution.

Root Cause:

The issue was caused by a configuration error introduced during a recent change.

Resolution:

The configuration was corrected, and the service resumed normal operation.

Preventive Actions:

Strengthen pre-deployment validation checks.
Improve monitoring for early detection of similar issues.

Jun 18, 04:11 UTC
Jun 17, 2025

No incidents reported.

Jun 16, 2025

No incidents reported.

Jun 15, 2025

No incidents reported.

Jun 14, 2025

No incidents reported.

Jun 13, 2025

No incidents reported.

Jun 12, 2025

No incidents reported.