Is Kong Down Right Now? Check if there is a current outage ongoing.

Affected services include Konnect UI and Developer Portal.

We're currently experiencing disruptions in some of our services due to issues with an upstream service provider. Our team is actively monitoring the situation and working with the provider to restore normal operations as quickly as possible. We'll continue to provide updates as we learn more. Thank you for your patience. https://www.cloudflarestatus.com/

The application at https://app.insomnia.rest/ is seeing intermittent errors due to an ongoing incident with our cloud provider, GCP, and the related hosting provider, Firebase Hosting. We're monitoring this incident and will post updates as the situation develops. https://status.firebase.google.com/incidents/1gSdDPiJpQPdMKb4H55t

We care currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

We are currently investigating this issue.

We have confirmed that verification email deliverability for affected users has recovered to normal levels. Enterprise customers and users authenticating via Google, GitHub, or SSO were not affected during this incident. Users still seeing verification emails directed to spam can mark the email as "Not Spam" to resolve mailbox-specific issues.

We've deployed additional protections to limit the volume of verification emails, and we're actively monitoring the impact. Some users may still see verification emails go to spam over the next day due to the nature of the email ecosystem. Enterprise customers and users authenticating via Google, GitHub, or SSO remain unaffected.

We have identified the root cause of this issue: an unusually high volume of verification emails has impacted our email delivery reputation, causing legitimate login and signup emails to be filtered to spam folders. This issue is limited to users authenticating via passwordless email login on Insomnia. Enterprise customers and users authenticating via Google, GitHub, or SSO are not affected. We are implementing a fix and will provide updates on our progress.

Some users attempting to log in or sign up via email may see verification emails being sent to spam. Users authentication via other means remain unaffected. We're actively working on a fix and will post updates as we approach a resolution.

We have confirmed that verification email deliverability for affected users has recovered to normal levels. Enterprise customers and users authenticating via Google, GitHub, or SSO were not affected during this incident. Users still seeing verification emails directed to spam can mark the email as "Not Spam" to resolve mailbox-specific issues.

We've deployed additional protections to limit the volume of verification emails, and we're actively monitoring the impact. Some users may still see verification emails go to spam over the next day due to the nature of the email ecosystem. Enterprise customers and users authenticating via Google, GitHub, or SSO remain unaffected.

We have identified the root cause of this issue: an unusually high volume of verification emails has impacted our email delivery reputation, causing legitimate login and signup emails to be filtered to spam folders. This issue is limited to users authenticating via passwordless email login on Insomnia. Enterprise customers and users authenticating via Google, GitHub, or SSO are not affected. We are implementing a fix and will provide updates on our progress.

Some users attempting to log in or sign up via email may see verification emails being sent to spam. Users authentication via other means remain unaffected. We're actively working on a fix and will post updates as we approach a resolution.

This incident has been resolved.

The pipeline has been restored and the backlog of data is being processed.

We have identified and taken steps to begin restoring our Analytics pipeline.

Our analytics processing pipeline to publish Analytics data has stopped ingesting new data as of 11:00 UTC. New Analytics data sent from customer data planes is not being lost, but it will not visible in Konnect while the pipeline is stopped.

This incident has been resolved.

A fix has been implemented and we are monitoring results.

The issue has been identified and a fix is being prepared.

This incident has been resolved.

Fixes have been implemented, service is restored, and we are monitoring the results. Analytics data may be delayed.

The issue has been identified and service is broadly restored. We are working through remaining issues.

We are currently investigating.

Between 2025-04-10T22:12Z and 2025-04-11T02:17Z, some users incorrectly received audit logs indicating authorization failures for actions that were in-fact authorized. The team reverted the change that caused the incorrect audit events. Only service reports were affected and not the actual service.

A permission replication issue in our authorization system led to some users seeing unexpected authorization failures during the time period.

A software update led to some accounts not being able to authenticate. We have reverted a change and service has been restored. The outage was approximately 22:15Z to 02:15Z.

Data plane connections have recovered, and we are actively monitoring the health of the Konnect platform in the India region. Some data planes experienced degraded performance and delays in configuration propagation for roughly two minutes. During this period, any data planes that lost connectivity to the Konnect platform fell back to their cached configuration. The issue was caused by hardware degradation reported by our infrastructure provider, affecting the underlying host of one instance. This led to intermittent performance issues or unavailability for some users.

We have identified and are promptly responding to an issue impacting data planes from connecting in the India region.

The issue has been resolved.

The identity provider for Konnect has implemented a fix which resolved the outage on their end. The Logins/Signups should be back up. We are currently monitoring the health of the system.

The identity provider for Konnect accounts is experiencing an outage. New social login "Sign ups" and "Logins" are affected. Organizations that use OIDC or SAML to login are not impacted. Logged-in users are also not impacted. We are urgently following up with our auth vendor who has an ongoing incident.

We are continuing to investigate this issue.

New logins that do not use OIDC or SAML are currently not possible. We are investigating the issue.

Components of Kong Insomnia interacting with our servers were degraded or unavailable from 13:42 - 14:10 UTC on March 13, 2025. This includes login, registration, and in-product capabilities like Cloud Sync. Local & git-backed capabilities were unaffected. Services were fully restored by the end of the incident window.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

Services configured with application registration are not responding to new configuration changes. Existing configuration will continue to work. We've identified the issue and are working on a fix.

We have reverted to a previously working version and systems are back to normal.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

We are currently investigating this issue.

On 1/29/2025 between 08:42Z and 10:39Z, users logging into Konnect were unable to load the Konnect UI to an error when attempting to build the session. This resulted in a complete UI outage for new logins during the incident. API traffic, Data Plane connections, and other non-UI functionality was not impacted. The cause was determined to be a combination of two changes: * A recent UI update made certain data a critical component for session building, which relied on an overly-precise data structure * A back-end change which modified the data structure in such a way that the UI component could no longer successfully parse the response Although initial unit and end-to-end tests for the new UI component passed, the issue only surfaced after the backend change was deployed. The extended outage was caused by a failure to initially identify the backend change, and Konnect engineers rolled back several UI changes before determining the immediate problem To prevent this issue in the future, the Konnect team is * Ensuring the UI will be able to function in all but the most critical of back-end outages * Having back-end changes that could impact session building run an additional set of UI end-to-end tests before deploying * Using our feed of all Konnect changes to inform Konnect Engineers of possible incident causes, bringing down our time to identify in cases where the incident is caused by interactions between multiple changing systems

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are continuing to investigate the issue.

We are currently investigating this issue.

This incident has been resolved.

Listing assigned roles for teams, users and system accounts have all been fixed. We are monitoring the results.

Listing assigned roles for users has now been fixed in addition to system accounts. We are continuing to work on a fix for the assigned role list api for teams.

Listing assigned roles for system accounts has been fixed and works as expected now. We are continuing to work on a fix for assigned role list api's for users and teams

We have identified an issue with our list assigned roles API. We are working on a fix.

Roles assigned to users and system accounts are not listable via API and Konnect UI. Authorization based on the permissions assigned to users and system accounts is still working as expected. We are investigating.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are investigating an issue with configuring Dev Portal OIDC login settings

The fix is working as expected. This incident is resolved.

The issue has been identified and the team is working on a fix.

The team is continuing to investigate the issue. We believe the current impact is minor with a very small number orgs and users impacted.

Some SSO organizations are not showing on the org switcher list for some users. SSO/Built-in login still works as expected. The team is investigating.

This incident has been resolved

The team has identified the issue, deployed a fix and is monitoring results currently.

The team is currently currently investigating the issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

We are investigating an issue with developer registration in the Developer Portal.

This issue has been resolved, but for a brief period Application Analytics were unavailable in Developer Portals.

Some Konnect customers who created new organizations were unable to complete the initial onboarding demonstration. This issue affected the functionality of the demonstration control plane; however, all other control planes and Konnect features remained fully usable.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

Investigating an issue affecting Analytics and Developer Portal documents

Some services experienced brief elevated error rates due to an infrastructure change, but normal operation has since been restored

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently investigating the issue.

We have confirmed that all permission functionality is working as expected. This incident has been resolved.

The team has found the root cause and fixed the issue. Permissions are now propagating for new non-admin users as expected.

Permissions are not propagating for new non-admin users in all Konnect orgs. The team is investigating.

This incident has been resolved.

Patch has been applied successfully. All developer-teams are working as expected.

We are applying a patch to the specific portals identified earlier.

New developer-teams or new role/team assignments to new and existing developers in AU also work now, similar to the US and EU regions. We have identified a small subset of portals across all regions where we continue to see issues with existing developer-teams. We are continuing to investigate those specific cases.

New developer-teams or new role/team assignments to new and existing developers in US and EU now work as expected. The AU region continues to see issues. The team is continuing to investigate.

Some Dev Portal developers part of developer-teams with RBAC controls do not have the permissions they expect. This issue is being investigated.

The incident has been resolved. Developers are able to successfully authenticate to Dev Portals in AU consistently.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results. Developers should now be able to successfully authenticate to Dev Portals in AU.

Developers are unable to authenticate into Dev Portals in AU. The team is actively investigating.

This incident has been resolved.

Serverless Cloud Gateway creation is functional again. We are continuing to monitor the situation.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

We are investigating an issue related to creating Serverless Cloud Gateways.

Between 08:35Z-09:23Z, users attempting to create a new control plane in the EU region were unable to do so. This issue was blocked from being deployed to other regions, and rolled back, restoring the ability to create new Control Planes. There were no impacts to existing control planes, customer data planes, or cloud data planes in any region during this incident.

Some requests to the Portal APIs were failing with 404s causing various issues, including preventing developers from logging in. The issue has been resolved.

The issue is resolved and the service is operating normally .

The system has fully recovered, and we are monitoring the health of the Australia Region while working with AWS to obtain a full root cause analysis.

We identified a routing issue with AWS where one set of IPs for a service was working, and another set was being dropped. The issue seems resolved now as the DNS record has changed and autoscaling has recovered.

This is only impacting the Australia region; we are investing the issue currently.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We’re currently investigating reports of a potential service interruption with the Konnect Telemetry endpoint. We will update this page with additional information as we learn more.

A temporary DNS change caused a disruption, leading to a brief period of service unavailability for konnect cp/tp endpoints limited to the Australian Geo. The issue was swiftly identified and resolved, restoring normal operations of the service.

This incident has been resolved.

Database migration has been completed for all regions and telemetry connections have been re-established.

Control plane and telemetry plane authentication mechanisms are out of sync; database migration process underway.

Telemetry/Analytics data is currently being buffered locally on data plane nodes while connections are impacted for all regions.

A rollback has been applied on a faulty deployment and the login service is back online and working normally. Users should be able to login or switch organizations now.

A fix has been implemented and we are monitoring the results.

Konnect users are experiencing issues to log into their organizations. We are actively looking into this issue now and a fix is being rolled out. Users who are already logged in are not impacted, and Data Plane connections to the Konnect Control Plane are also not impacted.

At approximately 12:25 UTC, the Konnect API service in the US region experienced degradation for control plane configurations due to increased resource utilization on the database. This issue was triggered by a rollout that caused rolling restarts of both the control plane and analytics pods, adding extra stress to the system. Database resources have been increased, and proper rollout isolation between the control planes and analytics has been implemented. The issue was resolved around 13:23 UTC.

All affected DNS records have been corrected, and data plane node connections will resume.

We have updated the impacted DNS records and have observed connections able to be established again.

We have identified a dns configuration issue resulting in DPs resolving an incorrect control plane host, causing the TLS issues. We are currently deploying a correction.

The Konnect Control Plane team has observed an increase in the number of TLS errors being observed from Data Planes trying to establish new connections to the Konnect Control Plane in all regions. The team is currently assessing cause and impact and will continue to update this incident as we learn more.

This incident has been resolved.

Lag on propagating permission changes continues to approach near zero. We expect the system to be fully operational in the next hour. The team is continuing to monitor closely.

We have a fix out for the issue but customers might continue to see 403's while we are propagating permission changes that were made during the incident period. The team is continuing to monitor closely.

We are continuing to investigate this issue.

Customers may see an increased number of 403s (Forbidden) API responses and "permission denied" pages in Konnect. We are investigating this issue at the moment.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

Some users were unable to login via SSO between 17:05 UTC and 17:13 UTC. New organization creations were also impacted during the same time window. Both actions are consistently succeeding now but the team is continuing to monitor closely.

This incident has been resolved.

We are taking actions to reduce search ingestion time for new entities.

Customers may notice delays in being able to Search or Filter for new objects they create. This includes items in Gateway Manager such as Routes and Plugins. The team is actively working to reduce the time for new objects to appear in Searching/Filtering.

This US region incident has been resolved.

We have made adjustments to our system configurations to mitigate the increased latency and timeout issues affecting some API requests. We will continue to monitor the situation closely to ensure stability and performance. Note: This is only impacted the US region.

We are currently looking into the increased latency and timeout issues that are occurring with some API requests. Note: This is only impacting the US region.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

From approximately 13:00 UTC to 14:00 UTC, some data planes failed to authenticate to their control planes. Any configuration changes made during this time failed to reach the data planes.

This incident has been resolved.

Approximately 30 minutes ago the deployment rollout of the control plane services resumed normal operations within Konnect. We will continue to actively monitor the situation.

We have identified the issue and are looking into restoring the services impacted in the US region only. Some requests may continue to experience errors while we deploy the new services.

The Konnect API is experiencing performance issues that is affecting its ability to process some requests in the US region only. This occurred during a rollout of a new deployment for the control plane service and it is being actively investigated.

Analytics operation is restored and ongoing verification is in progress. This incident has been resolved.

Recent data is available again. We continue to work on recovering a brief gap.

The issue has been identified and a fix is being implemented.

We are currently investigating this issue.

The Konnect API underwent performance issues that affected its ability to process requests, resulting in errors 499 and 504 when accessed either directly or through the Gateway Manager UI. The service has now been fully restored.

On Wednesday, April 10th, Konnect users with the predefined team permissions from Control Plane Admin and Control Plane Viewer were unable to view the Control Plane Overview page, instead receiving a message that they had insufficient permissions. This error was due to an API call that should only have been made for specific Control Plane types, but was being called for all Control Plane types, causing the 403. Once the cause of the issue was identified, a patch was rolled out to production to ensure the call could fail gracefully, and access was restored. The team is investing in additional monitoring and testing of specific permission groups to ensure we can avoid such disruptions for our predefined teams.

This incident has been resolved.

From 16:05 UTC to 22:57 UTC non-org admin users saw "Permission Denied" errors after logging in to Konnect. We identified the issue and deployed a fix.

This incident has been resolved.

A fix has been deployed and we are monitoring the result

After logging in to Konnect, an error is shown saying "unable to retrieve organization list". We have identified the issue and are preparing a fix.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We have identified the issue and are implementing fix for the potential reconnection issues that would be listed in data plane logs for customers.

Around 15:27 UTC connection and configuration reconciliation issues have been identified on customer control planes. This may result in reconnections of customer data planes and will have no impact on data plane proxy.

From 10:15Z to 10:55Z users may have experienced increased errors using Konnect; connections and UI. We are continuing to monitor for future issues; however, the incident has been resolved.

From 21:52Z to 22:10Z, users were unable to create new organizations in Konnect. This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.