BEMODEM - Cmdr - Notice history

The issue has been resolved by Amazon and the cited root cause is internet connectivity at their US-WEST-2 facility. We'll monitor closely and as mentioned in an earlier update, leave our secondary synthetics layer as primary until we see that the primary layer is stable for a period of 24hrs or, suffer a similar outage requiring a fail over to our 3rd layer.

This decision does not impact your coverage as a customer or performance of our scripts - our systems are designed with this functionality to keep you covered during exactly this scenario.

We've also confirmed PagerDuty is back up and running for those using it as their central incident management tool.

During a closer look, we've determined out incident management platform is partially impacted. Though we're still able to escalate, assign, and acknowledge incidents, some users are unable to open the PagerDuty App or website.

If you use a different incident management platform, you're unimpacted. Those using PagerDuty will still receive text, email, and phone call notifications but push notifications are currently unavailable.

We believe this to be tied to the same AWS outage impacting our primary tier of synthetics and will advise once we've seen improvement.

If your organization is using a Cmdr Status page from BEMODEM, this is still working as designed and will accurately reflect and alert on your system health.

The issue in out primary synthetic engine has been restored and all impacted scripts are again running here as expected.

As a reminder, impacted customer would not have noticed an issue and monitoring as a whole was never lost thanks to our tri-tiered synthetics platform. We share details on this incident for visibility but for our customers, life went on without so much as a hiccup 😎