Know when CDC goes offline or comes back
Choose how long to watch. We email only when the status changes.
cdc.gov · Reference
CDC has recorded 100.0% uptime over the last 17 days, with no outage. It answers our checks in 119 ms on average.
CDC answered our last automated check normally, 12 minutes ago. If it is not working for you, the problem is most likely local - Your connection, your DNS resolver, a cached page, or an extension.
Choose how long to watch. We email only when the status changes.
Check any website now, or jump straight to a similar service.
See all referenceCounted in 15-minute buckets from reports submitted on this site. This is a user signal - A tall bar means people are complaining, not that our check failed.
No reports in the last 24 hours.
If CDC is not working for you, tell us and the chart starts here.
The last 24 checks of https://www.cdc.gov/index.html from our network. Bar height is the response time; the tallest bar is the slowest.
Tell us what is not working. Reports go straight onto the 24-hour chart above and help other people see a problem before any company admits to one. 0 reports in the last 24 hours.
CDC sits at number 238 on the worldwide traffic ranking with about 22.4M organic visits a month, and the address it resolves to belongs to Akamai Technologies, Inc. CDC publishes 4 addresses for the name, reachable over IPv6 as well as IPv4. Reverse DNS for the address behind cdc.gov resolves to a23-48-224-207.deploy.static.akamaitechnologies.com.
Name service for cdc.gov is operated by Akamai, with the registration held through get.gov, and dated to 1997. Cdc.gov signs its zone with DNSSEC and sends an HSTS header, so browsers refuse it over plain HTTP. The certificate cdc.gov presented to us was issued by DigiCert Inc, covering 2 names, with 148 days left on it at first check, and negotiated over TLSv1.3. Our first check of cdc.gov returned HTTP 200 in 114 ms, of which 8 ms was name resolution and 1 ms the connection. The request to cdc.gov passed through 2 redirects before it settled on https://www.cdc.gov/index.html. Those figures are the baseline this page measures cdc.gov against from now on, every 20 minutes.
Our last check reached cdc.gov normally, from a different network, resolver and route than yours. If it is broken for you, the fault is most likely local or too narrow for a single probe to see. Our next automated check runs within 20 minutes and this page updates with it.
Try a search-engine cached copy. Reference content changes slowly, so a cached version is usually just as good for what you needed.
Pages load from cache while anything dynamic - search, editing, the API - fails. Because so much of these sites is cacheable, partial availability is the normal presentation. The rest of the steps, and why this category breaks the way it does, are on our reference status page, with more background in how we record outage history.
Over the last 30 days CDC ranks 16 of 16 reference services we monitor, measured on recorded uptime. The category averages 100.0%, and CDC sits at 100.0%. The steadiest in this group is IMDb.
On speed, CDC answers our checks in about 119 ms against a category average of 481 ms - Faster than its peers. Response time is not availability, but a service drifting well above its own normal is often the first sign of trouble.
Across the most recent 24 checks, the quickest response was 60 ms and the slowest 202 ms, against a 30-day average of 119 ms. The chart above plots each one, so a widening spread is visible before it becomes an outage.
All figures are our own measurements, taken every 20 minutes from one network. What that can and cannot see is set out in the methodology, and every reference service is listed on the category page.
Five more fields about the server behind cdc.gov.
Free, one click with Google, and nothing is posted or shared. We ask because the lookups behind this cost us real requests to other people’s servers.
Read from our last sweep of cdc.gov, not requested when you opened this page.
Who issued it, what it covers and exactly when it expires.
Free, one click with Google, and nothing is posted or shared. We ask because the lookups behind this cost us real requests to other people’s servers.
An expired certificate stops browsers loading a site entirely while the server itself stays perfectly healthy, which is why we track it beside the uptime figure.
.CDC is up and responding normally. This page is refreshed by an automated check that runs every 20 minutes from an independent network, and by reports from visitors.
Because an outage can be partial. Our check runs from one network and asks for one page. Your problem may be regional, may affect only the mobile app, or may be local to your connection, DNS resolver or browser cache.
CDC has been reachable for 100.0% of the last 17 days we have measured, with 0 seconds of recorded downtime.
CDC does not publish a public status page, which is why independent monitoring and user reports are the only external signal available during an incident.
CDC discussion
Useful comments say what broke, roughly where you are and roughly when it started - That is what turns a pile of complaints into something other people can act on. Links are shown as plain text and carry no SEO value, so there is nothing here worth spamming.