I would rate the stability an eight out of ten. It has good stability. 

It's stable.

I would rate its stability capabilities ten out of ten.

It's very stable. Previous versions were not as stable, but now, starting from 2018, I can see that the product is very stable. I would rate it a ten out of ten.

IBM API Connect is a stable solution.

Stability-wise, I rate the solution a seven to eight out of ten.

IBM API Connect is a stable solution. It's used in government services, and my team barely receives calls about the solution. IBM API Connect is also used in major banks here in Jordan, and it's stable. There are no complaints about it.

I find the stability of IBM API Connect to be fine.

It is a stable solution.

The solution provides high stability. I would rate it nine out of ten.

We are having some issues with the stability of the solution.

I rate the stability of IBM API Connect a seven out of ten.

The stability of the solution is good.

Stability-wise, I rate the solution an eight out of ten.

Given the fact that it's not operationalized, I cannot really comment too well on the stability because we haven't really had to worry about the stability yet. I'm not really in a place to know. I've heard rumors that there are occasionally some issues related to how it maintains connections with its other pair, but I don't know enough to know.

The newer versions, from 2018 forwards, are quite stable.

The stability has been fine. We've found it to be very stable. There are no bugs or glitches. It doesn't crash and freeze. In the past versions, stability was a bit of an issue, however, in the latest version, we have found it to be much better and much more reliable. We are satisfied with it so far. 

This is a stable solution. 

There have been some internal issues within the product that have caused instability.

It's quite stable.

It is a stable product. I rate the stability an eight out of ten.

The solution has a modern cloud and it has been stable and reliable. We have not had any breaches of security.

It's very stable.

We are using it for the last six months, so we haven't yet gone into production. We are hoping it will be a very stable solution.

This solution is stable. 

The new version is very unstable. There are a lot of fix patches and a host of known errors. They've started it on their website. So we're waiting for some of that to stabilize before we continue, but we're working around that as far as possible. The old version 5 was quite stable. We were able to put a lot of business commercial APIs in place. It is actually being monetized, and the guys are making money out of that. 

I would rate the stability a seven to eight out of ten; it's still evolving. There are features which are missing, that are there in the other similar product from another vendor. Overall, it's good.

The stability is good. 

We just started. We are converting from the old infrastructure to the new API Connect. We started maybe a year ago, but we'll see the results maybe in six months.

This is a strong and stable solution. 

In regards to the stability, we are new to it, so it is OK right now. We haven't put much into it yet.

API Connect is reliable.

It's a very stable solution.

In terms of stability, we are still prototyping the product. We have the older version, which is now stable, but the current version or the new version, that we are still prototyping, is still not 100% stable.

Stability is not good.

The stability has been very good. It doesn't crash or freeze. There are no bugs. From a performance perspective, it's reliable.

As far as I know, there haven't been any issues with the stability of the solution.

Stability has still not matured. We are still growing with the industry. We will find out after some time how it is going. But, as of now, it's stable.

The solution is very stable.

IBM API management did have several stability issues, where working in different tabs in browser cause issues saving the configuration changes.

Also IBM API management is very slow and its inbuilt test tool is crappy as it takes around 1.5-2 mins to test any API after configuration changes.

IBM API connect is far better but we still haven't stress/load tested apis,so wouldn't comment on it.

One example of instability, We lost the old configuration during firmware upgrade of API connect.

Stability has improved greatly with the latest releases. There were some struggles in the beginning. There were some components that were not stable. They weren't behaving consistently through environments when we moved stuff from development to demo to prime. I think core functionality is pretty stable but there are things on the outskirts that weren't so stable.

There are some issues with API Connect's stability, with parts going down abruptly sometimes. Its stability doesn't compare well to Epigee or Kong API, and I would only rate it seven out of ten.

In terms of stability, I think it needs some improvement when it comes to externalizing the analytics data. The analytics collected with this product are part of the product database. If we could push the analytics data to an external data source, the customers could use it for historical purposes.

No issues encountered.

It is stable.

In general, stability is good, although there are very frequent patches that are required, and that is annoying.

IBM API Connect is stable.

The system has not been put through real stress. We use it for our third-party APIs and the connection and so that's not too much stress. I can't give a metrics on its stability. And then at the point of setup, we were already getting a bit of redundancy.

Current versions are stable. However, a few minor issues were observed during the early stages of product evolution.

No issues encountered.

API Connect's stability was okay. We ran it on top of the Kubernetes cluster, so it wasn't a standalone service. In the worst-case scenario, API Connect couldn't stay online if all the containers went down. We had to restart all the services. We shut down all the containers automatically one by one. That was the only problem. It didn't happen often— maybe three or four times in two years — but it was still somewhat problematic. API Connect is not fully cloud-native in that sense.

There are issues with upgrading in the cloud version. The cloud version is extremely buggy. We prefer to use the on-premise version.

IBM API Connect is a stable solution.

Actually, we're in production for demo purposes, so I really can't speak to this. So far, we've had no issues.

IBM API Connect is based on data power and, from a security and stability point of view, it's good. However, we use a 2018 version that has a stability issue. The one problem we encounter is that the syncing between different components of API management is not happening. We had to get the administrator to do some locking, unlocking, things like that. Most of the time, I deploy it, everything is sorted, and the transactions are going through, but at times, we have issues with publishing the APIs. So I sometimes question the stability. 

We had one problem with the security and data resources early on when beginning to use the product. The problem was mostly due to the fact that when we started using the product, we did not have any knowledge of its requirements or experience using it.  

It is quite stable. We've not had any problem. It has made for a good buy because we are finding that other companies that have similar set ups go down maybe once a month.

Our transactions has been escalating. We're doing an average of about 1.2 million transactions every week now, and it's stable.

I found the solution to be stable.

No issues with stability.

I haven't had any issues with the stability. There are around 1,000 users using IBM API in my company. 

We have no issues.

It was a fairly new product so there was, so it took a year or so to really stabilize. But now I'm happy with the performance.