Issues Occurred in RPC

Summary

Found issues in the following monitors: 3rd-party HTTP RPC (Quicknode), AltLayer HTTP RPC Monitors:

• AltLayer HTTP RPC: ❌

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

• 3rd-party HTTP RPC (Quicknode): ❌

  The latest block number 5134879 is 1h17m39s old

Events:

Open - Incident created (06:23 UTC — Aug 15)

Issue - AltLayer HTTP RPC: ❌ - Failed to get block number: HTTPSConnectionPool(host='cyber.alt.technology', port=443): Max retries exceeded with url: / (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x7f8fae41a320>: Failed to resolve 'cyber.alt.technology' ([Errno -5] No address associated with hostname)")) (06:23 UTC — Aug 15)

Issue - 3rd-party HTTP RPC (Quicknode): ❌ - The latest block number 5134879 is 1h17m39s old (06:23 UTC — Aug 15)

Issue - AltLayer Websocket RPC: ❌ - Failed to get block number: [Errno -5] No address associated with hostname (06:23 UTC — Aug 15)

Resolved - AltLayer HTTP RPC is back to normal (15:53 UTC — Aug 15)

Resolved - AltLayer Websocket RPC is back to normal (16:53 UTC — Aug 15)

Resolved - All issues resolved (17:49 UTC — Aug 15)