Is pornhub.be down right now?

pornhub.be is currently UP HTTP 200, response time 95ms. Uptime over last 20 checks: 100%.

How do I check if pornhub.be is down for everyone?

Our tool checks from our Frankfurt, Germany server. If we show UP but you cannot access it, the problem is on your end try flushing DNS or switching networks.

Is It Down? pornhub.be

pornhub.be

https://pornhub.be · UP

All sites WHOIS

Host: pornhub.be Server: Frankfurt, DE Timezone: America/New_York History: 1 / 20 checks Site is UP

Live monitoring · last checked 07:46:37

sec until next refresh

Current

200

HTTP Code

Response ms

100%

Uptime (20)

Outages

Response Time Last 1 Checks

UP DOWN

Recent Checks (Last 20 Pings)

	Time (America/New_York)	Status	HTTP Code	Response (ms)
	07:46:37 · 04.06.2026	UP	200	95

07:46:37

04.06.2026

UP HTTP 200 · 95ms

Last Detected Downtime

No downtime recorded in the last 20 checks. ✅

Recently Checked Sites

Website	Status	HTTP	Response	Uptime
pornhub.com	UP	200	340 ms	100%
pornhub.fr	UP	200	735 ms	100%
pornhub.be	UP	200	95 ms	100%
es.pornhub.com	UP	200	302 ms	100%
pornhub.org	DOWN	503	110 ms	40%
porn.com	UP	200	172 ms	100%
fr.pornhub.com	UP	403	5052 ms	100%
lovetorrent.net	DOWN		6001 ms	0%
pornohub.com	UP	200	459 ms	100%
americanas.com.br	UP	200	347 ms	100%

pornhub.com

340ms

UP HTTP 200 · 100%

pornhub.fr

735ms

UP HTTP 200 · 100%

pornhub.be

95ms

UP HTTP 200 · 100%

es.pornhub.com

302ms

UP HTTP 200 · 100%

pornhub.org

110ms

DOWN HTTP 503 · 40%

porn.com

172ms

UP HTTP 200 · 100%

fr.pornhub.com

5052ms

UP HTTP 403 · 100%

lovetorrent.net

6001ms

DOWN HTTP · 0%

pornohub.com

459ms

UP HTTP 200 · 100%

americanas.com.br

347ms

UP HTTP 200 · 100%

About This Check

We send an HTTP HEAD request from our Frankfurt, Germany server to pornhub.be. A response of HTTP 200–399 within 10 seconds = UP. Any timeout, DNS failure, or error code = DOWN. A rolling history of the last 20 checks is stored and displayed above.

If the site shows UP here but you can't access it, the issue is local flush your DNS cache (ipconfig /flushdns on Windows / sudo dscacheutil -flushcache on macOS) or try a different network.