Is CVS/Aetna down right now?

Checking…

Verifying live status…

Our latest checks found CVS/Aetna responding normally. Live verification is running now.

Live latency
···
Reports · 5 min
···
Reports · 24 h
···
Verification tier
···
What's not working with CVS/Aetna?

Your report feeds the live outage-velocity detector. One click per 30 s.

Live latency (probe round-trip, ms)

User reports, last 24 hours

Outage history

last 30 days

Recent outages and issues we recorded for CVS/Aetna, based on our own checks. An episode opens on the second check that finds a problem, since a single adverse reading is not reported, and closes when a check finds the service normal again.

60 days agoToday

No problemsProblemsOutageNot monitored

···Observed uptime, 7 days
···Observed uptime, 30 days
···Episodes, last 30 days

    Comments

    Comments are hosted and moderated via Disqus. Spam is filtered automatically, readers can flag anything, and the thread loads only when you scroll to it so the rest of the page stays fast.

    Jump to comments

    How we check CVS/Aetna

    No evidence of problems with CVS/Aetna. Our last recorded check found it behaving normally. That does not rule out a fault affecting only some users or regions.

    Every check runs a four-tier cascade and stops at the first tier that gives a clear answer: CVS/Aetna's official status feed, then a direct HTTP probe, then an ICMP network ping, and finally reports from visitors. The Verification tier box above tells you which one produced the verdict you are looking at. When enough separate people report a problem for it to be well outside what CVS/Aetna normally sees, that counts as evidence too, which is how a partial fault can show here before an operator's own status page catches up.

    CVS/Aetna (cvs.com) is re-checked continuously, and this page picks up any change on its own, with no refresh needed.

    Common CVS/Aetna problems users report

    • Cannot log into member portal or mobile app
    • Claim submission or status tracking not working
    • Coverage verification and eligibility checks failing
    • Prescription refill requests timing out or rejected

    What to do when CVS/Aetna is not working

    First check the banner above. If it shows evidence of problems, the fault is most likely on CVS/Aetna's side and waiting is usually the only option. If it shows nothing wrong, clear your browser cache and cookies, try the mobile app if the website is slow, or call CVS/Aetna member services to verify your account access and check claim status by phone.

    About CVS/Aetna

    CVS/Aetna provides health insurance coverage, pharmacy benefits, and integrated healthcare services to millions of members. When their systems are down, members cannot access coverage information, submit claims, verify eligibility, or manage prescriptions through their portal and mobile app.

    Official CVS/Aetna resources

    Cross-check an incident with the company's own channels:

    Frequently asked questions

    Is CVS/Aetna down right now?

    No. Our checks are finding no problems with CVS/Aetna right now. That verdict is live, and the banner at the top of this page carries it too. We re-check CVS/Aetna continuously using its official status feed, direct network probes and reports from visitors, stopping at the first check that gives a clear answer, and the page updates itself as soon as anything changes. A green verdict does not rule out a fault affecting only some users or regions.

    What usually goes wrong with CVS/Aetna?

    The problems visitors report most often on this page are can't log in, API errors, can't connect, website / app down, no response / timing out, slow or laggy, 5xx error pages and checkout or payment. Those are the options the report button offers for CVS/Aetna, chosen for how this service actually fails rather than a generic list, and the "user reports" chart above breaks down which ones people are picking right now.

    Why is CVS/Aetna portal not loading for me when this page says it is fine?

    Our checks run from one place on the internet, so a fault limited to your region or network can be real while our probes succeed. With CVS/Aetna specifically, CVS/Aetna's member portal, claims processing backend, and pharmacy systems operate on separate infrastructure, so one region or subsystem can fail while others remain accessible. That is why this page reports what it observed rather than declaring the service healthy, and why reports from other visitors count toward the verdict.

    How do I tell whether it is CVS/Aetna or my own connection?

    For CVS/Aetna, try logging in from a different device and network, then check your claim status directly on the CVS/Aetna website rather than through email or phone. A problem that follows you across networks and devices is very unlikely to be yours.

    What should I do while CVS/Aetna is down?

    If this page shows evidence of problems, the fault is most likely on CVS/Aetna's side. Specifically: do not resubmit claims multiple times, as duplicate submissions can cause processing delays and confusion when systems recover; instead, note your submission time and contact support once service is restored. Reporting it here helps other people see they are not alone.

    How does status.buzz check CVS/Aetna?

    Continuously, around the clock. CVS/Aetna does not publish a machine-readable status feed, so we cannot read a verdict from them. We probe cvs.com directly over HTTP, fall back to an ICMP ping if that is inconclusive, and weigh reports from visitors. That means we can tell you the service is unreachable, but not what CVS/Aetna says about it. The verification tier box on this page names whichever check produced the verdict you are reading, so you can see how direct the evidence is.

    Is status.buzz affiliated with CVS/Aetna?

    No. status.buzz is an independent monitoring site operated by LuzLab LLC, with no connection to CVS/Aetna or cvs.com. It reads publicly available endpoints and status feeds, and publishes what it observed. For account or billing problems you need CVS/Aetna's own support, not us.