Maintenance · over 1 year ago · lasted about 1 hour
Due to an upwards trend in DB backend usage, we are proactively upgrading the underlying hardware. Also, we are enabling some elasticity features so the resources can better scale with the load from here onwards. The expected service interruption is less than a minute.
Maintenance · over 1 year ago · lasted 27 days
We are currently remediating the issue. The service is operational in maintenance mode, however, one or two brief interruptions are expected.
Major · over 1 year ago · lasted 2 months
The planned upgrade from RDS 9.6 to 13.3 is taking longer than initially expected. The reason is identified and we are working to get Central up and running again ASAP. The estimated time of resolution and full functionality restoration is 35 minutes.
Minor · over 1 year ago · lasted 2 months
The planned upgrade from RDS 9.6 to 13.3 is taking longer than initially expected. The reason is identified and we are working to get Central up and running again ASAP.
Minor · over 2 years ago · lasted about 1 year
During the deployment of static I.P. addresses for Amplify Central (as noted at the URL below), our engineers encountered unexpected issues with our DNS service which caused the Amplify Central administration interface and Unified Catalog (U.S. only) to to be unreachable. Our engineers worked to resolve the issue and service was restored after approximately 39 minutes. Notification of Static I.P. addresses: https://status.axway.com/incidents/jmy8d6fzwdlh
Minor · almost 4 years ago · lasted over 2 years
On Saturday, September 28th, Axway upgraded the access management capabilities of the AMPLIFY Platform in the production environment. During that upgrade, at 10:03 AM PDT, a regression happened which the product team promptly stopped with a hot fix (note: a patch is going in shortly to resolve the problem more permanently). On Monday, September 30th, at 9:40 AM PDT, it was discovered that the regression had caused a few single-user organizations to lose at least part of their data. The same day, at 4:40 AM PDT, all data had been fully restored and the incident had been marked as resolved. Axway will be contacting each one of the organizations affected by this temporary loss of data. Already, we want to apologize to these customers for the inconvenience or disruption that this may have caused. The product team systematically conducts full regression tests before any upgrade; this time, there was an edge case flow that we missed in our testing and that led to that incident in produc...
Get notified only when an outage impacts a certain component.
SaaS rules the world, and all teams depend on them to do their most productive work. IsDown helps you monitor all your cloud services, so you can focus on what matters.
Try it out! How much time you'll save your team, by having the outages information close to them?