Is Nghttp2 down right now?
nghttp2.org
Checking nghttp2.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
Response time by location, last 24 hours
| Location | Average response | Reached |
|---|---|---|
| Berlin 1, Germany | 760 ms | 1 of 1 checks |
| Falkenstein, Germany | 801 ms | 5 of 5 checks |
| Berlin 2, Germany | 806 ms | 3 of 3 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 Nghttp2 could not be reached from at least two locations in two checks in a row.
Recent checks
| Time | Status | Locations | Response |
|---|---|---|---|
| 2026-10-10 11:00 UTC | Up | 1 of 1 | 803 ms |
| 2026-10-10 10:18 UTC | Up | 1 of 1 | 849 ms |
| 2026-10-10 09:12 UTC | Up | 1 of 1 | 767 ms |
| 2026-10-10 08:09 UTC | Up | 1 of 1 | 809 ms |
| 2026-10-10 07:05 UTC | Up | 1 of 1 | 822 ms |
| 2026-10-10 06:02 UTC | Up | 1 of 1 | 786 ms |
| 2026-10-10 05:20 UTC | Up | 1 of 1 | 767 ms |
| 2026-10-10 04:17 UTC | Up | 1 of 1 | 760 ms |
Comments
No comments yet. Be the first to say what you are seeing.
About Nghttp2
Nghttp2: HTTP/2 C Library - nghttp2.org
Nghttp2: HTTP/2 C Library Feb 16th, 2015 11:16 pm nghttp2 is an implementation of HTTP/2 and its header compression algorithm HPACK in C. The …
Visit nghttp2.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 nghttp2.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 Nghttp2 on your own page or in a README. The badge updates by itself.