Kong Outage History

Started Mar 08, 2026, 08:23 PM UTC· resolved Mar 08, 2026, 11:39 PM UTC

1. investigating Mar 08, 2026, 08:23 PM UTC

   The team is scaling up the message handling infrastructure to process the backlog. However, ongoing maintenance by our cloud service provider in the area is impacting our ability to scale the infrastructure. We will update as we are able to take further actions.

2. monitoring Mar 08, 2026, 09:29 PM UTC

   The cloud server provider has completed the maintenance. The message handling infrastructure is operating as expected and the backlog has been processed. We are continuing to monitor.

3. monitoring Mar 08, 2026, 10:34 PM UTC

   We are continuing to monitor for further issues with message processing.

4. resolved Mar 08, 2026, 11:39 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 04, 2026, 10:09 PM UTC· resolved Mar 04, 2026, 11:00 PM UTC

1. identified Mar 04, 2026, 10:09 PM UTC

   Kong Identity is unable to mint tokens in all regions. The team has identified the issue and is applying a fix.

2. identified Mar 04, 2026, 10:09 PM UTC

   We are continuing to work on a fix for this issue.

3. identified Mar 04, 2026, 10:30 PM UTC

   Fix has been applied for all auth servers in the US and EU. Updating other regions currently.

4. monitoring Mar 04, 2026, 10:35 PM UTC

   The fix has been applied to all regions. We are actively monitoring.

5. resolved Mar 04, 2026, 11:00 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 03, 2026, 03:25 PM UTC· resolved Mar 03, 2026, 03:35 PM UTC

1. resolved Mar 03, 2026, 05:23 PM UTC

   From 15:25z to 15:35z, the Konnect Control Plane saw an increase in dropped connections and re-connections in the US region from connected dataplanes. Dataplanes automatically re-connect when a connection is dropped, so there should be no observed impact, but customers may have noticed an increase in log volume if re-connections were occurring during this window.

Read the full incident report →

Started Mar 01, 2026, 01:08 PM UTC· resolved Jun 29, 2026, 03:56 PM UTC

1. investigating Mar 01, 2026, 01:08 PM UTC

   We are seeing increased 5xx in the ME Region. Our engineers are currently investigating the issue.

2. identified Mar 01, 2026, 02:45 PM UTC

   The increased error rates are associated with the AWS me-central-1 outage. Our engineers are monitoring the situation closely.

3. monitoring Mar 01, 2026, 06:41 PM UTC

   AWS continues to experience issues some services. However most of Konnect services are now recovered and operating as expected. Our engineers are closely monitoring the services and it's operational efficiency.

4. investigating Mar 01, 2026, 08:07 PM UTC

   We are currently observing renewed elevated 5XX error rates across multiple Konnect services in ME region. Our engineering team is actively investigating the issue and assessing customer impact. We will provide additional updates as soon as more information becomes available.

5. identified Mar 02, 2026, 01:54 AM UTC

   We are seeing many services in ME region recovering and some services are in degraded state. Dataplanes are not affected as part of this incident. All other Konnect regions are 100% operational and healthy. Our engineers are closely monitoring the situation. We will provide additional updates as soon as more information becomes available.

6. identified Mar 02, 2026, 06:31 AM UTC

   We are currently observing renewed elevated error rates across multiple Konnect services in ME region related to the AWS outage in that region.

7. identified Mar 02, 2026, 11:27 AM UTC

   The incident is ongoing. We are working closely with our cloud provider to monitor restoration efforts. Due to significant physical infrastructure damage in both the UAE and Bahrain regions, recovery is expected to take more time. We appreciate your patience as we work toward a full resolution.

8. identified Mar 02, 2026, 03:26 PM UTC

   We are actively migrating the affected services to operate on the two healthy Availability Zones in the Bahrain region (ME-SOUTH-1 Region). Our engineers are working to restore full service functionality and expect the migration to be completed within the next few hours. We will provide further updates as they become available. Thank you for your patience.

9. identified Mar 02, 2026, 05:26 PM UTC

   We are actively migrating the affected services to operate on other Availability Zones in the Bahrain region (ME-SOUTH-1 Region), but critical AWS services are not responding in that region. Our engineers are working to restore full service functionality and we are communicating with AWS to attempt to determine our failover options. At this time we cannot provide an ETA. We will provide further updates as they become available. Thank you for your patience.

10. identified Mar 02, 2026, 05:36 PM UTC

    Control Plane restored for Config Download and Telemetry We have restored the control plane and telemetry endpoints. Dataplanes can now connect to the control plane api at `me.cp0.konghq.com` and `me.tp0.konghq.com` This is a read-only instance set up for this incident. Configuration changes are still blocked. But now customers should be able to connect new dataplanes and download their configuration, as well as send telemetry. The Admin API for changing control plane configuration remains down.

11. identified Mar 02, 2026, 08:05 PM UTC

    We continue to make progress on restoring to a failover region for the Middle East region. Key AWS services to support our failover efforts are beginning to work as of 11am PST. The Konnect engineering team is working to restore and validate all services and data and will update in one hour. Please note the control plane and telemetry endpoints are already restored, so dataplanes can connect to Konnect.

12. identified Mar 02, 2026, 09:35 PM UTC

    We have restored partial service to Konnect. The UI is working again for Gateway Manager and Dev Portal, as well as all backing APIs. Dataplane connections to the Control Plane and Telemetry endpoints have been restored for 3 hours and should continue to work.

13. monitoring Mar 02, 2026, 09:39 PM UTC

    The Kong engineering team is now verifying restored services in the Middle East region

14. monitoring Mar 02, 2026, 09:50 PM UTC

    The following services have been restored: - All Konnect UI-accessible products except for Event Gateway and Metering - Dataplane connections to the Konnect Control Plane for configuration download and analytics upload Analytics data is delayed several hours. Konnect is accepting and persisting Analytics data, but it is not yet visible or queryable as we continue investigating restoring service.

15. monitoring Mar 02, 2026, 10:45 PM UTC

    Status Update (PDP – ME-SOUTH-1) User permission data replication in ME-SOUTH-1 (Bahrain) region are experiencing extended latencies. Mitigation has been implemented to cap this to 15 minutes. Updated data should now propagate within a maximum of 15 minutes. We continue to monitor the situation and will provide further updates as needed.

16. monitoring Mar 03, 2026, 03:03 AM UTC

    User permission data is now propagating normally again.

17. monitoring Mar 03, 2026, 03:45 AM UTC

    Service remains restored, and Kong engineers will continue to monitor the apps in the new region.

18. monitoring Mar 03, 2026, 05:13 AM UTC

    The data store for traces sent to Debugger is still experiencing issues in the Middle East region. Debugging sessions can be started but no spans will be able to be ingested. The team will update as they bring that service online.

19. monitoring Mar 03, 2026, 05:35 AM UTC

    Current Status Summary for Konnect Middle East Region: All services have been moved to our failover region in Middle East Almost all services are operational, with 2 caveats: - Analytics data is delayed several hours. Konnect is accepting and persisting Analytics data, but it is not yet visible or queryable as we continue investigating restoring service. - Debugger is unable to accept incoming trace data. While debugging sessions can be started, none of the trace data will be persisted in Konnect until the datastore for traces is restored. Everything else is back online. The team will update as we make progress on these remaining items.

20. monitoring Mar 03, 2026, 08:53 AM UTC

    Current Status Summary for Konnect Middle East Region: All services have been moved to our failover region in Middle East Almost all services are operational, with 2 caveats: - Analytics data is delayed several hours. Konnect is accepting and persisting Analytics data, but it is not yet visible or queryable as we continue investigating restoring service. - The Debugger is operational including trace data; however session logs will not be available in this region. - Observability is operational; however UUID to display name resolution will not be available in this region. Everything else is back online. The team will update as we make progress on these remaining items.

21. monitoring Mar 05, 2026, 01:16 PM UTC

    It was discovered that DNS for KIC reconciliation endpoints were still pointing to the out-of-service region. We have failed over these DNS records now to properly point to our new region. Customers using KIC would have seen 500s' during the reconciliation to Konnect. This was resolved at 10:30 UTC on March 5th.

22. monitoring Mar 20, 2026, 09:12 PM UTC

    Customers in the Middle East (Bahrain) region are operating in a reduced Availability Zone (AZ) configuration due to an ongoing AWS infrastructure issue. The platform remains available, but some customers in this region may experience intermittent performance degradation or elevated error rates. Data plane proxy traffic is not impacted. We are actively working with AWS to resolve the issue and will provide updates as more information becomes available.

23. monitoring Mar 23, 2026, 11:19 PM UTC

    We are observing increased error rates across services in the Konnect Middle East region. Data plane proxy traffic is not impacted. We are actively working with AWS to resolve the issue and will provide updates as more information becomes available.

24. monitoring Apr 02, 2026, 07:48 PM UTC

    Konnect Middle East Region: Indefinite Outage The Konnect Middle East Region is undergoing a prolonged outage due to the operational loss of AWS datacenters in the region. The duration of this outage is undetermined. As a result, we have no timeline for service restoration in the ME Region Customers are encouraged to migrate to one of our other Konnect control plane hosting regions in the EU, Australia, India or the United States. If assistance is required, please reach out to your Kong support representative.

25. resolved Jun 29, 2026, 03:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Started Feb 25, 2026, 12:17 PM UTC· resolved Feb 25, 2026, 02:57 PM UTC

1. investigating Feb 25, 2026, 12:17 PM UTC

   In the US Region of Konnect, changes relating to the ACE plugin are being delayed in their delivery to customer data planes. The changes that are delayed are: - Changes to ACE-managed API entity operations - App registrations to ACE-managed APIs

2. investigating Feb 25, 2026, 12:21 PM UTC

   We are continuing to investigate this issue.

3. monitoring Feb 25, 2026, 12:50 PM UTC

   A fix has been implemented, and the delays in delivery have been resolved. We are continuing to monitor the issue.

4. resolved Feb 25, 2026, 02:57 PM UTC

   The issue has been resolved. Delivery is now operating as expected.

Read the full incident report →

Started Feb 23, 2026, 11:32 AM UTC· resolved Feb 23, 2026, 11:51 AM UTC

1. investigating Feb 23, 2026, 11:32 AM UTC

   We are currently investigating a partial outage affecting the control plane in the US region. While some API requests are processing successfully, please note that configuration changes are not currently propagating to data plane nodes. Existing traffic on the data plane remains unaffected.

2. monitoring Feb 23, 2026, 11:43 AM UTC

   A fix has been implemented and configuration changes are now propagating correctly to data plane nodes

3. resolved Feb 23, 2026, 11:51 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 20, 2026, 02:51 PM UTC· resolved Feb 20, 2026, 05:35 PM UTC

1. investigating Feb 20, 2026, 02:51 PM UTC

   In the US geo, some users are experiencing an elevated error rate on some search and analytics APIs

2. identified Feb 20, 2026, 03:52 PM UTC

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

3. monitoring Feb 20, 2026, 05:06 PM UTC

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

4. resolved Feb 20, 2026, 05:35 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 11, 2026, 01:14 AM UTC· resolved Feb 11, 2026, 06:17 AM UTC

1. identified Feb 11, 2026, 01:14 AM UTC

   Some users may experience visual rendering issues on the Konnect login page, causing the page to appear broken or improperly formatted. Login functionality remains operational - users can still successfully authenticate despite the degraded appearance. The issue is intermittent and may resolve upon page refresh.

2. monitoring Feb 11, 2026, 04:32 AM UTC

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

3. resolved Feb 11, 2026, 06:17 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 08, 2026, 11:13 AM UTC· resolved Feb 09, 2026, 10:21 AM UTC

1. investigating Feb 08, 2026, 11:13 AM UTC

   We are currently investigating an issue with provisioning of new serverless gateways.

2. identified Feb 08, 2026, 12:28 PM UTC

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

3. monitoring Feb 08, 2026, 12:33 PM UTC

   A fix has been implemented and serverless gateways are now provisioning normally. We will continue to monitor the issue.

4. resolved Feb 09, 2026, 10:21 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 02, 2026, 08:33 PM UTC· resolved Feb 25, 2026, 12:20 PM UTC

1. monitoring Feb 02, 2026, 08:33 PM UTC

   We are progressively rolling out a new permissions system for Konnect. We are actively monitoring the rollout and don't expect customers to experience any access issues. Please contact support if you experience any issues.

2. resolved Feb 25, 2026, 12:20 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 29, 2026, 09:17 AM UTC· resolved Jan 29, 2026, 09:47 AM UTC

1. investigating Jan 29, 2026, 09:17 AM UTC

   Some customers may be seeing occasional connection resets during API calls to Konnect. This could also impact the UI which relies on Konnect APIs. Retrying the call or UI action should succeed as this appears to be a low percentage of calls impacted. Konnect engineers are looking into the issue and will update shortly.

2. investigating Jan 29, 2026, 09:17 AM UTC

   We are continuing to investigate this issue.

3. monitoring Jan 29, 2026, 09:40 AM UTC

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

4. resolved Jan 29, 2026, 09:47 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 18, 2025, 01:01 PM UTC· resolved Nov 18, 2025, 03:46 PM UTC

1. identified Nov 18, 2025, 01:01 PM UTC

   Konnect portals are experiencing intermittent 500 errors due to a third-party service provider outage, customers might encounter errors viewing and accessing developer portals.

2. identified Nov 18, 2025, 01:36 PM UTC

   Email logins to Insomnia are currently blocked due to an outage with a third-party service provider. SSO authentication is not affected. We are monitoring the third-party provider status closely.

3. monitoring Nov 18, 2025, 03:03 PM UTC

   The third-party provider believes to have resolved the incident. We will continue to monitor the third-party provider status closely.

4. resolved Nov 18, 2025, 03:46 PM UTC

   We are no longer seeing intermittent errors in Insomnia and Konnect Portals. We will continue to monitor the third-party provider status closely.

Read the full incident report →

Started Nov 06, 2025, 03:30 PM UTC· resolved Nov 06, 2025, 07:20 PM UTC

1. resolved Dec 19, 2025, 03:12 AM UTC

   This is an after-the-fact incident being reported as it was determined that a breaking API change was in production for some time on November 6th, 2025. On November 6 2025, for a period from 15:40 UTC to 19:20 UTC a breaking change to the Konnect API's certificate management endpoints was deployed, causing SNI’s to be disassociated with Certificates if Certificate updates did not include the full SNI list in each update. For users of the Kong Operator, which manages SNIs and Certificates separately and reconciles frequently, this resulted in SNI’s being deleted almost as soon as the API change was deployed to Konnect. Kong has reached out directly to impacted customers.

2. postmortem Dec 19, 2025, 03:12 AM UTC

   # Summary On _**November 6 2025**_, a breaking change to the Konnect API's certificate management endpoints caused SNI’s to be disassociated with Certificates if Certificate updates did not include the full SNI list in each update. ‌ For users of the Kong Operator, which manages SNIs and Certificates separately and reconciles frequently, this resulted in SNI’s being deleted almost as soon as the API change was deployed to Konnect. ## Additional Details The incident originated from an effort to align the Konnect API's behavior with the Kong Gateway API. While Kong Gateway allows Server Name Indicators \(SNIs\) to be managed directly through the Certificate endpoint, Konnect API historically managed certificates and SNIs as separate entities. To achieve consistency, the Konnect team updated the Create and Upsert endpoints to match Kong's behavior. ‌ However, this update introduced an unintended breaking change: when no SNIs were provided in an upsert request, the new logic purged all existing SNIs associated with the certificate instead of leaving them unchanged as in the previous implementation. ‌ This breaking change critically affected the Kong Operator, which manages certificates and SNIs through separate API calls using PUT requests. When the Kong Operator updated certificates without including SNI data, the new Koko logic deleted all associated SNIs. As a result, customer dataplanes fall back to using generic certificates, breaking customer traffic. ‌ ## Kong’s Response The issue was discovered when the CRE team detected service degradation for a customer and alerted the Konnect engineering team. The incident was resolved by reverting the API to its previous version across all regions. ‌ The Kong API does allow for PUT requests to not include every field for a resource. However, in some cases the API must respond with an HTTP400/Bad Request when the lack of some field could result in a destructive action. ‌ Therefore, the Konnect engineering team is adding a mechanism to our API design and testing automation that will block any API that allows critical resource information to be excluded from a request. In this case, the API change would have been blocked, as SNIs would be marked critical to a Certificate request.

Read the full incident report →

Started Oct 20, 2025, 08:26 PM UTC· resolved Oct 21, 2025, 02:07 PM UTC

1. investigating Oct 20, 2025, 08:26 PM UTC

   Konnect APIs and UI in US region is experiencing increased 502 due to the ongoing AWS incident. This does not impact any data planes.

2. investigating Oct 20, 2025, 08:41 PM UTC

   Our engineers are actively working on the issue. Currently the following APIs on the US region are identified to be affected by the outage: - Control Plane - API Products - Portal Management - API Catalog Management

3. identified Oct 20, 2025, 09:16 PM UTC

   An ongoing incident in the AWS us-east-1 region impacted some underlying services. Our teams are monitoring the situation closely to ensure Konnect data planes remain stable and working on alternative resolution paths to bring up affected US region services. All other regions are currently operating normally. Even though the Konnect UI may be showing empty results, we want to ensure that there is no data loss. We will provide the next update within 30 minutes or sooner.

4. identified Oct 20, 2025, 10:28 PM UTC

   We are continuing to work on a fix for the ongoing AWS outage and impacted underlying services. We will provide our next update within 60 minutes.

5. identified Oct 21, 2025, 12:19 AM UTC

   We’re seeing a steady decline in 502 error rates. Our engineering team is actively working to fully resolve the remaining errors in the AWS US region. All other regions are operating normally and remain unaffected. We’ll provide the next update within 60 minutes.

6. identified Oct 21, 2025, 12:29 AM UTC

   We’ve started to observe some Developer Portals being affected and becoming inaccessible. Our engineering team is fully aware of the situation and is actively working to restore all services.

7. identified Oct 21, 2025, 02:06 AM UTC

   We are currently observing intermittent issues affecting some Developer Portals in the AWS US region. Our team is actively working to resolve these. Error rates for the Konnect Service API have decreased significantly and are stabilizing, though we continue to monitor the situation. The next update will be provided within 60 minutes.

8. monitoring Oct 21, 2025, 03:44 AM UTC

   We’ve deployed a fix to address the issue impacting Konnect and Developer Portals in the AWS US regions. Since the change, we’re seeing a substantial decrease in error rates across both Konnect and Portal APIs. The affected services are steadily recovering and progressing toward a healthy operational state. Our engineering team is continuing to closely monitor the platform’s performance and stability to ensure that all systems remain fully functional. While most components are showing clear signs of improvement, we’ll continue active observation over the next several hours to confirm that the recovery is complete and sustained. All services across other regions in Konnect and Developer Portal remains unaffected and fully operational. We appreciate your patience as we worked to ensure full restoration of service and continued reliability across Konnect.

9. resolved Oct 21, 2025, 02:07 PM UTC

   The issue affecting Konnect and Developer Portals in the AWS US region has been fully resolved. Error rates on Konnect and Portal APIs have stabilized, and all services are now operating normally. Our team has implemented a fix and confirmed system recovery. We’ll continue to monitor to ensure ongoing stability. A detailed Root Cause Analysis (RCA) will be published shortly.

Read the full incident report →

Started Oct 20, 2025, 07:11 AM UTC· resolved Oct 21, 2025, 02:13 PM UTC

1. identified Oct 20, 2025, 01:47 PM UTC

   AWS Incident Reference: Ongoing service disruption in us-east-1 region Current Impact: Dedicated Cloud Gateways: • Existing Cloud Gateways are operating normally. • Provisioning of new network is currently unavailable due to the AWS issue. • There is potential impact if additional nodes need to be scaled in us-east-1. Other Konnect Services: • No impact observed at this time. Next Steps: We are continuing to monitor the AWS incident and will resume normal operations once AWS confirms full service restoration in us-east-1 (Virginia).

2. resolved Oct 21, 2025, 02:13 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 17, 2025, 09:58 AM UTC· resolved Oct 17, 2025, 12:03 PM UTC

1. investigating Oct 17, 2025, 09:58 AM UTC

   Some users are experiencing issues connecting DPs in the US region

2. monitoring Oct 17, 2025, 11:23 AM UTC

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

3. resolved Oct 17, 2025, 12:03 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 06, 2025, 04:00 PM UTC· resolved Oct 06, 2025, 05:54 PM UTC

1. investigating Oct 06, 2025, 04:00 PM UTC

   The UI for Audit Log Configuration is currently unavailable in Konnect. API's are still available for managing Audit Logging configurations. The team is investigating and will update shortly.

2. resolved Oct 06, 2025, 05:54 PM UTC

   The issue has been resolved and all users should now be able to see their Webhook configuration details properly. A more elaborated update about the issue will follow shortly.

3. postmortem Oct 17, 2025, 02:27 PM UTC

   On October 6, 2025, some Konnect customers encountered 404 errors when accessing the Audit Log Configuration screen in the Konnect UI. The issue was caused by a UI change that attempted to call a new version \(v3\) of the Audit log configuration API that was not yet fully enabled for all customers. Our engineering team quickly identified the issue and rolled back the change, fully restoring the audit log configuration from the UI. This incident did not affect the actual functionality and no customer audit logs were lost. The impact was limited to the display of the Audit Logs page. We’ve taken steps to strengthen monitoring, testing, and feature flag handling to help prevent similar incidents in the future.

Read the full incident report →

Started Oct 03, 2025, 06:09 PM UTC· resolved Oct 03, 2025, 06:50 PM UTC

1. investigating Oct 03, 2025, 07:07 PM UTC

   Some customer are experiencing issues making configurations changes to the control plane. This does not impact data plane operations.

2. investigating Oct 03, 2025, 07:07 PM UTC

   We are continuing to investigate this issue.

3. resolved Oct 03, 2025, 07:15 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 23, 2025, 05:58 PM UTC· resolved Sep 23, 2025, 06:20 PM UTC

1. investigating Sep 23, 2025, 05:58 PM UTC

   We are investigating an issue with Konnect login.

2. identified Sep 23, 2025, 06:11 PM UTC

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

3. monitoring Sep 23, 2025, 06:19 PM UTC

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

4. resolved Sep 23, 2025, 06:20 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 23, 2025, 04:57 PM UTC· resolved Jul 23, 2025, 05:04 PM UTC

1. monitoring Jul 23, 2025, 04:57 PM UTC

   This is only impacting Portal customers

2. monitoring Jul 23, 2025, 04:58 PM UTC

   We are continuing to monitor for any further issues.

3. resolved Jul 23, 2025, 05:04 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 22, 2025, 06:30 PM UTC· resolved Jul 22, 2025, 08:10 PM UTC

1. investigating Jul 22, 2025, 06:30 PM UTC

   Provisioning times for new Cloud Gateway control planes have returned to normal. We performed several test provisions and confirmed that the issue has been resolved

2. investigating Jul 22, 2025, 08:09 PM UTC

   We are continuing to investigate this issue.

3. resolved Jul 22, 2025, 08:10 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 17, 2025, 11:51 AM UTC· resolved Jul 17, 2025, 12:27 PM UTC

1. investigating Jul 17, 2025, 11:51 AM UTC

   Our corporate website, konghq.com, is currently unreachable. This has no impact on any of our cloud services.

2. monitoring Jul 17, 2025, 12:15 PM UTC

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

3. resolved Jul 17, 2025, 12:27 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 16, 2025, 03:03 PM UTC· resolved Jul 16, 2025, 05:05 PM UTC

1. investigating Jul 16, 2025, 03:03 PM UTC

   Some clients using Konnect APIs over Private Link are experiencing unexpected rate limiting. This has been identified as an issue with our edge proxy failing to differentiate different clients for rate limits. The team is currently working to resolve and restore full rate limit capacity to all clients

2. identified Jul 16, 2025, 04:32 PM UTC

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

3. monitoring Jul 16, 2025, 04:33 PM UTC

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

4. resolved Jul 16, 2025, 05:05 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 12, 2025, 06:46 PM UTC· resolved Jun 13, 2025, 03:29 AM UTC

1. investigating Jun 12, 2025, 06:46 PM UTC

   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

2. monitoring Jun 12, 2025, 11:38 PM UTC

   Our upstream provider has noted that everything is functioning correctly on their end now, and https://app.insomnia.rest/ is functioning normally now. We'll keep an eye on the numbers for some time before considering this fully resolved.

3. resolved Jun 13, 2025, 03:29 AM UTC

   This incident has been resolved.

Read the full incident report →