User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Education
rutgers.edu · Education
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 298 ms · 2 min ago.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 13:15 | 0 | 0.0 | 493 ms | 0 |
| 13:30 | 0 | 0.0 | 285 ms | 0 |
| 13:45 | 0 | 0.0 | 407 ms | 0 |
| 14:00 | 0 | 0.0 | 922 ms | 0 |
| 14:15 | 0 | 0.0 | 410 ms | 0 |
| 14:30 | 0 | 0.0 | 1843 ms | 0 |
| 14:45 | 0 | 0.0 | 149 ms | 0 |
| 15:00 | 0 | 0.0 | 444 ms | 0 |
| 15:15 | 0 | 0.0 | 535 ms | 0 |
| 15:30 | 0 | 0.0 | 554 ms | 0 |
| 15:45 | 0 | 0.0 | 684 ms | 0 |
| 16:00 | 0 | 0.0 | 400 ms | 0 |
| 16:15 | 0 | 0.0 | 87 ms | 0 |
| 16:30 | 0 | 0.0 | 1042 ms | 0 |
| 16:45 | 0 | 0.0 | 324 ms | 0 |
| 17:00 | 0 | 0.0 | 1046 ms | 0 |
| 17:15 | 0 | 0.0 | 160 ms | 0 |
| 17:30 | 0 | 0.0 | 356 ms | 0 |
| 17:45 | 0 | 0.0 | 1073 ms | 0 |
| 18:00 | 0 | 0.0 | 740 ms | 0 |
| 18:15 | 0 | 0.0 | 122 ms | 0 |
| 18:30 | 0 | 0.0 | 725 ms | 0 |
| 18:45 | 0 | 0.0 | 168 ms | 0 |
| 19:00 | 0 | 0.0 | 653 ms | 0 |
| 19:15 | 0 | 0.0 | 421 ms | 0 |
| 19:30 | 0 | 0.0 | 458 ms | 0 |
| 19:45 | 0 | 0.0 | 951 ms | 0 |
| 20:00 | 0 | 0.0 | 799 ms | 0 |
| 20:15 | 0 | 0.0 | 852 ms | 0 |
| 20:30 | 0 | 0.0 | 298 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Rutgers University yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Rutgers University goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Rutgers University alerts to Slack, Discord or a webhook — free.
Rutgers University is listed in our Education category and checked at rutgers.edu. Live checks and user reports.
Rutgers University publishes an official status page at it.rutgers.edu; when we can read it, its incident level is folded into the status shown here.
Typical issues with education services: learning management systems and student portals slowing down around assignment deadlines, exams and registration.
Measured uptime from our checks: 100% over 1 day of checks. No public incidents logged since monitoring began 1 day ago.
Response time over the last 24 hours: 600 ms average, 66–3612 ms range across 55 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Rutgers University incident since monitoring began 1 day ago.
From our own checks: 100% over 1 day of checks.
600 ms on average over the last 24 hours (66–3612 ms).
Yes, at https://it.rutgers.edu/alerts/.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For education services, watch for learning management systems and student portals slowing down around assignment deadlines, exams and registration. If many people report Rutgers University here at once, the problem is on Rutgers University's side.