Issues Occurred in RPC

Summary

Found issues in the following monitors: Chain HTTP RPC, Chain Websocket RPC Monitors:

• Chain HTTP RPC: ❌

  Failed to get block number: HTTPSConnectionPool(host='allo-testnet.alt.technology', port=443): Max retries exceeded with url: / (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x7ff2a441e440>: Failed to resolve 'allo-testnet.alt.technology' ([Errno -5] No address associated with hostname)"))

• Chain Websocket RPC: ❌

  Failed to get block number: [Errno -5] No address associated with hostname

Events:

Open - Incident created (01:47 UTC — Sep 10)

Issue - Chain HTTP RPC: ❌ - Failed to get block number: HTTPSConnectionPool(host='allo-testnet.alt.technology', port=443): Max retries exceeded with url: / (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x7ff2a441e440>: Failed to resolve 'allo-testnet.alt.technology' ([Errno -5] No address associated with hostname)")) (01:47 UTC — Sep 10)

Issue - Chain Websocket RPC: ❌ - Failed to get block number: [Errno -5] No address associated with hostname (01:47 UTC — Sep 10)

Resolved - Chain HTTP RPC is back to normal (02:02 UTC — Sep 10)

Resolved - All issues resolved (01:39 UTC — Sep 17)