Skip to content

Is intensedebate.com down right now?

intensedebate.com

Checking intensedebate.com…

Asking our locations to reach the site. This takes a few seconds.

Uptime, 24 hours
100 %
Uptime, 7 days
100 %
Uptime, 30 days
100 %

Based on 1 day of checks so far. Checks that failed because of how we test, not because of the site, are left out.

Response time per hour, last 24 hours

2026-10-10 03:00 UTC: 512 ms2026-10-10 04:00 UTC: 504 ms2026-10-10 05:00 UTC: 486 ms2026-10-10 06:00 UTC: 502 ms2026-10-10 07:00 UTC: 498 ms
Green: response time, full height at 760 ms or more. Red: down. Amber: not confirmed.

Response time by location, last 24 hours

LocationAverage responseReached
Berlin 1, Germany508 ms1 of 1 checks
Falkenstein, Germany500 ms3 of 3 checks
Berlin 2, Germany487 ms1 of 1 checks

Each check runs from all locations at once. A location far from the site’s servers answers later; that says nothing about the site being slow.

Outage history

No confirmed outage on record. An outage is listed once intensedebate.com could not be reached from at least two locations in two checks in a row.

Recent checks

TimeStatusLocationsResponse
2026-10-10 07:08 UTCUp1 of 1500 ms
2026-10-10 06:05 UTCUp1 of 1500 ms
2026-10-10 05:02 UTCUp1 of 1499 ms
2026-10-10 04:20 UTCUp1 of 1508 ms
2026-10-10 03:18 UTCUp1 of 1487 ms

Comments

0/500 · no links · do not post personal data

No comments yet. Be the first to say what you are seeing.

About intensedebate.com

IntenseDebate comments enhance and encourage conversation on your blog or website

IntenseDebate's comment system enhances and encourages conversation on your blog or website.

Visit intensedebate.comTitle and description as published by the site.

We can reach it, but you cannot?
  • Reload the page without the cache: Ctrl + F5 on Windows, Cmd + Shift + R on a Mac.
  • Open the site in a private window. If it works there, clear the cookies and cache for intensedebate.com.
  • Try another network, such as mobile data. If that works, the problem is with your provider or router.
  • Switch to a public DNS resolver such as 1.1.1.1 or 8.8.8.8, then flush your DNS cache.
  • Turn off VPNs, proxies and ad blockers for a moment. Some sites refuse those connections.
Embed a status badge

Show the current status of intensedebate.com on your own page or in a README. The badge updates by itself.

Status of intensedebate.com

Similar sites