Moodle outages and problems
In the past 24 hours, 28 user reports came in for Moodle. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day.
The busiest 15-minute window had 6 reports, about 2 hours ago. That stays below our outage threshold, so it doesn't count as downtime.
Moodle in October 2026
- Problem reports in October (since 27 October)
- 28
Monthly report for October 2026
What people said was wrong in recent problem reports for Moodle, as a share of those reports:
- 78% Website
- 11% App
- 11% Login
Where Moodle problem reports come from
Recent reports came from 9 areas. The most came from around Grand Rapids, MI, Baton Rouge, LA and Detroit, MI. Share of recent reports by area, named after its biggest town:
- 22% Grand Rapids, MI
- 19% Baton Rouge, LA
- 11% Detroit, MI
- 7% Memphis, TN
- 7% Riverside, CA
- 4% Pittsburgh, PA
From 27 recent problem reports. Big cities always send the most, so reports from many places point to a widespread problem, and one area far ahead of the rest can mean a regional one. Town names: GeoNames.
Moodle problem spikes, last 30 days
Since 27 October, Moodle had no outage spikes or periods of elevated reports.
A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 27 October 2026. Monthly reports for all services
How to fix Moodle not working
Moodle is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:
Your browser tries to reach moodle.org over your own connection, right now. Nothing is sent to us or stored.
Reload and restart
Reload the page (Ctrl+F5, or Cmd+Shift+R on a Mac), or fully close the app and open it again.
Try another connection
Switch between Wi-Fi and mobile data. If it works on one and not the other, the problem is your network, not Moodle.
Update the app
Install the latest version from the App Store or Google Play. Old versions can stop connecting after a server-side change.
Common Moodle error messages
What each message means and what to try. The wording can differ a little between app versions.
-
Invalid login, please try again
- Means
- The username or password did not match an account.
- Fix
- Check Caps Lock and type the username or email exactly as the site expects. If it still fails, use the site's password reset link.
-
Your session has timed out. Please log in again.
- Means
- The login expired after the browser sat idle or the tab was closed for too long.
- Fix
- Sign in again. If it keeps happening, allow cookies for the site and keep the tab open while you work.
While Moodle is down: what to use instead
- Browser Use the browser if the installed app stalls; the course site can load there when the app itself has trouble.
- Instructor email If a deadline is close, message your instructor for the reading or assignment file so the task can move without the course page.
- Saved course files Open saved slides or readings you downloaded before the outage; that covers material already on your device.
- Google Classroom If your school also runs this class in Classroom, check its stream for the same handout or notice; use it only when you already have access.
Moodle IP address, servers and network
Checking moodle.org from our server…
How we track Moodle
The status on this page comes from user-submitted problem reports for Moodle, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Moodle, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.
When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. Moodle doesn't publish a public status page that we know of, so user reports are often the quickest sign that something is wrong on their side.