Jump to content

Unable to access HB service due to an issue with application subscription [RESOLVED]


nasimg
Message added by Victor

We are investigating an issue affecting multiple instances showing incorrect (0) app subscriptions.

We have identified the issue and working to have a fix deployed.

The fix has now been deployed in all affected instances.

Please follow https://status.hornbill.com/ for updates

Recommended Posts

  • Victor changed the title to Unable to access HB service due to an issue with application subscription [RESOLVED]
1 minute ago, Victor said:

@all

The fix has now been deployed in most of the affected instances and the issue should be resolved. Please let us know if not or any other issues.

Hello - Could we please be added to the queue if not already, my colleague Colin Chalmers did post earlier.
 

Thanks

Link to comment
Share on other sites

  • Victor unpinned and unfeatured this topic
Guest Paul Davis

The RCA for this issue is as follows:

Around 12:30 BST on Wednesday last week, a small number of Hornbill customers were impacted by an issue that left them without access to Hornbill Service Manager for up to three hours. Full service was restored to those customers, and a fix has since been deployed to prevent any further occurrence of this issue. The issue was not caused by any application or platform update, but was the result of a pre-existing problem with our SaaS configuration management system.

The issue was ultimately identified as being caused by incorrect handling of a database communication error for a particular part of our SaaS configuration management system. This led to incorrect subscription values being applied to a small number of instances in our UK data center.

This issue caused significant problems for customers over an extended period of time and we sincerely apologize for the temporary loss of service. Although the number of customers impacted was small and whilst outages of this nature are very rare, we recognize Hornbill fell short of the high standards we set ourselves. A Lesson Learnt Review is always conducted after major incidents of this kind and in this instance, we have already made changes to ensure this could not happen again, and we are working on further improvements that will make this particular area even more robust in the future.

Once again, we are sorry for the inconvenience caused to those affected.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...