Last checked: 29 seconds ago
Get notified about any outages, downtime or incidents for Applicaster and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Applicaster.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
Component | Status |
---|---|
Applicaster Admin CMS | Active |
Docs | Active |
Zapp Runtime APIs | Active |
Builds-OPS | Active |
Android Builds | Active |
Android TV Builds | Active |
Apple TV Builds | Active |
iOS Builds | Active |
LG builds | Active |
Roku Builds | Active |
Samsung TV Builds | Active |
Third Party Services | Active |
AWS | Active |
CircleCI | Active |
CircleCI CircleCI 2.0 | Active |
CircleCI macOS Builds | Active |
GitHub | Active |
Heroku | Active |
Intercom Admin notifications | Active |
npm Package installation | Active |
npm Package publishing | Active |
RedisToGo Servers | Active |
Zapp | Active |
Build Preprocessing | Active |
Localizations | Active |
Plugins | Active |
Studio | Active |
Styles & Assets | Active |
View the latest incidents for Applicaster and check for official updates:
Description: This incident has been resolved.
Status: Resolved
Impact: Major | Started At: Feb. 13, 2024, 6:53 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Major | Started At: Feb. 13, 2024, 6:53 p.m.
Description: 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.
Status: Postmortem
Impact: None | Started At: Nov. 15, 2023, 2:23 p.m.
Description: 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.
Status: Postmortem
Impact: None | Started At: Nov. 15, 2023, 2:23 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Major | Started At: Oct. 30, 2023, 8:14 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.