Is DataCamp Down?

No — DataCamp is up

We cannot measure DataCamp directly — it blocks automated checks — but DataCamp's own status page currently reports no issues.

Last checked 1 hour ago · checks run every 6 hours

Official status page: https://status.datacamp.com

Why there is no uptime figure on this page

The last time we fetched DataCamp's page directly, the origin answered and turned our client away rather than serving the page. That answer tells us the origin was reachable and responding, but it is a response about our automation, not about whether DataCamp works for you.

A percentage built from those checks would measure our own access, so we do not publish one. What this page does show is each region's most recent result and DataCamp's own status feed, which you can weigh yourself.

30-day history

Sep 14 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

gru

edge reachable

A static asset loaded in 228ms. That proves the edge is up, but not that the site works.

iad

edge reachable

A static asset loaded in 141ms. That proves the edge is up, but not that the site works.

jnb

edge reachable

A static asset loaded in 222ms. That proves the edge is up, but not that the site works.

lax

edge reachable

A static asset loaded in 130ms. That proves the edge is up, but not that the site works.

lhr

edge reachable

A static asset loaded in 102ms. That proves the edge is up, but not that the site works.

nrt

edge reachable

A static asset loaded in 379ms. That proves the edge is up, but not that the site works.

ord

edge reachable

A static asset loaded in 166ms. That proves the edge is up, but not that the site works.

sin

edge reachable

A static asset loaded in 299ms. That proves the edge is up, but not that the site works.

What DataCamp does

DataCamp teaches data science, analytics and programming through exercises that run code in the browser rather than on the learner's machine. Individuals subscribe directly and companies buy group licences, with administrators tracking team progress. Its DataLab notebooks and Sandbox give learners a working environment to write and run code without installing anything locally.

What an outage looks like

An exercise refuses to start or hangs while loading a session, so a course stalls at the moment code needs to run even though the lesson text around it renders normally. DataLab notebooks may fail to open or lose their connection part way through. Sign-in, checkout and the group administration dashboard can each fail on their own without the lessons being affected.

What to do about it

Read status.datacamp.com, which reports In-App Web Learning Experience, Mobile App, Group Admin Experience, the Datacamp.com website, Registration and Checkout, DataLab, Sandbox and the Content Authoring Tool as separate components. Match your symptom to the row rather than assuming the platform is down. If only DataLab or Sandbox is affected, courses that do not need those environments continue normally.

Is it down for everyone, or just you?

If this page says DataCamp is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

DataCamp outage FAQ

My exercise will not start but the lesson text loads. Is DataCamp down?

That split is characteristic. DataCamp reports the In-App Web Learning Experience, DataLab and Sandbox as components separate from the Datacamp.com website, and running your code needs a session on the environment rather than just the page. A lesson that renders while its exercise hangs points at the environment rows. Check those on status.datacamp.com before you retry the exercise repeatedly.

Will I lose my course progress or my streak during an outage?

Completed exercises that were recorded before an incident remain recorded. The risk is work in progress: an exercise that never successfully submitted may not count, and a session that dropped mid-exercise can need repeating. DataCamp does not publish a guarantee covering every failure mode, so if a streak or a deadline matters to you, note the incident window and raise it with support rather than assuming either outcome.

Does the mobile app work when the website is down?

Sometimes, because DataCamp reports Mobile App as its own component separate from the web learning experience. If the web row is affected and the mobile row is not, the app is worth trying. The reverse also happens. Neither is a general fallback for the other, though, since exercises that need a code environment depend on the same DataLab and Sandbox rows in both places.

I am an administrator and cannot see my team's progress. Is that the same outage?

Not necessarily. Group Admin Experience is a separate component from the learning experience itself, so reporting and licence management can fail while your team continues working through courses without noticing anything. Check that specific row. If only the admin row is affected, there is nothing your learners need to do and progress continues to be recorded normally.

Is it DataCamp or my browser?

Compare scope. A browser extension, an ad blocker or a corporate proxy blocking the code environment affects one person and usually one machine, and the same account often works elsewhere. A DataCamp incident affects everyone at once and shows on the status page. Try a different network or a private window before concluding either way, since code environments are the part most often blocked locally.

How we measure this

We request DataCamp's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where DataCamp publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it — and when DataCamp blocks our checks entirely, we report the vendor's own status directly.

Get alerted when DataCamp goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required