Is Kong Down?

No — Kong is up

Reachable from all 8 checked regions

Average response time: 207ms

Last checked 3 hours ago · checks run every 6 hours

Official status page: https://status.konghq.com

Kong uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

128ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 32 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

32-day clean streak

Aug 22 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ewr

43ms

DNS 16ms TCP 2ms TLS 6ms TTFB 35ms

fra

152ms

DNS 138ms TCP 1ms TLS 4ms TTFB 147ms

gru

885ms

DNS 158ms TCP 109ms TLS 114ms TTFB 511ms

iad

69ms

DNS 50ms TCP 1ms TLS 4ms TTFB 61ms

jnb

211ms

DNS 190ms TCP 0ms TLS 5ms TTFB 207ms

lax

100ms

DNS 73ms TCP 2ms TLS 4ms TTFB 94ms

lhr

43ms

DNS 23ms TCP 2ms TLS 4ms TTFB 35ms

nrt

160ms

DNS 139ms TCP 2ms TLS 4ms TTFB 152ms

What Kong does

Kong builds API gateway and connectivity software. Kong Konnect is its hosted control plane for managing gateways, and Insomnia is its API client for designing and testing requests. Teams use it to route, secure and observe traffic between services. The distinction that matters during an incident is that the control plane is hosted while gateway nodes usually run in your own infrastructure.

What an outage looks like

The Konnect console will not load, or loads without showing gateway data. Configuration changes cannot be published to gateways, so a route or plugin update does not take effect. Analytics and traffic charts go blank. Insomnia may fail to sync collections and environments between team members while local requests still work. Nodes started during the incident cannot fetch their configuration.

What to do about it

status.konghq.com tracks Kong Konnect Cloud, Kong Insomnia and the Kong Support Portal separately, so a tooling or ticketing problem is not mistaken for a control plane one. Konnect is the row that matters when configuration will not publish. Hold off on restarting gateway nodes or rolling out config changes until it recovers, since both depend on reaching the control plane.

Is it down for everyone, or just you?

If this page says Kong is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Cloudflare

AWS

Postman

GitHub

Kong outage FAQ

Is my API traffic affected when Kong Konnect is down?

That depends on your topology, and it is worth knowing the answer before an incident rather than during one. Konnect is the hosted control plane, which distributes configuration, while the gateway nodes that proxy requests typically run in your own infrastructure. Confirm how your deployment behaves when the control plane is unreachable against Kong's documentation rather than assuming.

Configuration changes will not publish. What should I do?

Wait rather than working around it. Publishing configuration to gateways goes through Konnect, so a control plane incident blocks it by design. Applying changes directly to individual nodes to get past the outage leaves them out of step with what Konnect believes is deployed, and reconciling that afterwards is more work than the delay costs.

Insomnia will not sync. Is that the same outage?

Not necessarily. Kong's status page lists Kong Insomnia as a component separate from Kong Konnect Cloud, so the API client and the gateway control plane can fail independently. Local requests in Insomnia generally do not depend on the sync service, so you can usually keep testing while collection and environment sync is unavailable.

Should I restart gateway nodes during a Konnect incident?

Avoid it if you can. A node coming up fresh has to reach the control plane before it is configured, so a restart during a Konnect outage risks turning a management problem into a traffic one. If a node genuinely must be replaced, check first how your deployment supplies configuration when the control plane is unreachable.

The support portal is down too. How do I report an issue?

Kong tracks the Support Portal as its own component, so it can be unavailable while Konnect is healthy, and the reverse. When the portal is affected, use the status page's subscribe option for updates rather than waiting on a ticket, and keep your own timeline of what you observed so you can file it accurately once the portal returns.

How we measure this

We request Kong's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Kong publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Kong goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required