Skip to main content

Is Pearson Down?

No — Pearson is up

Reachable from all 8 checked regions

Average response time: 883ms

Last checked · checks run every 6 hours

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

Pearson uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
1063ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 13 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

13-day clean streak
Jul 19: no data
Jul 20: no data
Jul 21: no data
Jul 22: no data
Jul 23: no data
Jul 24: no data
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: 100.00% uptime, 16 checks
Aug 6: 100.00% uptime, 32 checks
Aug 7: 100.00% uptime, 32 checks
Aug 8: 100.00% uptime, 32 checks
Aug 9: 100.00% uptime, 24 checks
Aug 10: 100.00% uptime, 32 checks
Aug 11: 100.00% uptime, 32 checks
Aug 12: 100.00% uptime, 32 checks
Aug 13: 100.00% uptime, 40 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 40 checks
Aug 16: 100.00% uptime, 32 checks
Aug 17: 100.00% uptime, 24 checks
Jul 19 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.

fra
778ms
DNS 600ms TCP 1ms TLS 5ms TTFB 772ms
gru
395ms
DNS 190ms TCP 2ms TLS 8ms TTFB 381ms
iad
825ms
DNS 247ms TCP 1ms TLS 6ms TTFB 820ms
jnb
2127ms
DNS 930ms TCP 5ms TLS 15ms TTFB 2115ms
lax
951ms
DNS 327ms TCP 0ms TLS 5ms TTFB 947ms
lhr
671ms
DNS 312ms TCP 1ms TLS 6ms TTFB 662ms
nrt
1036ms
DNS 218ms TCP 1ms TLS 6ms TTFB 1031ms
ord
685ms
DNS 39ms TCP 22ms TLS 51ms TTFB 618ms
sin
376ms
DNS 75ms TCP 1ms TLS 6ms TTFB 369ms

What Pearson does

Pearson publishes course materials and runs the platforms students submit work through: MyLab, Mastering, MathXL, Revel, StatCrunch, Learning Catalytics and Pearson+. Its status page also covers English language learning, clinical assessments, school assessments, Pearson Virtual Schools and UK teaching and awarding, which is a reminder that an incident can land on an exam as easily as on homework.

What an outage looks like

A homework assignment loads but will not submit, or submits and does not register, which is the failure students notice at a deadline. MyLab and Mastering may fail to launch from a course link while the campus learning management system is healthy. Answers time out mid-attempt and the attempt is consumed. Sign-in through an institutional account can fail separately from the platform itself.

What to do about it

Check status.pearson.com, which groups the service into Higher Education Courseware, English Language Learning, Clinical Assessments, School Assessments, Pearson Virtual Schools and UK Teaching and Awarding, and shows a history grid per product covering Learning Catalytics, Mastering, MathXL, MyLab, Pearson+, Revel, StatCrunch, Pearson Interactive Labs and third-party learning management system links. Screenshot the error and the timestamp before retrying, because that is what an instructor needs to extend a deadline.

Is it down for everyone, or just you?

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

Test it yourself

Related services

Pearson outage FAQ

Will I be marked late if Pearson was down at the deadline?
That is your instructor's decision, and evidence makes it far easier for them. Take a screenshot showing the error and the time, and note what the status page reported. Pearson's status page keeps a dated history grid per product, so an incident during your attempt is verifiable after the fact. Contact the instructor before the deadline rather than after, even if you cannot submit.
Does a Pearson outage mean my whole course is down?
No. The learning management system your institution runs, whether Canvas, Blackboard or another, is a separate service from Pearson's platforms. Course pages, announcements and non-Pearson assignments generally keep working while MyLab or Mastering fails. The status page lists third-party learning management system integrations as their own row, because the link between the two can break while both sides are otherwise healthy.
Is my work saved if the platform fails mid-attempt?
It depends on the product and how far the attempt progressed. Work that reached Pearson's servers is retained; work sitting only in your browser when the session dropped generally is not. For a timed attempt the more serious risk is the attempt being consumed without a recorded submission, which usually requires an instructor to reset. Do not start a fresh attempt during an incident until you know the first one's state.
Why can't I sign in when the platform is up?
Institutional sign-in usually routes through your school's identity provider before reaching Pearson, so either side can fail. If classmates on the same campus are also blocked while the status page is green, the problem is more likely on the institution's side. If sign-in works elsewhere on campus but not for Pearson, the handoff between the two is the likelier culprit and the help desk needs to know both details.
Do Pearson outages affect exams and assessments?
They can, and the status page treats assessments seriously enough to list clinical assessments, school assessments and UK teaching and awarding as separate categories from courseware. An incident touching those affects scheduled testing rather than homework, which has a much shorter tolerance for delay. If an assessment is affected, the test centre or awarding body, not the platform, is the right place to escalate.

How we measure this

  • We request Pearson's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • 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 Pearson 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.

Get alerted when Pearson goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required