Skip to content

Is kottke.org down right now?

kottke.org

Checking kottke.org…

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: 142 ms2026-10-10 04:00 UTC: 208 ms2026-10-10 05:00 UTC: 139 ms2026-10-10 06:00 UTC: 294 ms2026-10-10 07:00 UTC: 256 ms2026-10-10 08:00 UTC: 129 ms2026-10-10 09:00 UTC: 138 ms
Green: response time, full height at 380 ms or more. Red: down. Amber: not confirmed.

Response time by location, last 24 hours

LocationAverage responseReached
Berlin 1, Germany131 ms3 of 3 checks
Falkenstein, Germany150 ms3 of 3 checks
Berlin 2, Germany135 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 kottke.org could not be reached from at least two locations in two checks in a row.

Recent checks

TimeStatusLocationsResponse
2026-10-10 09:06 UTCUp1 of 1130 ms
2026-10-10 08:02 UTCUp1 of 1124 ms
2026-10-10 07:20 UTCUp1 of 1169 ms
2026-10-10 06:16 UTCUp1 of 1135 ms
2026-10-10 05:13 UTCUp1 of 1139 ms
2026-10-10 04:11 UTCUp1 of 1144 ms
2026-10-10 03:30 UTCUp1 of 1136 ms

Comments

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

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

About kottke.org

kottke.org - home of fine hypertext products

Jason Kottke's daily links and commentary on art, science, technology, design, film, and culture since 1998.

Visit kottke.orgTitle 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 kottke.org.
  • 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 kottke.org on your own page or in a README. The badge updates by itself.

Status of kottke.org