Skip to main content

Is Nearpod Down?

No — Nearpod is up

Reachable from all 8 checked regions

Average response time: 706ms

Last checked · checks run every 6 hours

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

Nearpod uptime

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

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

30-day history

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

arn
636ms
DNS 44ms TCP 1ms TLS 14ms TTFB 525ms
cdg
1475ms
DNS 41ms TCP 2ms TLS 13ms TTFB 1473ms
dfw
135ms
DNS 45ms TCP 1ms TLS 11ms TTFB 133ms
ewr
88ms
DNS 43ms TCP 2ms TLS 11ms TTFB 85ms
fra
1536ms
DNS 15ms TCP 2ms TLS 13ms TTFB 1533ms
gru
420ms
DNS 119ms TCP 2ms TLS 16ms TTFB 417ms
iad
69ms
DNS 33ms TCP 1ms TLS 9ms TTFB 67ms
jnb
1294ms
DNS 16ms TCP 0ms TLS 15ms TTFB 1293ms

What Nearpod does

Nearpod is an interactive lesson platform for K-12 classrooms. Teachers build or import slide-based lessons with embedded quizzes, polls, drawings and virtual field trips, then deliver them live with students following along on their own devices, or set them for students to work through independently. Schools use it across subjects and grade levels.

What an outage looks like

Students cannot join a lesson code, or a live lesson stops advancing on student devices while the teacher view still moves. Nearpod reports Login, Content Creation, Content Delivery and Reporting as separate components, so being unable to sign in, being unable to build a lesson and being unable to run one are three different incidents.

What to do about it

Check status.nearpod.com and read which of the four components is affected. A Content Delivery incident is the one that interrupts a class in progress; a Content Creation incident only blocks lesson building and can wait. If Reporting is the failing component, student responses may not appear in your reports even though the lesson ran, so hold off judging participation from an incomplete view.

Is it down for everyone, or just you?

If this page says Nearpod 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

Nearpod outage FAQ

Students cannot join my Nearpod lesson code. Is Nearpod down?
Check Content Delivery and Login, which Nearpod reports separately. Joining a code touches both, so the failure can be in student sign-in or in lesson delivery itself. If both read operational, the more likely cause is the school network or device restrictions, which a status page covering only Nearpod's own systems cannot see.
Will student answers be lost if Nearpod goes down mid-lesson?
Nearpod does not publish what happens to responses submitted during an incident, so treat the affected window as uncertain rather than assuming answers were saved. Reporting is a separate component from Content Delivery, so responses can also be captured but temporarily missing from reports. Check reports again after both components recover before re-running the activity.
I cannot sign in to Nearpod but a colleague can. Is that an outage?
Possibly not. Login is its own component, and if it reads operational while only your account is affected, the cause is more likely your credentials, a school SSO provider or a device policy. Nearpod's status page covers its own systems, so it cannot report a failure inside your district's identity provider.
Can I still build lessons while Nearpod is having problems?
Often yes. Content Creation is reported separately from Content Delivery, so an incident that stops live lessons can leave authoring available, and the reverse is also possible. If you are preparing for a later class rather than teaching now, check the Content Creation row specifically instead of giving up on the whole platform.
Is Nearpod down for every school or just mine?
Nearpod's status page reports components rather than regions or individual schools, so it cannot tell you. Independent multi-region measurement is what separates the two cases: if outside probes reach Nearpod normally while a whole school cannot, the problem is closer to that school's network, filtering or device fleet.

How we measure this

  • We request Nearpod'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 Nearpod 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 Nearpod 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