Notice history

~0.0 ms

100.0% uptime

May 2026 · 100.0%Jun · 100.0%Jul · 100.0%

May 2026

Jun 2026

Jul 2026

99.99% uptime

May 2026 · 99.99%Jun · 100.0%Jul · 99.99%

May 2026

Jun 2026

Jul 2026

99.96% uptime

May 2026 · 100.0%Jun · 99.92%Jul · 99.97%

May 2026

Jun 2026

Jul 2026

99.96% uptime

May 2026 · 100.0%Jun · 100.0%Jul · 99.87%

May 2026

Jun 2026

Jul 2026

ResolvedJuly 20, 2026 at 8:47 PMUTC
Rise Chain is now operational! This update was created by an automated monitoring service.
InvestigatingJuly 20, 2026 at 8:42 PMUTC
Rise Chain cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedJuly 20, 2026 at 7:01 PMUTC
Rise Chain is now operational! This update was created by an automated monitoring service.
InvestigatingJuly 20, 2026 at 6:16 PMUTC
Rise Chain cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedJuly 06, 2026 at 4:19 PMUTC
Rise Chain is now operational! This update was created by an automated monitoring service.
InvestigatingJuly 06, 2026 at 4:14 PMUTC
Rise Chain cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedJuly 06, 2026 at 8:29 AMUTC
RISEx - REST API is now operational! This update was created by an automated monitoring service.
InvestigatingJuly 06, 2026 at 8:24 AMUTC
RISEx - REST API cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedJuly 15, 2026 at 2:05 AMUTC
This incident has been resolved.
InvestigatingJuly 06, 2026 at 8:23 AMUTC
RISEx Websocket cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedJune 15, 2026 at 5:03 AMUTC
RISEx Websocket is now operational! This update was created by an automated monitoring service.
InvestigatingJune 15, 2026 at 4:58 AMUTC
RISEx Websocket cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedJune 14, 2026 at 4:33 PMUTC
RISEx Websocket is now operational! This update was created by an automated monitoring service.
InvestigatingJune 14, 2026 at 4:28 PMUTC
RISEx Websocket cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedJune 14, 2026 at 4:27 PMUTC
RISEx Websocket is now operational! This update was created by an automated monitoring service.
InvestigatingJune 14, 2026 at 4:22 PMUTC
RISEx Websocket cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedJune 14, 2026 at 4:18 PMUTC
RISEx Websocket is now operational! This update was created by an automated monitoring service.
InvestigatingJune 14, 2026 at 4:13 PMUTC
RISEx Websocket cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedJune 14, 2026 at 4:11 PMUTC
RISEx Websocket is now operational! This update was created by an automated monitoring service.
InvestigatingJune 14, 2026 at 4:06 PMUTC
RISEx Websocket cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedMay 07, 2026 at 1:37 AMUTC
RISEx - REST API is now operational! This update was created by an automated monitoring service.
InvestigatingMay 07, 2026 at 1:32 AMUTC
RISEx - REST API cannot be accessed at the moment. This incident was created by an automated monitoring service.

May 2026 to Jul 2026

RISEx Mainnet - Notice history