Notice history - Quivr - Status

100.0% uptime

Feb 2025 · 100.0%Mar · 100.0%Apr · 100.0%

Feb 2025

Mar 2025

Apr 2025

Operational

99.87% uptime

99.89% uptime

Feb 2025 · 99.84%Mar · 99.94%Apr · 99.88%

Feb 2025

Mar 2025

Apr 2025

99.85% uptime

Feb 2025 · 100.0%Mar · 99.85%Apr · 99.70%

Feb 2025

Mar 2025

Apr 2025

Notice history

View current status

Apr 2025

ResolvedApril 26, 2025 at 9:57 AMUTC
Rails (beta) is now operational! This update was created by an automated monitoring service.
InvestigatingApril 26, 2025 at 9:41 AMUTC
Rails (beta) cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedApril 26, 2025 at 9:57 AMUTC
Rails (production) is now operational! This update was created by an automated monitoring service.
InvestigatingApril 26, 2025 at 9:41 AMUTC
Rails (production) cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedApril 25, 2025 at 11:52 AMUTC
Rails (production) is now operational! This update was created by an automated monitoring service.
InvestigatingApril 25, 2025 at 11:46 AMUTC
Rails (production) cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedApril 13, 2025 at 1:34 PMUTC
Rails (beta) is now operational! This update was created by an automated monitoring service.
InvestigatingApril 13, 2025 at 12:18 PMUTC
Rails (beta) cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedApril 13, 2025 at 10:20 AMUTC
Rails (beta) is now operational! This update was created by an automated monitoring service.
InvestigatingApril 13, 2025 at 9:58 AMUTC
Rails (beta) cannot be accessed at the moment. This incident was created by an automated monitoring service.

Mar 2025

ResolvedMarch 27, 2025 at 9:40 PMUTC
Rails (production) is now operational! This update was created by an automated monitoring service.
InvestigatingMarch 27, 2025 at 9:39 PMUTC
Rails (production) cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedMarch 27, 2025 at 9:40 PMUTC
Rails (beta) is now operational! This update was created by an automated monitoring service.
InvestigatingMarch 27, 2025 at 9:39 PMUTC
Rails (beta) cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedMarch 25, 2025 at 2:19 PMUTC
Rails (production) is now operational! This update was created by an automated monitoring service.
InvestigatingMarch 25, 2025 at 2:17 PMUTC
Rails (production) cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedMarch 25, 2025 at 2:16 PMUTC
Rails (production) is now operational! This update was created by an automated monitoring service.
InvestigatingMarch 25, 2025 at 2:12 PMUTC
Rails (production) cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedMarch 25, 2025 at 2:11 PMUTC
Rails (production) is now operational! This update was created by an automated monitoring service.
InvestigatingMarch 25, 2025 at 2:10 PMUTC
Rails (production) cannot be accessed at the moment. This incident was created by an automated monitoring service.

Feb 2025

ResolvedFebruary 12, 2025 at 12:49 AMUTC
Rails (production) is now operational! This update was created by an automated monitoring service.
InvestigatingFebruary 12, 2025 at 12:48 AMUTC
Rails (production) cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedFebruary 12, 2025 at 12:43 AMUTC
Rails (production) is now operational! This update was created by an automated monitoring service.
InvestigatingFebruary 12, 2025 at 12:42 AMUTC
Rails (production) cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedFebruary 10, 2025 at 3:02 PMUTC
Rails (production) is now operational! This update was created by an automated monitoring service.
InvestigatingFebruary 10, 2025 at 2:57 PMUTC
Rails (production) cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedFebruary 10, 2025 at 12:49 PMUTC
Rails (production) is now operational! This update was created by an automated monitoring service.
InvestigatingFebruary 10, 2025 at 12:48 PMUTC
Rails (production) cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedFebruary 10, 2025 at 12:47 PMUTC
Rails (production) is now operational! This update was created by an automated monitoring service.
InvestigatingFebruary 10, 2025 at 12:42 PMUTC
Rails (production) cannot be accessed at the moment. This incident was created by an automated monitoring service.

Feb 2025 to Apr 2025