Service outage on 'RPC' and 'Explorer'

Summary

The following monitors are down: Explorer Indexer Status, AltLayer Websocket RPC, Explorer Page, Explorer API, AltLayer HTTP RPC

Events:

Open - Monitor(s) are down (02:35 UTC — Jul 8)

Issue - Monitor Explorer Indexer Status is down: HTTPSConnectionPool(host=‘trex-mainnet-explorer.alt.technology’, port=443): Max retries exceeded with url: /api/v2/main-page/indexing-status (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x7f3b7f069ac0>: Failed to resolve ’trex-mainnet-explorer.alt.technology’ ([Errno -5] Name has no usable address)")) (02:35 UTC — Jul 8)

Issue - Monitor AltLayer Websocket RPC is down: Failed to get syncing status on trex-mainnet.alt.technology: [Errno -5] Name has no usable address (02:35 UTC — Jul 8)

Issue - Monitor Explorer Page is down: HTTPSConnectionPool(host=‘trex-mainnet-explorer.alt.technology’, port=443): Max retries exceeded with url: / (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x7f64450256d0>: Failed to resolve ’trex-mainnet-explorer.alt.technology’ ([Errno -5] Name has no usable address)")) (02:35 UTC — Jul 8)

Issue - Monitor Explorer API is down: HTTPSConnectionPool(host=‘trex-mainnet-explorer.alt.technology’, port=443): Max retries exceeded with url: /api/v2/main-page/blocks (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x7f6445d70da0>: Failed to resolve ’trex-mainnet-explorer.alt.technology’ ([Errno -5] Name has no usable address)")) (02:35 UTC — Jul 8)

Issue - Monitor AltLayer HTTP RPC is down: Failed to get syncing status on trex-mainnet.alt.technology: HTTPSConnectionPool(host=‘trex-mainnet.alt.technology’, port=443): Max retries exceeded with url: / (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x7f3b7f081940>: Failed to resolve ’trex-mainnet.alt.technology’ ([Errno -5] Name has no usable address)")) (02:35 UTC — Jul 8)

Note - Monitor(s) Explorer Page are up again (02:37 UTC — Jul 8)

Note - Monitor(s) Explorer API, Explorer Indexer Status are up again (02:39 UTC — Jul 8)

Resolved - resolved (02:40 UTC — Jul 8)