Issue was ongoing after incident

We had a major outage today related to an incident. The weird thing is that the incident continued even after it was marked as resolved, as shown in the image.

A restart did the trick, which pointed me to a possible application issue. But, oddly enough, our observability platform did not catch any database high latency or RabbitMQ publish latency after the incident period.

Our issue is already solved after a restart, but maybe other users are also suffering from the same issue and the incident wasn't actually solved? Just letting y'all know

image.png

Attachments

1 Replies

theblondealex
HOBBY

5 days ago

I think I’ve had a similar thing this evening seeing big latency issues


Welcome!

Sign in to your Railway account to join the conversation.

Loading...