Status pages

Status pages Admin application
 
Nov-15, 8:00pm EST

StatusCast engineers have been alerted to a possible performance impacting event affecting status pages and the admin application response times. This event is not impacting notification processing. We apologize for this inconvenience and will provide an update shortly. 

 
Nov-18, 2:00pm EST

All services should be fully functional and performing regularly. 

 
Nov-27, 3:00pm EST

StatusCast's engineers determined that at approximately 8:00PM EST on November 15th 2024, several of StatusCast's application servers experienced an issue that caused the response time to spike. StatusCast's infrastructure in Azure is designed to perform scaling procedures for services under duress, and for all but one of the application servers in question this was done successfully restoring the service to an acceptable level of performance.

The remaining application service did not correctly scale and stayed in a degraded state for multiple days. On November 18th engineers were alerted that some customers were still experiencing load time delays and at that point the last server was corrected. 

After this event occurred StatusCast's Devops team began an audit of all scaling procedures to ensure that all application services across our Azure operational regions adhere to a consistent scaling process and more importantly to ensure that monitoring is properly deployed to all services. 

Status pages Admin application
 
Jul-30, 9:30am EDT

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. 

 
Jul-30, 10:44am EDT

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.  

 
Jul-30, 4:47pm EDT

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. 

 
Jul-30, 6:00pm EDT

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.

 
Aug-1, 1:07pm EDT
FROM MICROSOFT:
Mitigation Statement - Azure Front Door Issues accessing a subset of Microsoft services
Tracking ID: KTY1-HW8

What happened?

Between approximately at 11:45 UTC and 19:43 UTC on 30 July 2024, a subset of customers may have experienced issues connecting to a subset of Microsoft services globally. Impacted services included Azure App Services, Application Insights, Azure IoT Central, Azure Log Search Alerts, Azure Policy, as well as the Azure portal itself and a subset of Microsoft 365 and Microsoft Purview services.

What do we know so far?

An unexpected usage spike resulted in Azure Front Door (AFD) and Azure Content Delivery Network (CDN) components performing below acceptable thresholds, leading to intermittent errors, timeout, and latency spikes. While the initial trigger event was a Distributed Denial-of-Service (DDoS) attack, which activated our DDoS protection mechanisms, initial investigations suggest that an error in the implementation of our defenses amplified the impact of the attack rather than mitigating it.

How did we respond?

Customer impact began at 11:45 UTC and we started investigating. Once the nature of the usage spike was understood, we implemented networking configuration changes to support our DDoS protection efforts, and performed failovers to alternate networking paths to provide relief. Our initial network configuration changes successfully mitigated majority of the impact by 14:10 UTC. Some customers reported less than 100% availability, which we began mitigating at around 18:00 UTC. We proceeded with an updated mitigation approach, first rolling this out across regions in Asia Pacific and Europe. After validating that this revised approach successfully eliminated the side effect impacts of the initial mitigation, we rolled it out to regions in the Americas. Failure rates returned to pre-incident levels by 19:43 UTC - after monitoring traffic and services to ensure that the issue was fully mitigated, we declared the incident mitigated at 20:48 UTC. Some downstream services took longer to recover, depending on how they were configured to use AFD and/or CDN.

What happens next?

Our team will be completing an internal retrospective to understand the incident in more detail. We will publish a Preliminary Post Incident Review (PIR) within approximately 72 hours, to share more details on what happened and how we responded. After our internal retrospective is completed, generally within 14 days, we will publish a Final Post Incident Review with any additional details and learnings. To get notified when that happens, and/or to stay informed about future Azure service issues, make sure that you configure and maintain Azure Service Health alerts – these can trigger emails, SMS, push notifications, webhooks, and more: https://aka.ms/ash-alerts. For more information on Post Incident Reviews, refer to https://aka.ms/AzurePIRs. Finally, for broader guidance on preparing for cloud incidents, refer to https://aka.ms/incidentreadiness.
Status pages Admin application
 
Apr-3, 8:19pm EDT

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

 
Apr-3, 9:03pm EDT

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.

 
Apr-5, 5:00pm EDT

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. 

Status pages Admin application Notification services Third Party Integrations Support Services
 
Apr-2, 9:00am EDT

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!

 
Jan-18, 5:45pm EST

We want to keep you fully informed about recent security enhancements on our platform, especially if you are utilizing third-party agents, bots, uptime monitors, or accessing our services through APIs with nonstandard user agents.


Recent Security Enhancements


As part of our commitment to maintaining robust digital security, we have increased the surface security of our firewall and denial of service protection services. This proactive measure is crucial to counter the significant rise in distributed denial of service (DDoS) attacks and unauthorized penetration attempts.


If you're using third-party agents, bots, uptime monitors, or APIs with nonstandard user agents, you may experience inconsistencies in accessing our services. We understand the importance of uninterrupted access to our services for your operations. If you encounter any access difficulties, please contact us immediately. Our team is ready to work closely with you to ensure any problems are swiftly resolved.


We appreciate your understanding and cooperation as we enhance our security measures. Thank you for your continued trust in our services. Together, we ensure a secure and efficient digital experience.


 
Jan-7, 8:00am EST

The StatusCast team will be performing a maintenance January 7, 8:00am EST, the estimated duration is 1h. During this period StatusCast's technical team will be required to make a DNS update to *.status.page traffic which may cause brief interruptions in connecting to StatusCast. CNAMEs will continue to work as expected during this time.  While we understand the importance of uninterrupted service, these updates are crucial to ensuring a secure and efficient environment for all our users.

We appreciate your understanding and thank you for your continued trust in our services. If you have any urgent concerns or questions related to this maintenance, please feel free to reach out to our support team at support@statuscast.com.

 
Jan-7, 9:00am EST

This maintenance has been completed.

Status pages Admin application
 
Jan-5, 10:21am EST

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. 

 
Jan-5, 11:14am EST

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

Status pages
 
Dec-31, 8:00am EST

The maintenance that was scheduled for today, December 31st at 8:00AM EST has been rescheduled for January 7th at  8:00AM EST. We apologize for any inconvenience, if you have any questions please send them to support@statuscast.com.

Status pages Admin application
 
Dec-27, 11:00am EST

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

Status pages Admin application Notification services
 
Dec-17, 8:00am EST

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.

 
Dec-17, 10:00am EST

This maintenance has been completed.