Opened on Wednesday 10th February 2021, last updated
Resolved — AWS has resolved the core issue in one of the availability zones in use by Voci licensing and we have reverted our DNS to the us-east-1 endpoint(s). We expect Amazon to restore the additional availability zone shortly, but currently all services are up and available via the standard static IP endpoint(s). If any Voci services are not behaving as expected, please restart the service/server and contact firstname.lastname@example.org if problems persist.
Monitoring — Currently, the Voci licensing service is up and operational, but the AWS outage has forced us to redirect our DNS for license.vocitec.com to endpoints in the us-est-2. If any affected hosts cannot currently resolve to the us-east-2 endpoint, we recommend clearing any DNS caches and/or changing name resolution to a non-cached server. Name resolution should look like the following to avoid licensing errors/failures: $ host license.vocitec.com license.vocitec.com is an alias for ls-dr-us-east-2-ae226488f64c4f50.elb.us-east-2.amazonaws.com. ls-dr-us-east-2-ae226488f64c4f50.elb.us-east-2.amazonaws.com has address 188.8.131.52 ls-dr-us-east-2-ae226488f64c4f50.elb.us-east-2.amazonaws.com has address 184.108.40.206 Public nameservers known to currently be returning non-cached/accurate responses include: 220.127.116.11 (CloudFlare) 18.104.22.168 (CloudFlare) 22.214.171.124 (Google) 126.96.36.199 (Google) Additional workarounds include temporarily adding /etc/hosts entries to resolve license.vocitec.com for 188.8.131.52 and 184.108.40.206
Monitoring — UPDATE FROM AWS - 12:45 PM PST We continue to work to identify the root cause of the event resulting in connectivity issues for some Network Load Balancers within the US-EAST-1 Region. Some Network Load Balancers in USE1-AZ2, USE1-AZ4, and USE1-AZ5 are experiencing connection issues for TLS (SSL) requests. Non-TLS (SSL) requests are not affected by this issue. We are also experiencing some delays in the provisioning of new Network Load Balancers and registration of new targets behind existing Network Load Balancers. We have identified the underlying subsystems responsible for this issue and continue to work towards root cause and resolution.
Monitoring — UPDATE FROM AWS - 12:19 PM PST We are investigating increased connectivity issues for Network Load Balancers within the US-EAST-1 Region