Company Logo

Is there an Applicaster outage?

Applicaster status: Systems Active

Last checked: 7 minutes ago

Get notified about any outages, downtime or incidents for Applicaster and 1800+ other cloud vendors. Monitor 10 companies, for free.

Subscribe for updates

Applicaster outages and incidents

Outage and incident data over the last 30 days for Applicaster.

There have been 0 outages or incidents for Applicaster in the last 30 days.

Severity Breakdown:

Tired of searching for status updates?

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 Now

Components and Services Monitored for Applicaster

Outlogger tracks the status of these components for Xero:

Applicaster Admin CMS Active
Docs Active
Zapp Runtime APIs 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
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
Build Preprocessing Active
Localizations Active
Plugins Active
Studio Active
Styles & Assets Active
Component Status
Applicaster Admin CMS Active
Docs Active
Zapp Runtime APIs Active
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
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
Active
Build Preprocessing Active
Localizations Active
Plugins Active
Studio Active
Styles & Assets Active

Latest Applicaster outages and incidents.

View the latest incidents for Applicaster and check for official updates:

Updates:

  • Time: Feb. 13, 2024, 8:51 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Feb. 13, 2024, 8:36 p.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: Feb. 13, 2024, 7:47 p.m.
    Status: Identified
    Update: We are continuing to work on a fix for this issue.
  • Time: Feb. 13, 2024, 7:23 p.m.
    Status: Identified
    Update: We identified the issue and we are working on a solution to resolve it. Client Apps are not affected.
  • Time: Feb. 13, 2024, 6:53 p.m.
    Status: Investigating
    Update: We are currently investigating this issue.

Updates:

  • Time: Feb. 13, 2024, 8:51 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Feb. 13, 2024, 8:36 p.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: Feb. 13, 2024, 7:47 p.m.
    Status: Identified
    Update: We are continuing to work on a fix for this issue.
  • Time: Feb. 13, 2024, 7:23 p.m.
    Status: Identified
    Update: We identified the issue and we are working on a solution to resolve it. Client Apps are not affected.
  • Time: Feb. 13, 2024, 6:53 p.m.
    Status: Investigating
    Update: We are currently investigating this issue.

Updates:

  • Time: Nov. 17, 2023, 3:06 p.m.
    Status: Postmortem
    Update: 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.
  • Time: Nov. 15, 2023, 4:16 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Nov. 15, 2023, 3:07 p.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: Nov. 15, 2023, 2:55 p.m.
    Status: Identified
    Update: The issue has been identified and a fix is being implemented.
  • Time: Nov. 15, 2023, 2:23 p.m.
    Status: Investigating
    Update: We are currently investigating this issue.

Updates:

  • Time: Nov. 17, 2023, 3:06 p.m.
    Status: Postmortem
    Update: 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.
  • Time: Nov. 15, 2023, 4:16 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Nov. 15, 2023, 3:07 p.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: Nov. 15, 2023, 2:55 p.m.
    Status: Identified
    Update: The issue has been identified and a fix is being implemented.
  • Time: Nov. 15, 2023, 2:23 p.m.
    Status: Investigating
    Update: We are currently investigating this issue.

Updates:

  • Time: Oct. 30, 2023, 8:31 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Oct. 30, 2023, 8:14 p.m.
    Status: Investigating
    Update: 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.

Check the status of similar companies and alternatives to Applicaster

Hudl
Hudl

Systems Active

OutSystems
OutSystems

Systems Active

Postman
Postman

Systems Active

Mendix
Mendix

Systems Active

DigitalOcean
DigitalOcean

Issues Detected

Bandwidth
Bandwidth

Systems Active

DataRobot
DataRobot

Systems Active

Grafana Cloud
Grafana Cloud

Systems Active

SmartBear Software
SmartBear Software

Systems Active

Test IO
Test IO

Systems Active

Copado Solutions
Copado Solutions

Systems Active

CircleCI
CircleCI

Systems Active

Frequently Asked Questions - Applicaster

Is there a Applicaster outage?
The current status of Applicaster is: Systems Active
Where can I find the official status page of Applicaster?
The official status page for Applicaster is here
How can I get notified if Applicaster is down or experiencing an outage?
To get notified of any status changes to Applicaster, simply sign up to OutLogger's free monitoring service. OutLogger checks the official status of Applicaster every few minutes and will notify you of any changes. You can veiw the status of all your cloud vendors in one dashboard. Sign up here
What does Applicaster do?
Applicaster is a platform that enables content owners, OTT providers, and publishers to create and expand their streaming businesses with minimal coding.

Start monitoring now!

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.

Get Started for Free