---
title: "The error has been identified and the fix applied"
description: "Resolved · affects Kronos Platform API · Sep 1, 2026"
base_url: "https://kronos-status.openstatus.dev"
canonical: "https://kronos-status.openstatus.dev/events/report/2803"
homepage_url: "https://aquiles-ai.vercel.app/enterprise"
---

# The error has been identified and the fix applied

[Status](/.md) › [Events](/events.md) › The error has been identified and the fix applied

Sep 1, 2026 · 3 hours ago · affects: Kronos Platform API · 2 hours

## Updates

### + Resolved — Sep 2, 1:21 AM

affects: Kronos Platform API (operational)



### x Identified — Sep 1, 11:26 PM

affects: Kronos Platform API (degraded performance)

Given the configuration when bringing up our proxy instances alongside the API instances, it caused a `502 Bad Gateway` (`dial tcp 127.0.0.1:8081: connection refused`). By sharing the same network namespace, restarting only the proxy recreated its netns and left `app`/`postgres` on the old one, breaking communication via `127.0.0.1`. It was migrated to bridge `kronos-app-net` with `http://app:8081` and `postgres:5432`/`valkey`, leaving `curl https://kronos-demo.*/healthz` at `200`.

---

_Powered by [openstatus.dev](https://openstatus.dev)_