We recently experienced a system-wide outage that affected both developers and API providers. We have identified and solved the problem.
While the issue is resolved now, we’d like to thank you again for your patience here and apologize again for the inconvenience. All systems should be set from here! If you have any additional issues, we are on-call and here to help. Please email email@example.com or leave your comments below.
If you are interested in learning more about why this issue occurred, see below:
We host API keys and subscriptions on a Redis database and rely on a third party (RedisLabs) to access them in real-time. Last night, RedisLabs throttled our service, which caused outages on our side. The RedisLabs issue is resolved, but we are taking proactive steps to ensure that our system is not affected should another issue on their side occur. Moving forward, we are building additional fail-safe redundancies to ensure that these errors do not occur again.
Thanks for your patience today and we apologize again for this issue. We know that many of you host APIs or apps on our service and that these outages affect your business. We are taking active steps to ensure that this doesn’t happen again and look forward to any feedback that you provide about this process.
While outages like these are rare, we want to give better visibility around them. Visit our new RapidAPI status page to see any issues as they appear in real-time. We’ve built this page based on today’s incident and hope it will be helpful to you in the future.