Skip to main content

Is Padlet Down?

No — Padlet is up

Reachable from all 8 checked regions

Average response time: 274ms

Last checked · checks run every 6 hours

Official status page: https://status.padlet.help

Padlet uptime

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

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

30-day history

22-day clean streak
Aug 24: no data
Aug 25: no data
Aug 26: no data
Aug 27: no data
Aug 28: no data
Aug 29: no data
Aug 30: no data
Aug 31: no data
Sep 1: 100.00% uptime, 24 checks
Sep 2: 100.00% uptime, 32 checks
Sep 3: 100.00% uptime, 32 checks
Sep 4: 100.00% uptime, 28 checks
Sep 5: 100.00% uptime, 21 checks
Sep 6: 100.00% uptime, 24 checks
Sep 7: 100.00% uptime, 32 checks
Sep 8: 100.00% uptime, 38 checks
Sep 9: 100.00% uptime, 38 checks
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, 31 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, 8 checks
Aug 24 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.

gru
284ms
DNS 168ms TCP 2ms TLS 8ms TTFB 276ms
iad
222ms
DNS 60ms TCP 2ms TLS 6ms TTFB 213ms
jnb
130ms
DNS 12ms TCP 1ms TLS 6ms TTFB 125ms
lax
315ms
DNS 72ms TCP 2ms TLS 9ms TTFB 306ms
lhr
204ms
DNS 37ms TCP 2ms TLS 7ms TTFB 195ms
nrt
300ms
DNS 157ms TCP 1ms TLS 7ms TTFB 294ms
ord
229ms
DNS 59ms TCP 2ms TLS 8ms TTFB 221ms
sin
511ms
DNS 118ms TCP 3ms TLS 12ms TTFB 499ms

What Padlet does

Padlet gives teachers and teams a shared board where people post notes, images, links and files onto a common canvas. In classrooms it is used for brainstorms, exit tickets and group work, where thirty students post to the same board at once and everyone expects to see each other's contributions appear as they are added.

What an outage looks like

Boards load and existing posts are readable, but new posts from other people stop appearing and your own may not save, because Padlet reports Realtime Collaboration as a component separate from Boards. In a classroom that reads as students claiming they posted when the teacher's screen shows nothing. Boards themselves can also fail to open, which is the more obvious failure.

What to do about it

Check status.padlet.help, which lists Boards, Realtime Collaboration, the API, Sandbox and Arcade as separate entries with 90-day uptime figures. If Realtime Collaboration is the affected component, ask students to stop reposting and refresh instead, because duplicates are the usual result. Boards that were already open often keep displaying content that is no longer being updated.

Is it down for everyone, or just you?

If this page says Padlet 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 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

S
Seesaw
C
ClassDojo
N
Nearpod
P
Pear Deck

Padlet outage FAQ

Students say they posted but nothing appears. Is Padlet down?
Check Realtime Collaboration specifically. Padlet lists it as a component separate from Boards, and when it is affected the board still loads and old posts still read while new contributions do not propagate. Students see their own post locally and the teacher sees an empty board, so both are describing the truth from where they sit. Refreshing is more useful than reposting.
Will we lose the posts made during an outage?
Padlet does not publish what happens to posts submitted while Realtime Collaboration is affected, so we will not claim they are queued and delivered later. Treat anything posted during an incident as unconfirmed until it appears after a refresh. Asking students to repost immediately tends to produce duplicates rather than recovering the original.
Is it Padlet or our school network?
Test from outside the school connection before concluding either way. School content filters and bandwidth limits at the start of a lesson produce the same symptoms as a Padlet incident, and a class of thirty devices loading images at once is a heavier load than the network sees most of the day. If it loads on mobile data and the status page is clear, the problem is local.
Does an outage affect boards I already have open?
An open board often keeps displaying what it already loaded, which is the confusing part. The content on screen is what arrived before the incident, so the board looks alive while nothing new reaches it. Treat a board that has stopped changing during active group work as suspect rather than as evidence that nobody is posting.
How reliable has Padlet been recently?
Padlet publishes a 90-day uptime percentage against each component on its status page, so Boards and Realtime Collaboration can be compared over the same window. Those are vendor self-reported figures. The measurement shown on this page is taken independently from several regions, which is why our number and theirs can differ.

How we measure this

  • We request Padlet'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 Padlet 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 Padlet goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required