Is Applicaster Down Right Now? Check if there is a current outage ongoing.

Applicaster is currently Operational

Last checked 2025-06-14T13:37:48.970Z from Applicaster's official status page

Historical record of incidents for Applicaster

Feb 13, 2024

Report: "Major outage - Zapp CMS"

Last update 2024-02-13T20:51:09.630Z

resolved2024-02-13T20:51:09.616Z

This incident has been resolved.

monitoring2024-02-13T20:36:21.087Z

A fix has been implemented and we are monitoring the results.

identified2024-02-13T19:47:13.423Z

We are continuing to work on a fix for this issue.

identified2024-02-13T19:23:36.895Z

We identified the issue and we are working on a solution to resolve it. Client Apps are not affected.

investigating2024-02-13T18:53:36.560Z

We are currently investigating this issue.

Nov 17, 2023

Report: "Processing actions fails (layouts changes)"

Last update 2023-11-17T15:12:58.326Z

postmortem2023-11-17T15:06:31.234Z

There was a leak between the new cluster \(private\) that was created. Sidekiq \(bg jobs processing\) is connected to the same Redis DB on all clusters. The new cluster didn’t have the Zapp app running properly \(pods\) and therefore jobs weren’t processing Once we found the issue, we downscaled the new private cluster to 0, increased node size on AWS console, and restarted the pods on the prod-us1 cluster \(the running production cluster\). In order to prevent it in the future, we need to make sure there is no running nodes on redundant clusters, only the active one. In addition, we should consider Redis DB separation between clusters, although this could cause losing some of the running processes.

resolved2023-11-15T16:16:00.780Z

This incident has been resolved.

monitoring2023-11-15T15:07:15.995Z

A fix has been implemented and we are monitoring the results.

identified2023-11-15T14:55:13.797Z

The issue has been identified and a fix is being implemented.

investigating2023-11-15T14:23:57.339Z

We are currently investigating this issue.

Oct 30, 2023

Report: "Issues editing App Versions"

Last update 2023-10-30T20:31:04.793Z

resolved2023-10-30T20:31:04.776Z

This incident has been resolved.

investigating2023-10-30T20:14:53.000Z

We are investigating an issue where NPM registry API cannot be reached due to a server error. This issue has no impact on end users apps.

Jul 20, 2022

Report: "Layout changes issues"

Last update 2022-07-20T01:25:06.806Z

resolved2022-07-19T22:15:31.000Z

This incident has been resolved.

monitoring2022-07-19T22:03:14.463Z

A fix has been implemented and we are monitoring the results.

identified2022-07-19T21:01:38.439Z

We are continuing to work on a fix for this issue.

identified2022-07-19T18:57:57.104Z

We are currently seeing issues effecting apps when doing a changes to layout. We are working on a fix.

Feb 24, 2022

Report: "Authentication failures and Zapp fails to load"

Last update 2022-02-24T18:34:16.718Z

resolved2022-02-24T18:34:16.701Z

This incident has been resolved.

monitoring2022-02-24T17:16:48.128Z

Heroku services are starting to act as expected, we will keep on monitoring.

investigating2022-02-24T16:57:49.000Z

Zapp authentication and login is impacted by a major outage on Heroku: https://status.heroku.com/incidents/2402

Apr 2, 2020

Report: "Build process outage"

Last update 2020-04-02T21:44:10.044Z

postmortem2020-04-02T21:43:48.700Z

Third party services are running properly. We will keep on monitoring.

resolved2020-04-02T21:40:13.300Z

This incident has been resolved.

investigating2020-04-02T21:18:36.759Z

We see recovery on third party services (Github, Circleci), we keep on monitoring.

investigating2020-04-02T20:59:46.435Z

Few third party services we rely on are currently in major outage (Github, CircleCi)