Apwide Outage History

Apwide had 5 outages in the last 2 years totaling 12h 20m of downtime — averaging 0.2 incidents per month.

There were 5 Apwide outages since April 17, 2025 totaling 12h 20m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://apwide.statuspage.io

Critical March 10, 2026

Outage on Golive

Detected by Pingoru: Mar 10, 2026, 07:04 PM UTC
Resolved: Mar 10, 2026, 08:27 PM UTC
Duration: 1h 22m

Affected: Golive Cloud - AppGolive Cloud - APIGolive Cloud - Email NotificationsGolive Cloud - Automations & Webhooks

Timeline · 3 updates

investigating Mar 10, 2026, 07:04 PM UTC

We are currently investigating the issue.
investigating Mar 10, 2026, 07:32 PM UTC

We identified a DNS resolution issue on one of our production nodes. The Golive service has been moved to another node and is now available again. We are currently working with our cloud provider to determine the root cause of the issue and implement a fix.
resolved Mar 10, 2026, 08:27 PM UTC

We have identified and resolved the root cause of the issue. One of our nodes was unable to perform DNS resolution due to routing errors. The routing issues have now been fixed, and DNS resolution is working correctly. We apologize for the inconvenience caused.

Read the full incident report →

Major February 5, 2026

Performance issue on Golive

Detected by Pingoru: Feb 05, 2026, 07:46 AM UTC
Resolved: Feb 05, 2026, 02:56 PM UTC
Duration: 7h 10m

Affected: Golive Cloud - AppGolive Cloud - APIGolive Cloud - Email NotificationsGolive Cloud - Automations & Webhooks

Timeline · 9 updates

Read the full incident report →

Critical November 5, 2025

Golive and Time Squad outage

Detected by Pingoru: Nov 05, 2025, 06:20 AM UTC
Resolved: Nov 05, 2025, 10:07 AM UTC
Duration: 3h 47m

Affected: Golive Cloud - AppGolive Cloud - APITime Squad CloudGolive Cloud - Email NotificationsGolive Cloud - Automations & Webhooks

Timeline · 5 updates

Read the full incident report →

Critical April 29, 2025

Unexpected outage

Detected by Pingoru: Apr 29, 2025, 08:00 AM UTC
Resolved: Apr 29, 2025, 08:00 AM UTC
Duration: —

Affected: Golive Cloud - AppGolive Cloud - APITime Squad CloudGolive Cloud - Email NotificationsGolive Cloud - Automations & Webhooks

Timeline · 2 updates

resolved Apr 29, 2025, 08:49 PM UTC

Golive & Time Squad were unavailable this morning for a duration of approximately 30 minutes. We are currently conducting an investigation to identify the root cause.
postmortem May 01, 2025, 01:35 PM UTC

**After a thorough analysis, we identified that one of our components had reached the maximum number of database connections it was allowed to establish.** As traffic continued to grow, our health check system marked the component as unavailable and automatically restarted it in an attempt to restore normal operation. It took approximately 30 minutes for the component to come back online with a sufficient number of available connections to handle the load. **Remediation:** We have increased the maximum number of allowed connections for this particular component. We sincerely apologize for any inconvenience this outage may have caused. Please rest assured that we are committed to providing the best service possible.

Read the full incident report →

Critical April 17, 2025

Unexpected outage on managed database

Detected by Pingoru: Apr 17, 2025, 01:30 AM UTC
Resolved: Apr 17, 2025, 01:30 AM UTC
Duration: —

Timeline · 1 update

resolved Apr 17, 2025, 01:55 PM UTC

Golive & Time Squad were unavailable this morning for a duration of 1 hour and 10 minutes. The root cause of the issue was a problem accessing the application databases. After contacting our hosting provider, they confirmed that a network maintenance was scheduled for this morning. Traffic was supposed to be rerouted, but a configuration issue caused a routing error. We apologize for the inconvenience caused.

Read the full incident report →