Incident Description
A wide outage is affecting multiple external-facing applications in the fleet, all returning HTTP 502 Bad Gateway with Nginx headers.
Impacted Apps:
- revela (
https://revela.club)
- HTTP 502 Bad Gateway
- Latency: 71 ms
- nextrole (
https://nextrole.site)
- HTTP 502 Bad Gateway
- Latency: 68 ms
- intel (
https://intel.hyperdrift.io)
- HTTP 502 Bad Gateway
- Latency: 82 ms
- web3-capital (
https://web3.hyperdrift.io)
- HTTP 502 Bad Gateway
- Latency: 111 ms
Healthy Apps (Internal/Sandbox):
- sandbox (HTTP 200, 28ms)
- cargo (HTTP 200, 28ms)
Attempted Remediation:
- Attempted to run the healing runbook (
heal_service) on revela and nextrole.
- Result: Failed. No automated runbooks exist for these services (
no automated runbook for 'revela' — escalate to a human).
Diagnosis & Action Required:
This is a coordinated outage across multiple external services returning Nginx 502 errors, indicating a routing layer, reverse proxy, or upstream backend connection issue. Since these services are outside automated operational scope and lack wired runbooks, human intervention is required to investigate the routing layer or nginx reverse proxy configuration/backends.
Incident Description
A wide outage is affecting multiple external-facing applications in the fleet, all returning HTTP 502 Bad Gateway with Nginx headers.
Impacted Apps:
https://revela.club)https://nextrole.site)https://intel.hyperdrift.io)https://web3.hyperdrift.io)Healthy Apps (Internal/Sandbox):
Attempted Remediation:
heal_service) onrevelaandnextrole.no automated runbook for 'revela' — escalate to a human).Diagnosis & Action Required:
This is a coordinated outage across multiple external services returning Nginx 502 errors, indicating a routing layer, reverse proxy, or upstream backend connection issue. Since these services are outside automated operational scope and lack wired runbooks, human intervention is required to investigate the routing layer or nginx reverse proxy configuration/backends.