- Ably FAQs
- Account billing and packages
- Packages & Pricing
-
Account billing and packages
-
General
-
Realtime API and client libraries
-
Troubleshooting
-
Channels
-
REST API and client libraries
-
Ably error codes
-
Account and app setup and configuration
-
Ably architecture, transports, and security
-
Performance and Redundancy
-
Push Notifications
-
Reactor Queues, Events and Firehose
-
Migrating to Ably from an existing service
-
API Streamer
-
Connections
-
Latest advice
I've hit a connection limit, what does this mean?
This means you've had enough concurrent connections to surpass your limit or hit a warning. Connections are counted for each instance of the Ably library connected to Ably.
There are three types of connection limits you can hit:
- connections.warning - when you reach 80% of your pre-paid quota.
- connections.soft - when your pre-paid quota has been exceeded. You may then be charged at the base rate ($12.50 p/thousand) for exceeding your connection limit for extended periods of time.
- connections.hard - when the hard limit on the account has been exceeded. You will not be able to create new connections until you're below your hard limit.
If you need the ability to have more connections, we recommend you upgrade your account.
If you're certain you shouldn't be hitting your connections limit, make sure you're not instantiating an Ably library multiple times.