Is Blooket Down?

No — Blooket is up

Reachable from all 8 checked regions

Average response time: 49ms

Last checked 5 hours ago · checks run every 6 hours

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

Blooket uptime

100%

Last 7 days

—

Last 30 days

—

Last 90 days

—

Avg response, 30 days

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

30-day history

6-day clean streak

Jul 25 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.

cdg

40ms

DNS 0ms TCP 5ms TLS 9ms TTFB 35ms

dfw

34ms

DNS 0ms TCP 1ms TLS 8ms TTFB 31ms

ewr

59ms

DNS 0ms TCP 2ms TLS 9ms TTFB 57ms

fra

65ms

DNS 0ms TCP 1ms TLS 13ms TTFB 60ms

gru

31ms

DNS 0ms TCP 3ms TLS 12ms TTFB 28ms

iad

104ms

DNS 0ms TCP 1ms TLS 14ms TTFB 101ms

jnb

25ms

DNS 0ms TCP 1ms TLS 8ms TTFB 22ms

lax

37ms

DNS 0ms TCP 2ms TLS 11ms TTFB 35ms

What Blooket does

Blooket is a classroom game platform where a teacher hosts a set of questions and students join from their own devices with a game code, answering to progress through one of several game modes. It is used mostly in primary and secondary schools for review lessons and for homework, so an outage tends to land in the middle of a class period.

What an outage looks like

Blooket splits into four services that can fail separately, so an outage is usually partial rather than total. When hosting is affected, students enter a valid game code and never land in the game. When authentication is affected, teachers and students cannot sign in. When the dashboard is affected, saved question sets and stats will not load, and homework sets can stop recording answers while live games still work.

What to do about it

Check status.blooket.com, which reports Dashboard, Authentication, Hosting and Homework services separately and will usually show which one is affected. It publishes current health only, with no incident history and no timestamps, so it cannot tell you how long a problem has been running. If hosting is down mid-lesson, running the same question set on the projector is the fastest fallback.

Is it down for everyone, or just you?

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

Blooket outage FAQ

Is Blooket down for everyone or just my school?

Check status.blooket.com first, because the school network is the other common cause. The status page reports four services and will flag a problem that is platform-wide. If every service reads healthy but students still cannot join, the block is more likely a district content filter or the classroom network, which would affect only devices on that connection rather than Blooket itself.

Students cannot join my game but I can still see it. Why?

That pattern points at Blooket's hosting services rather than at your account. Hosting is tracked separately from authentication and the dashboard, so a teacher who is already signed in can keep seeing a game that students cannot reach. Check the Hosting Services line on status.blooket.com, and generate a fresh game code once before assuming the old one was mistyped.

Does Blooket homework still record answers during an outage?

Not necessarily, because homework runs as its own service on Blooket's status page. Homework Services can be affected while live hosting stays healthy, which means answers submitted during the incident may not be recorded against the set. If that component is flagged, tell students to stop and come back after it recovers rather than working through the whole assignment twice.

How long do Blooket outages usually last?

Blooket's own status page cannot tell you. It reports only the current health of its four services, with no incident history, no timestamps and no past-uptime graph, so there is no vendor record of duration to read. The measurements on this page are taken independently from several regions and keep 90 days of history, which is where an elapsed time can be seen.

How we measure this

We request Blooket'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 Blooket 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 Blooket 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