User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
konghq.com · Cloud & developer
Is Kong down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → konghq.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 41 min ago. Last stored result reached it in 55 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 87 ms | 0 |
| Nov 7 | 0 | 0.0 | 159 ms | 0 |
| Nov 7 | 0 | 0.0 | 136 ms | 0 |
| Nov 7 | 0 | 0.0 | 69 ms | 0 |
| Nov 7 | 0 | 0.0 | 113 ms | 0 |
| Nov 8 | 0 | 0.0 | 56 ms | 0 |
| Nov 8 | 0 | 0.0 | 61 ms | 0 |
| Nov 8 | 0 | 0.0 | 94 ms | 0 |
| Nov 8 | 0 | 0.0 | 102 ms | 0 |
| Nov 9 | 0 | 0.0 | 115 ms | 0 |
| Nov 9 | 0 | 0.0 | 59 ms | 0 |
| Nov 9 | 0 | 0.0 | 81 ms | 0 |
| Nov 9 | 0 | 0.0 | 99 ms | 0 |
| Nov 10 | 0 | 0.0 | 58 ms | 0 |
| Nov 10 | 0 | 0.0 | 96 ms | 0 |
| Nov 10 | 0 | 0.0 | 119 ms | 0 |
| Nov 10 | 0 | 0.0 | 55 ms | 0 |
| Nov 11 | 0 | 0.0 | 79 ms | 0 |
| Nov 11 | 0 | 0.0 | 115 ms | 0 |
| Nov 11 | 0 | 0.0 | 126 ms | 0 |
| Nov 11 | 0 | 0.0 | 156 ms | 0 |
| Nov 12 | 0 | 0.0 | 123 ms | 0 |
| Nov 12 | 0 | 0.0 | 111 ms | 0 |
| Nov 12 | 0 | 0.0 | 119 ms | 0 |
| Nov 12 | 0 | 0.0 | 66 ms | 0 |
| Nov 13 | 0 | 0.0 | 102 ms | 0 |
| Nov 13 | 0 | 0.0 | 82 ms | 0 |
| Nov 13 | 0 | 0.0 | 109 ms | 0 |
| Nov 13 | 0 | 0.0 | 69 ms | 0 |
Reliability
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Kong badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Kong yet. Outages of 10 minutes or more get their own page here.
Having trouble with Kong?
One report per service every 10 minutes from this network. No account.
Follow Kong
Get an email when Kong goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Kong alerts to Slack, Discord or a webhook — free.
About Kong
We track Kong (konghq.com) as part of the Cloud & developer group. From APIs to AI, Kong is the fabric of modern connectivity. Centralize LLM access, automate API workflows, and secure your digital ecosystem at scale.
Kong publishes an official status page at status.konghq.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 86 ms average, 17–123 ms range across 16 successful checks.
Questions
Is Kong down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Kong last down?
We have not recorded a public Kong incident since monitoring began 8 days ago.
What is Kong's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Kong respond?
86 ms on average over the last 24 hours (17–123 ms).
Does Kong have an official status page?
Yes, at https://status.konghq.com.
Kong not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Kong here at once, the problem is on Kong's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Kong. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.