Is Kong down in the US?
Vendor reports no incidentWhat Kong reports
Kong reports no incident on its status page.
As of the last successful poll, 2026-11-05 17:59 UTC.
Our regional reading
This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.
Checks passingin the US, measured from Ashburn and San Jose
All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked Kong at Nov 5, 2026, 6:02 PM UTC.
Over the last 24 hours we completed 253 checks from Ashburn and San Jose and 253 answered cleanly, 100.00% availability.
Of the 2 other regions we check Kong from, all 2 read checks passing right now.
Email me when Kong reports an incident on its status page, and again when it reports it resolved.
What our Ashburn and San Jose probes measured
Last checked Nov 5, 2026, 6:02 PM UTC.
Kong from Ashburn and San Jose over the last 30 days
Over the last 30 days, Kong answered our Ashburn probe in 981 ms on average, and 1 check in 20 took longer than 1,365 ms.
Over the last 30 days, Kong answered our San Jose probe in 1,017 ms on average, and 1 check in 20 took longer than 1,442 ms.
Ranked by average response time across the 4 cities we check Kong from, Ashburn 2nd, San Jose 3rd; Frankfurt was fastest at 546 ms and Tokyo slowest at 1,733 ms.
From Ashburn and San Jose we ran 793 checks of Kong in 4 days, and 793 answered cleanly: 100.00% availability.
Every one of those days was clean: not one failed check.
In Ashburn local time (EST), Kong was slowest around 2 PM, at 1,176 ms on average over the last 14 days, and quickest around 10 AM, at 667 ms.
| Day (UTC) | Checks | Availability | Average response |
|---|---|---|---|
| Thu, Nov 5 | 187 | 100.00% | 989 ms |
| Wed, Nov 4 | 253 | 100.00% | 937 ms |
| Tue, Nov 3 | 248 | 100.00% | 1,041 ms |
| Mon, Nov 2 | 105 | 100.00% | 1,051 ms |
Kong outages measured from the US
Our Ashburn and San Jose probes measured no confirmed Kong outage in the last 90 days.
How the other regions read right now
Of the 2 other regions we check Kong from, all 2 read checks passing right now.
| Probe city | Right now | Last 24h |
|---|---|---|
| Frankfurt | Checks passing | 100.00% of 99 checks |
| Tokyo | Checks passing | 100.00% of 62 checks |
Other countries we check Kong from
How we measured this
The US readings on this page come from RealUptime's own Ashburn and San Jose probes against Kong's public endpoints. They are not user reports, and they are not Kong's own status page.
See Kong's full check readings, the 90-day history by region, or the outage tracker methodology.
The US readings here are taken from that country and show the time of the last one, but Kong has not yet accumulated enough continuous history for us to publish this page to search engines.
Check your own site from Ashburn
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversRun a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter