Is crt.sh down right now?
crt.sh · last confirmed outage 19 min ago
Checking crt.sh…
Asking our locations to reach the site. This takes a few seconds.
- Uptime, 24 hours
- 100 %
- Uptime, 7 days
- –
- Uptime, 30 days
- –
Response time, last 24 hours
Response time by location, last 24 hours
| Location | Average response | Reached |
|---|---|---|
| Berlin 1, Germany | – | 2 of 8 checks |
| Falkenstein, Germany | – | 3 of 8 checks |
| Berlin 2, Germany | – | 2 of 8 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
- 2026-10-09 11:42 UTClasted 11 min
- 2026-10-09 11:03 UTClasted 6 min
Recent checks
| Time | Status | Locations | Response |
|---|---|---|---|
| 2026-10-09 11:53 UTC | Reachable | 3 of 3 | – |
| 2026-10-09 11:44 UTC | Down | 3 of 3 | – |
| 2026-10-09 11:42 UTC | Down | 3 of 3 | – |
| 2026-10-09 11:27 UTC | Reachable | 3 of 3 | – |
| 2026-10-09 11:25 UTC | Down | 3 of 3 | – |
| 2026-10-09 11:10 UTC | Reachable | 3 of 3 | – |
| 2026-10-09 11:06 UTC | Down | 3 of 3 | – |
| 2026-10-09 11:03 UTC | Down | 3 of 3 | – |
Comments
No comments yet. Be the first to say what you are seeing.
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 crt.sh.
- 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 crt.sh on your own page or in a README. The badge updates by itself.
