SmartLink service needs to be more robust

  • 1
  • Problem
  • Updated 1 year ago
I can see that there are a quite a number of posts and with that occasions when the SmartLink Service has been down for remote action.

If a service like SmartLink is needed for users to run remote then one would expect to have a design with uptime guarantee 99.99% isch.

So for the moment I would say we are having a bad design and I can see this as a showstopper for to promote FLEX remote usage, at least based on SmartLink-platform.

A more selfcontained solution based on VPN is probably the better option until SmartLink gets more reliable.

What is your view and/or the official statement from Flex ? 

Thank you in advance / Tilman SM0JZT
Photo of Tilman D Thulesius

Tilman D Thulesius

  • 5 Posts
  • 0 Reply Likes

Posted 1 year ago

  • 1
Photo of Michael Walker

Michael Walker, Employee

  • 1097 Posts
  • 325 Reply Likes
Official Response
Our Smart Link Service relies on Microsoft Azure to manage the authentication process.    Like you, we are a customer waiting for our services to be made available.

This is the update from Microsoft as of 15 minutes ago.  And, from my tests,  it looks like things are starting to come up, but it might be a few more hours for them to be at 100%.  Lots of boxes to restart here.

I just tested my iPhone on SmartSDR and it came right up.

PRELIMINARY ROOT CAUSE: A severe weather event, including lightning strikes, occurred near one of the South Central US datacenters. This resulted in a power voltage increase that impacted cooling systems. Automated datacenter procedures to ensure data and hardware integrity went into effect and critical hardware entered a structured power down process.
ENGINEERING STATUS: Engineers have restored access to storage resources for the majority of services, and customers should be seeing signs of recovery.  Engineers are continuing to work on any residual storage impact to fully mitigate this issue. The current mitigation workflow is outlined below:
1) Restore power to the South Central US datacenter (COMPLETED)
2) Recover software load balancers for Azure Storage scale units in South Central US (COMPLETED)
3) Recover impacted Azure Storage scale units in South Central US. (Mostly complete)
4) Recover the remaining Storage-dependent services in South Central US (Mostly complete)