1. Home
  2. Services
  3. Gradescope
Gradescope gradescope.com Live · Partial outage

Is Gradescope down right now? Live status and outage tracker

Partly. Gradescope has problems for some users.

Users are reporting a partial outage: 54 problem reports in the last hour, more than usual.

Reports, last hour
54
Usual at this hour
Almost none
Vs the hour before
−97%

User reports, last 24 hours, one bar per 15 minutes. Dashed line: the usual level. 91 normal · 2 elevated · 3 outage

What you can do

Last spike · · Data refreshes every 5 minutes

01 · User reports
54 reports in the last hour

From a public outage-reporting feed, counted in 15-minute windows. The verdict above is based on these.

02 · Our check, Frankfurt
No answer within 10 seconds

Our server loaded www.gradescope.com 1 h ago. Behind Amazon Web Services.

03 · 12 cities, check-host.net
12 of 12 got an answer

Fastest from Los Angeles (113 ms), slowest from Singapore (925 ms). 1 h ago.

Last 24 hours

Gradescope outages and problems

User reports, last 24 hours

1,914 reports in total, counted in 15-minute windows

In the last hour, 54 problem reports came in for Gradescope, and at this time of day there are usually almost none. Over the last 24 hours there were 1,914 reports. Most recent reports were about website (83%) and login (8%). The last spike in reports was 33 min ago and lasted 1 h 15 min. These are user reports from the US, where most people report Gradescope problems.

In the past 24 hours, 1,914 user reports came in for Gradescope. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 96.88% uptime for the day. The most recent spike big enough to count as an outage was 1 hour ago. The busiest 15-minute window of the day had 792 reports, about 1 hour ago.
  • NormalClose to the usual level22 h 45 min · 15 reports
  • ElevatedMore than 1.5 times the usual level30 min · 39 reports
  • OutageMore than twice the usual level and far above the day's average45 min · 1,860 reports
  • Usual levelWhat a usual day sees at that timeAlmost none at this time of day
Reports, last hour
54
97% on the hour before
Uptime, 24 h
96.88%
45 min of outage
Last outage
30 min ago
Lasted 1 h 15 min
Busiest 15 minutes
792
792 reports, 1 h ago
Gradescope status card: Partly. Gradescope has problems for some users. User reports over the last 24 hours.
Share this statusThe picture people see when this page is shared: the answer and the last 24 hours of reports.

In the past 24 hours, 1,914 user reports came in for Gradescope. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 96.88% uptime for the day.

The most recent spike big enough to count as an outage was 1 hour ago. The busiest 15-minute window of the day had 792 reports, about 1 hour ago.

  • Outage
    Ended 30 min ago
    Lasted 1 h 15 min
    792peak reports
This month

Gradescope in November 2026

Problem reports in November (since 4 November)
1,914

Monthly report for November 2026

What went wrong

What people said was wrong in recent problem reports for Gradescope.

  1. Website83%
  2. Login8%
  3. App7%
  4. Courses2%

Share of 326 recent reports that said what was wrong.

World map

Where Gradescope problem reports come from

The map shows where recent problem reports for Gradescope came from in the US. Big cities always send the most, so dots in many places point to a widespread problem, and one area far ahead of the rest can mean a regional one.

  • Outage now
  • Problems now
  • Normal
Each dot is a group of recent reports, coloured by how its country is doing now; bigger dots, more reports.

Map outlines: Natural Earth.

Last 30 days

Gradescope problem spikes, last 30 days

Since 4 November, Gradescope had 1 outage spike.

  • Outage
    Wed 4 Nov, 21:30–22:45
    Lasted 1 h 15 min
    796peak 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 4 November 2026. Monthly reports for all services

Troubleshooting

How to fix Gradescope not working

When Gradescope itself is having trouble, these steps won't bring it back, but they will rule out anything on your side:

Your browser tries to reach gradescope.com over your own connection, right now. Nothing is sent to us or stored.

  1. Reload and restart

    Reload the page (Ctrl+F5, or Cmd+Shift+R on a Mac), or fully close the app and open it again.

  2. 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 Gradescope.

  3. Update the app

    Install the latest version from the App Store or Google Play. Old versions can stop connecting after a server-side change.

Same time

Problems at the same time as Gradescope

Since 4 November, Gradescope's only spike in problem reports overlapped a spike at another service.

When several services get problem reports at once, something they share, such as a cloud host or a network, can be the real cause. Matching times alone do not prove it.

A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.

Busiest times

When people report Gradescope problems

The busiest hour for reports about Gradescope is 21:00 to 22:00 Central European time, and the busiest day is Wednesday.

By hour of the day

  • 00:00 to 01:00: 0 reports on an average day
  • 01:00 to 02:00: 0 reports on an average day
  • 02:00 to 03:00: 0 reports on an average day
  • 03:00 to 04:00: 0 reports on an average day
  • 04:00 to 05:00: 0 reports on an average day
  • 05:00 to 06:00: 0 reports on an average day
  • 06:00 to 07:00: 0 reports on an average day
  • 07:00 to 08:00: 0 reports on an average day
  • 08:00 to 09:00: 0 reports on an average day
  • 09:00 to 10:00: 0 reports on an average day
  • 10:00 to 11:00: 0 reports on an average day
  • 11:00 to 12:00: 0 reports on an average day
  • 12:00 to 13:00: 0 reports on an average day
  • 13:00 to 14:00: 0 reports on an average day
  • 14:00 to 15:00: 0 reports on an average day
  • 15:00 to 16:00: 0 reports on an average day
  • 16:00 to 17:00: 0 reports on an average day
  • 17:00 to 18:00: 0 reports on an average day
  • 18:00 to 19:00: 0 reports on an average day
  • 19:00 to 20:00: 0 reports on an average day
  • 20:00 to 21:00: 0 reports on an average day
  • 21:00 to 22:00: 17 reports on an average day
  • 22:00 to 23:00: 0 reports on an average day
  • 23:00 to 00:00: 0.28 reports on an average day

By day of the week

  • Monday: 0 reports on an average Monday
  • Tuesday: 0 reports on an average Tuesday
  • Wednesday: 130 reports on an average Wednesday
  • Thursday: 0 reports on an average Thursday
  • Friday: 0 reports on an average Friday
  • Saturday: 0 reports on an average Saturday
  • Sunday: 0 reports on an average Sunday

Each bar is the average number of user reports in that hour, or on that day of the week, from 28 days of reports since 5 October 2026. The busiest bar is highlighted. Spikes in reports are left out, so one outage does not set the pattern.

Servers and network

Gradescope IP address, servers and network

IPv4 addresses
44.241.230.10
Show all 3
  • 44.242.40.21
  • 54.212.7.72
IPv6
Not offered
Network
AS16509 · Amazon.com, Inc., registered in the United States
Served through
Amazon Web Services
DNS hosted by
Amazon Route 53
HTTPS certificate
Issued by Amazon, valid until 29 Jan 2027 (85 days)
HTTP/3
Not advertised
Our check
No answer within 10 seconds

Checked from our server in Frankfurt, Germany, 1 h ago, for www.gradescope.com. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.

Checked from 12 places around the world

All 12 locations got an answer from gradescope.com. Fastest from Los Angeles (113 ms), slowest from Singapore (925 ms). Every location connected through Amazon.com, Inc. (AS16509), using 3 different addresses.

LocationResultTimeAddress reached
FrankfurtGermanyUp · HTTP 301673 ms44.242.40.21
ViennaAustriaUp · HTTP 301772 ms54.212.7.72
MilanItalyUp · HTTP 301635 ms44.241.230.10
ParisFranceUp · HTTP 301650 ms44.241.230.10
AmsterdamNetherlandsUp · HTTP 301630 ms44.241.230.10
MadridSpainUp · HTTP 301686 ms44.241.230.10
WarsawPolandUp · HTTP 301707 ms44.241.230.10
DallasUSAUp · HTTP 301542 ms44.242.40.21
Los AngelesUSAUp · HTTP 301113 ms44.242.40.21
São PauloBrazilUp · HTTP 301894 ms44.241.230.10
SingaporeSingaporeUp · HTTP 301925 ms54.212.7.72
TokyoJapanUp · HTTP 301566 ms54.212.7.72

Checked with check-host.net from its servers in these cities 1 h ago, for gradescope.com. Time is how long each server took to load the page.

Official channels

Contact Gradescope support

Tip: Gradescope doesn't list a public status page that we know of, so its help centre and the report chart on this page are the best places to check.

For your site

Put the Gradescope status badge on your site

Paste one of these into a web page, a blog post or a README. The badge shows the same status as this page, based on user problem reports. Browsers can keep a copy for up to 4 hours. It links back here.

Gradescope status badge, as it looks now

HTML
<a href="https://isitdownrightnow.app/services/gradescope/"><img src="https://isitdownrightnow.app/badge/gradescope.svg" alt="Gradescope status" height="20"></a>
Markdown, for README files
[![Gradescope status](https://isitdownrightnow.app/badge/gradescope.svg)](https://isitdownrightnow.app/services/gradescope/)

The badge is a plain image: no scripts, no cookies. People who see it on your page load it from our server.

How we track Gradescope

The status on this page comes from user-submitted problem reports for Gradescope, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Gradescope, 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. Gradescope 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.

Elsewhere

Check other services