Is Kong Down?

No — Kong is up

Kong's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 213 ms

Right now

The verdict is the worse of these two. How we decide

Kong's status page

status.konghq.com · read 4 minutes ago · checked every 3 minutes

Operational

Kong's components, as its status page reports them
Component	Status
Kong Konnect Cloud	Operational
Kong Insomnia	Operational
Kong Support Portal	Operational

Open their status page

FlareWarden checks

konghq.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 213 ms
Checked: 2 hours ago

By region

Ashburn reachable, 74 ms
Dallas reachable, 65 ms
Frankfurt reachable, 55 ms
Johannesburg reachable, 208 ms
London reachable, 34 ms
Los Angeles reachable, 128 ms
Newark reachable, 128 ms
São Paulo reachable, 1012 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	47 ms	1 ms	5 ms	58 ms
Dallas	47 ms	1 ms	4 ms	59 ms
Frankfurt	34 ms	2 ms	4 ms	46 ms
Johannesburg	191 ms	1 ms	6 ms	202 ms
London	8 ms	2 ms	5 ms	22 ms
Los Angeles	104 ms	2 ms	4 ms	118 ms
Newark	98 ms	3 ms	7 ms	115 ms
São Paulo	150 ms	120 ms	124 ms	539 ms

We check that konghq.com loads, not every feature behind it. Test it yourself

History

Incidents Kong reported

Since Oct 22, 15 days · from status.konghq.com

Incidents: 1
Major or critical: 1
Median to resolve: 52m

Users unable to assign roles in Konnect
major · Oct 26
lasted 52m

Kong website availability

Measured by FlareWarden · konghq.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 214ms

Last 30 days

78-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of konghq.com from multiple regions every 6 hours. Kong's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 78 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 17 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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Kong itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Kong goes down

We check Kong every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required