All chain-key ledgers 503(Service Unavailable) 17 hours ago

I have a system that monitors 43 ledgers and all chain-key were 503 for a few minutes 17 hours ago. Can anyone explain what might be the reason? An update?

The subnet hosting the chain-key ledgers was upgraded yesterday at about 1 PM UTC executing this upgrade proposal.
That’s probably the reason for the brief period of unavailability that you observed.

1 Like