Is Redis Down? Check the current Redis status

Redis is operational

Updated

Redis not working for you?

Monitoring Redis since April 2020. Learn more

Monitoring 5 Redis services and regions

65 incidents in 2025

Current Redis official ongoing incidents

No incidents reported in Redis's status page

IsDown pulls data from Redis's status page every few minutes and collects user-reported issues. Refresh the page to see if there are any updates.

Redis issues reported by users in the last 24 hours

This chart displays the number of user-reported issues over the past 24 hours, grouped into 20-minute intervals. It's normal to see occasional reports, which may be due to individual user issues rather than a broader problem. We only consider an issue widespread if there are multiple reports within a short timeframe.

Latest user comments about Redis problems

  • A

    Anthony

    24 days ago

    Applications not able to connect

  • N

    nic

    about 1 month ago

    cannot resolve host with curl

  • N

    Nissanka

    about 2 months ago

    https://redis.io/ is not working

  • J

    Joe

    2 months ago

    https://download.redis.io/ is down

  • K

    kotesh

    6 months ago

    0% [Connecting to packages.redis.io] struck here while trying to do update using sudo apt update

  • S

    Simone

    9 months ago

    EAI_AGAIN error from node service, other endpoints are reachable but redislabs no

  • T

    Tom

    10 months ago

    One of my databases is not loading

  • S

    Simone

    12 months ago

    Temporary failure in name resolution

  • A

    A

    12 months ago

    redis.io is failing to load in the login page making it impossible to get into the service.

  • C

    Chris

    12 months ago

    getaddrinfo connecting to redislabs via heroku elements install

  • P

    Pratik

    12 months ago

    rror 11001 connecting to redis getaddrinfo failed.

  • L

    Lucien

    about 1 year ago

    heroku addons:create rediscloud, doesn't create a redis instance.

  • W

    Wojciech

    about 1 year ago

    http://cloud.redislabs.com doesn't work and my database is not connecting

  • 1

    1AL

    over 1 year ago

    Heroku add-on for Redis Cloud is not connecting.

  • P

    Praveenkannan

    over 1 year ago

    we have down time in heroku

  • J

    J

    over 1 year ago

    Intermittent failures connecting to urls

  • J

    Julio

    over 1 year ago

    Temporary failure in name resolution

Redis outage history

IsDown has tracked 6563 incidents since started monitoring Redis status in April 2020.

  • Mar 12 2025

    4 days ago · lasted 8 minutes

    We are currently investigating connectivity issues to some resources that have the following pattern in their endpoint: cls-prod33 More details

  • Mar 12 2025

    5 days ago · lasted about 2 hours

    Service maintenance applies to all of the resources with the following pattern in their endpoint : c1 More details

  • Mar 12 2025

    5 days ago · lasted about 1 hour

    Service maintenance applies to all of the resources with the following pattern in their endpoint : c327 More details

  • Apr 2020 ...
    IsDown started monitoring Redis status

    We've tracked and collected 6563 incidents since started monitoring Redis status

Sign up and check all outage history

Redis outages in the last 30 days

Number of Incidents

37 issues

Last incident

4 days ago

Having problems with Redis? What can you do?

  1. First, stay calm.

    • We know it's stressful when Redis is down, but running around is not going to fix it.
    • Remember that it's normal for services to go down sometimes. It can be for a number of reasons, from maintenance to unexpected issues.
  2. Make a quick evaluation of the impact

    • Try to evaluate the impact of the outage on your business. Is it impacting a majority of your users or just a few?
    • Did Redis already acknowledge the issue? And published a status update? (You can find it in the top of the page or in Redis status page)
    • If not, understand if other users are also experiencing issues. You can also check this information on the top of the page.
  3. Communicate with your team and users quickly

    • If Redis is having problems and impacting your business, it's important to keep your team and users informed.
    • Share this page with your team, so you can start incident response procedures. No need for everyone to go around searching for information. Create a post or a specific channel in your internal communication tools (Slack, Teams, Google Chat, etc.) so you can aggregate all the information in one place.
    • If you have a status page, create a status update to inform your users about the issue. This way they know what's going on and you can avoid a flow of support requests overburding your team.
  4. Understand the root cause

    • After the first communication, let's move on to the next step. Do a more thorough investigation to understand the root cause of the issue and impact.
    • Reach out to the service provider to understand if they are aware of the issue and if they are already working on it. You can reach them in their support channels, or their social media channels if they have any.
  5. Is there any mitigation for the issue?

    • Understand if there are workarounds or mitigations for the issue. Can you use a different provider? Is the switch easy to do? Talk with your team to understand the best course of action.
    • Need to wait on the service provider to fix the issue? Understand if there is a timeline for the fix. Adapt your communication with your team and users to the situation. It's very important to keep everyone informed.
  6. Service has recovered?

    • Continue to monitor the situation. A lot of times, the service can see a brief recovery and declare the issue as resolved, but it can come back. Keep monitor for some time to make sure it's really resolved.
  7. Post-incident analysis

    • Once the issue is resolved, it's important to do a post-incident analysis. Understand what went wrong and if it's possible or needed to do something to prevent it from happening again.
    • Sometimes if it's a critical dependency, you might need to have a backup plan in place to avoid a similar issue.
  8. Prepare for the next incident, because it will happen again

    • Start monitoring your dependencies. Sign up to IsDown and aggregate all your dependencies status in one place.
    • Nowadays, it's very common to have a lot of dependencies, and keeping an eye on them is not an easy task. IsDown can help you with that, by monitoring them for you and alerting you if they are having issues, and create status pages to communicate with your team and users.
Official Status Pages + User Reports

Get notified immediately when third-party services go down

Get instant alerts when your critical services go down. One dashboard to monitor all your vendors' status pages.

Start Your Free Trial
14-day free trial No credit card required Cancel anytime

Check Redis components, services, or regions current status in real-time

Get notified immediately when third-party services go down

Get instant alerts when your cloud vendors experience downtime. Create an internal status page to keep your team in the loop and minimize the impact of service disruptions.

Start Free Trial 14-day free trial · No credit card required · 3200+ cloud vendors available

Check the status of Redis alternatives & related services

Render OK
8 incidents in the last 30 days
Compare Redis vs. Render
Vultr MINOR
3 incidents in the last 30 days
Compare Redis vs. Vultr
Vercel OK
8 incidents in the last 30 days
Compare Redis vs. Vercel
Fly.io MINOR
5 incidents in the last 30 days
Compare Redis vs. Fly.io
Heroku OK
4 incidents in the last 30 days
Compare Redis vs. Heroku
Azure OK
9 incidents in the last 30 days
Compare Redis vs. Azure
5 incidents in the last 30 days
Compare Redis vs. Google Cloud
AWS OK
4 incidents in the last 30 days
Compare Redis vs. AWS
Netlify OK
8 incidents in the last 30 days
Compare Redis vs. Netlify
5 incidents in the last 30 days
Compare Redis vs. DigitalOcean
Linode OK
15 incidents in the last 30 days
Compare Redis vs. Linode
2 incidents in the last 30 days
Compare Redis vs. Snowflake
47 incidents in the last 30 days
Compare Redis vs. Hostinger
Railway OK
9 incidents in the last 30 days
Compare Redis vs. Railway

Stay informed about Redis status changes

IsDown offers an easy way to monitor Redis with maximum flexibility

Major Outages Notifications

IsDown monitors Redis for major outages. A major outage is when Redis experiences a critical issue that severely affects one or more services/regions. When Redis marks an incident as a major outage, IsDown updates its internal status, the customer status page and dashboard. Depending on the customer settings, IsDown will also send notifications.

Minor Outages Notifications

IsDown monitors Redis status page for minor outages. A minor outage is when Redis experiences a small issue affecting a small percentage of its customer's applications. An example is the performance degradation of an application. When a minor outage occurs, IsDown updates its internal status and shares that information on the customer status page. Depending on the customer settings, IsDown will also send notifications.

Outage Details

IsDown collects all information from the outages published in Redis status page to provide the most accurate information. If available, we gather the title, description, time of the outage, status, and outage updates. Another important piece of information is the affected services/regions which we use to filter the notifications that impact your business.

Maintenance Feed

Redis publishes scheduled maintenance events on their status page. IsDown collects all the information for each event and creates a feed that people can follow to ensure they are not surprised by unexpected downtime or problems. We also send the feed in our weekly report, alerting the next maintenances that will take place.

Component Filtering

IsDown monitors Redis and all their 5 components that can be affected by an outage. IsDown allows you to filter the notifications and status page alerts based on the components you care about. For example, you can choose which components or regions affect your business and filter out all other outages. This way you avoid alert fatigue in your team.

Early Outage Indicators

Redis and other vendors don’t always report outages on time. Our crowdsourced status platform helps you stay ahead of outages. Users report issues and outages, sharing details on what problems they are facing. We use that info to provide early signs of outages. This way, even without an official update, you can stay ahead of possible problems.

Frequently Asked Questions

Is Redis down today?

Redis isn't down. You can check Redis status and incident details on the top of the page. IsDown continuously monitors Redis official status page every few minutes. In the last 24 hours, there were 0 outages reported.

What is the current Redis status?

Redis is currently operational. You can check Redis status and incident details on the top of the page. The status is updated in almost real-time, and you can see the latest outages and issues affecting customers.

Is there a Redis outage now?

No, there is no ongoing official outage. Check on the top of the page if there are any reported problems by other users.

Is Redis slow today?

Currently there's no report of Redis being slow. Check on the top of the page if there are any reported problems by other users.

How are Redis outages detected?

IsDown monitors the Redis official status page every few minutes. We also get reports from users like you. If there are enough reports about an outage, we'll show it on the top of the page.

When was the last Redis outage?

Redis last outage was on March 12, 2025 with the title "Connection Issues"

Redis not working for you? How do I know if Redis is down?

  • Check on the top of the page if there are any reported problems by other users.
  • Find their support at their official website.
  • Find their support contact at their official status page.

How can I check Redis status and outages?

Why use IsDown to monitor Redis instead of the official status page?

Because IsDown is a status page aggregator, which means that we aggregate the status of multiple cloud services. You can monitor Redis and all the services that impact your business. Get a dashboard with the health of all services and status updates. Set up notifications via Slack, Datadog, PagerDuty, and more, when a service you monitor has issues or when maintenances are scheduled.

How IsDown compares to DownDetector?

IsDown and DownDetector help users determine if a service is having problems. The big difference is that IsDown is a status page aggregator. IsDown monitors a service's official status page to give our customers a more reliable source of information. The integration allows us to provide more details about the outage, like incident title, description, updates, and the parts of the affected service. Additionally, users can create internal status pages and set up notifications for all their third-party services.

“Very happy with isDown. Setting up and managing the monitoring is straightforward. The customer support team has been excellent, always quick to answer questions and provide assistance.
I definitely recommend IsDown.

We play well with others

Get Redis outage notifications where you need them the most

The data and notifications you need, in the tools you already use.

Latest Articles from our Blog

See all the blog articles

Never again lose time looking in the wrong place

14-day free trial · No credit card required · No code required