This page is to log CENTRL's outage history and details. If CENTRL has experienced any performance issues, it will be noted here.
For other information or to report a problem, please submit a ticket a New Support Request at https://supportcenter.
Outage History
October 1, 2023
Details:
At 9:15 am PT, there was an outage on the web.oncentrl.com website for about 66 minutes. During this time, the website was available. However, users were not able to log in to the application. Any API integrations or other calls to the APIs would have failed also. The outage was resolved at 10:22 am PT.
April 19, 2023
Details:
At 5:09 pm PT, there was an outage on the web.oncentrl.com website for about 17 minutes. During this time users were not able to login to the application. The outage was resolved at 5:26 pm PT and services returned to normal.
March 06, 2023
Details:
One of our content delivery partners is experiencing a network issue which has had intermittent impact to the application throughout the day. At certain times the website will not respond, again this is intermittent and will not affect all users. Our operations team has implemented a workaround for the problem which will give full access to the site again.
Update: This issue was fully resolved at 12:11 PM PT.
Tracking for the issue with the vendor and status can be seen here.
February 10, 2022
Details:
At 1:40 pm PT, there was a 26 minute outage on the auth.oncentrl.com and app.oncentrl.com websites. During this time users were not able to login to the application and if they were logged in would have been logged out. Web Services clients likewise would have seen issues in authentication and completing APIs as they would hang until there was a timeout. This outage was caused by our database servers becoming extremely slow in responding. The outage was resolved at 2:06 pm PT and services returned to normal.
December 24, 2020
Details:
At 11:29 am PT, there was a 34 minute outage on the auth.oncentrl.com and app.oncentrl.com websites. During this time users were not able to login to the application and if they were logged in would have been logged out. Web Services clients likewise would have seen issues in authentication and completing APIs as they would hang until there was a timeout. This outage was caused due to the changes of IP addresses in the infrastructure and certain load balancing rules did not honor the new IPs, this was taken care of manually and then also a patch was given so it will not happen in the future. The outage was resolved at 12:03 pm PT and services returned to normal.