As of August 1st, 2024 we have removed the link to the Legacy Incident Editor from the admin portal to ensure that users maintain a unified experience and are able to take advantage of all of our latest improvements to the incident creation process.

StatusCast engineers were alerted earlier that some users were experiencing sporadic issues attempting to connect to the status page and admin portal. Our hosting provider, Microsoft Azure, has alerted us via their status page that they are experiencing some network issues globally. We will provide an update as soon as more information is available. 

Access to status pages has remained stable and Azure has updated their status indicating failover processes have been engaged to improve their service availability. StatusCast's engineers will continue to watch this closely and will post additional updates as necessary.  

StatusCast's application has continued to remain stable. Our engineers will continue to watch the system closely as Microsoft has not fully closed out the event on their side. For more specific details on Azure's issue please refer to their status page. We will provide additional updates as necessary. 

Microsoft has closed the issue on their side and StatusCast's platform continues to operate as expected. Once Microsoft has published more details on this we will provide here in the form of an RCA.

Following the acquisition by 4me, we have been preparing to integrate StatusCast’s support operations into 4me’s infrastructure. By combining our support operations with 4me’s, our customers will have the advantage of 24x7 support and the number of available representatives will almost quadruple.

To take the first step forward in officially merging these teams we will be removing the live chat option available in the admin portal starting on Friday June 7th, 2024. You can continue to be  to communicate with support through email(support@statuscast.com) or by accessing our current support portal.

In the coming months, you will notice several changes in how StatusCast's support is provided. This will involve the introduction of a new and improved support portal for tracking any change requests or issues that you have logged with support. Additionally, more tools and auditing information will be made available in the application, and there will be an increase in the help and knowledge resources accessible directly.

We are very excited to be expanding our support offering with 4me and know that it will ultimately help our community of valued customers and users!

At approximately 8:19PM EDT, StatusCast’s engineers were alerted that some status page and admin applications were inaccessible. The team identified that its hosting partner, Microsoft, was experiencing some issues in its US East region related to app services and SQL databases connections. As of 9:03PM EDT services have been restored and StatusCast’s team is currently working with Microsoft to fully investigate the incident. Once the team has completed it’s investigation we will follow up with an RCA.

At this time StatusCast should be operating fully as expected, if you continue to have any further issues please contact us at support@statuscast.com

As of 9:03PM EDT services have been restored and StatusCast’s team is currently working with Microsoft to fully investigate the incident. Once the team has completed it’s investigation we will follow up with an RCA.

In working with Microsoft, StatusCast’s team confirmed that the disruption was due to an outage with SQL Databases located in Azure’s US East region which is where StatusCast is primarily hosted: 

StatusCast itself was impacted by this outage from approximately 8:19 PM EDT and had fully recovered by 9:03 PM EDT. StatusCast’s team will continue to work closely with Microsoft to further optimize its offering to help ensure that impact of service provider outages is as minimal as possible. 

We are very excited to announce that StatusCast has been acquired by 4Me! Since 2013 we have been working hard to close the gap between service outages and those who are impacted, and this acquisition is one large step further in our journey of providing critical information to those who need it most. 

The inclusion of StatusCast's features will aid 4Me in it's mission to modernize service management for organizations. Click here to read more!

At approximately 9:38AM EST StatusCast engineers detected malicious activity targeting our services. The attack, aimed at overwhelming our service and causing disruptions, was neutralized, ensuring minimal impact on our operations by 9:49AM EST. We will continue to monitor the platform's health and will perform an in-depth investigation to the malicious activity targeted against StatusCast. 

Services continue to operate as expected. StatusCast's team will provide additional information around this event once our investigation has been fully completed. 

Earlier today StatusCast's support team received reports of users sporadically getting a 403 "Unauthorized" error when authenticating to the status page and admin portal. Engineers investigated the reports and confirmed that one server in rotation was at fault and have performed an update to resolve the issue. If you continue to receive 403 errors when authenticating please reach out to us at support@statuscast.com

The StatusCast team will be performing a maintenance on December 17, 8:00am EST, the estimated duration is 2h. We do not expect any impact to your service but in some cases there may be a brief interruption.

This maintenance has been completed.

At this time services have been restored and should be operating as normal. If you continue to have any issues please contact support@statuscast.com to open a ticket. We will follow to this event with an RCA detailing what occurred and how we will handle this moving forward. 

Describe the full incident details below:

On July 21st, 2023 at approximately 9:40 EDT StatusCast’s engineers received alerts that the application was displaying a  HTTP Error 500.30 error when attempting to access any *.status.page status page or admin portal. During this period any notifications in progress or from schedule maintenance would have continued to work as expected. Additionally, during this period anyone using StatusCast’s legacy(*.statuscast.com) version of the application was not impacted. 

Describe action taken by StatusCast to mitigate issue:

Engineers immediately began to investigate the cause of the problem. StatusCast’s service provider, Azure, indicated that it was undergoing maintenance in the region that StatusCast’s is primarily hosted on(US East). Engineers got in contact with Microsoft to confirm and to get additional insight as the issue itself was impacting the failover region(US West). During this process StatusCast deployed an additional instance to another Azure region which experienced the same errors as both East and West.

The root cause of the problem ultimately was related to Azure’s maintenance and the availability of one of StatusCast’s databases used for managing connections to the application. Leading up to the outage StatusCast’s operations team was preparing for its monthly penetration test which regularly involves a fresh test database for a reserved test application. The updated connection was not properly propagated to all of StatusCast’s application servers and traffic manager which unfortunately caused the subsequent errors. 

Once the issue had been identified StatusCast’s engineers were quickly able to restore service. StatusCast development team will be performing an emergency patch today(July 21st, 2023) to ensure that an issue like this can be caught without the application going unavailable.