All Systems Operational

About This Site

This is Calamari's status page, where you can get updates on how our systems are doing. If there are interruptions to service, we will post a note here.

As always, if you are experiencing any issues with Calamari, don't hesitate to get in touch with us thorough the messenger on our website and we'll get back to you as soon as we can.

Uptime over the past 90 days. View historical uptime.
Web Apps - EU Operational
90 days ago
99.94 % uptime
Today
Public API - EU Operational
90 days ago
99.94 % uptime
Today
Email Notifications Operational
90 days ago
100.0 % uptime
Today
Mobile Apps Operational
90 days ago
100.0 % uptime
Today
Android App Operational
90 days ago
100.0 % uptime
Today
iOS App Operational
90 days ago
100.0 % uptime
Today
KIOSK App Operational
90 days ago
100.0 % uptime
Today
Web Apps - US Operational
90 days ago
99.96 % uptime
Today
Web Apps - ASIA Operational
90 days ago
99.96 % uptime
Today
Public API - US Operational
90 days ago
99.96 % uptime
Today
Public API - ASIA Operational
90 days ago
99.96 % uptime
Today
Intercom - Messenger ? Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Apr 2, 2025

No incidents reported today.

Apr 1, 2025

No incidents reported.

Mar 31, 2025
10:01:57 2025.03.31 Incident detected in eu-west-1 region [RESOLVED]
Resolved - The issue has been resolved at 10:32:00 on 2025.03.31. We're incredibly sorry for the inconvenience. This problem will be investigated further to make sure it won't happen again. We will add a postmortem shortly.
Mar 31, 10:32 CEST
Investigating - At 10:01:57 on 2025.03.31 our monitoring system discovered a problem in eu-west-1. Our team was notified and we're already working on fixing the issue.
Mar 31, 10:01 CEST
Mar 30, 2025
21:36:55 2025.03.30 Incident detected in eu-west-1 region [RESOLVED]
Resolved - The issue has been resolved at 21:57:01 on 2025.03.30. We're incredibly sorry for the inconvenience. This problem will be investigated further to make sure it won't happen again. We will add a postmortem shortly.
Mar 30, 21:57 CEST
Investigating - At 21:36:55 on 2025.03.30 our monitoring system discovered a problem in eu-west-1. Our team was notified and we're already working on fixing the issue.
Mar 30, 21:36 CEST
21:21:04 2025.03.30 Incident detected in EU region [RESOLVED]
Resolved - The issue has been resolved at 21:29:04 on 2025.03.30. We're incredibly sorry for the inconvenience. This problem will be investigated further to make sure it won't happen again. We will add a postmortem shortly.
Mar 30, 21:29 CEST
Investigating - At 21:21:04 on 2025.03.30 our monitoring system discovered a problem in EU. Our team was notified and we're already working on fixing the issue.
Mar 30, 21:21 CEST
Mar 29, 2025

No incidents reported.

Mar 28, 2025
14:07:06 2025.03.28 Incident detected in ap-southeast-1 region [RESOLVED]
Resolved - The issue has been resolved at 14:12:02 on 2025.03.28. We're incredibly sorry for the inconvenience. This problem will be investigated further to make sure it won't happen again. We will add a postmortem shortly.
Mar 28, 14:12 CET
Investigating - At 14:07:06 on 2025.03.28 our monitoring system discovered a problem in ap-southeast-1. Our team was notified and we're already working on fixing the issue.
Mar 28, 14:07 CET
Mar 27, 2025

No incidents reported.

Mar 26, 2025

No incidents reported.

Mar 25, 2025

No incidents reported.

Mar 24, 2025
17:22:06 2025.03.24 Incident detected in ap-southeast-1 region [RESOLVED]
Resolved - The issue has been resolved at 17:27:02 on 2025.03.24. We're incredibly sorry for the inconvenience. This problem will be investigated further to make sure it won't happen again. We will add a postmortem shortly.
Mar 24, 17:27 CET
Investigating - At 17:22:06 on 2025.03.24 our monitoring system discovered a problem in ap-southeast-1. Our team was notified and we're already working on fixing the issue.
Mar 24, 17:22 CET
13:42:06 2025.03.24 Incident detected in ap-southeast-1 region [RESOLVED]
Resolved - The issue has been resolved at 13:47:04 on 2025.03.24. We're incredibly sorry for the inconvenience. This problem will be investigated further to make sure it won't happen again. We will add a postmortem shortly.
Mar 24, 13:47 CET
Investigating - At 13:42:06 on 2025.03.24 our monitoring system discovered a problem in ap-southeast-1. Our team was notified and we're already working on fixing the issue.
Mar 24, 13:42 CET
Mar 23, 2025

No incidents reported.

Mar 22, 2025

No incidents reported.

Mar 21, 2025
15:22:05 2025.03.21 Incident detected in ap-southeast-1 region [RESOLVED]
Resolved - The issue has been resolved at 15:27:07 on 2025.03.21. We're incredibly sorry for the inconvenience. This problem will be investigated further to make sure it won't happen again. We will add a postmortem shortly.
Mar 21, 15:27 CET
Investigating - At 15:22:05 on 2025.03.21 our monitoring system discovered a problem in ap-southeast-1. Our team was notified and we're already working on fixing the issue.
Mar 21, 15:22 CET
Mar 20, 2025
15:47:06 2025.03.20 Incident detected in ap-southeast-1 region [RESOLVED]
Resolved - The issue has been resolved at 15:52:04 on 2025.03.20. We're incredibly sorry for the inconvenience. This problem will be investigated further to make sure it won't happen again. We will add a postmortem shortly.
Mar 20, 15:52 CET
Investigating - At 15:47:06 on 2025.03.20 our monitoring system discovered a problem in ap-southeast-1. Our team was notified and we're already working on fixing the issue.
Mar 20, 15:47 CET
13:02:05 2025.03.20 Incident detected in ap-southeast-1 region [RESOLVED]
Resolved - The issue has been resolved at 13:07:06 on 2025.03.20. We're incredibly sorry for the inconvenience. This problem will be investigated further to make sure it won't happen again. We will add a postmortem shortly.
Mar 20, 13:07 CET
Investigating - At 13:02:05 on 2025.03.20 our monitoring system discovered a problem in ap-southeast-1. Our team was notified and we're already working on fixing the issue.
Mar 20, 13:02 CET
Mar 19, 2025
11:27:05 2025.03.19 Incident detected in ap-southeast-1 region [RESOLVED]
Resolved - The issue has been resolved at 11:32:05 on 2025.03.19. We're incredibly sorry for the inconvenience. This problem will be investigated further to make sure it won't happen again. We will add a postmortem shortly.
Mar 19, 11:32 CET
Investigating - At 11:27:05 on 2025.03.19 our monitoring system discovered a problem in ap-southeast-1. Our team was notified and we're already working on fixing the issue.
Mar 19, 11:27 CET
← Incident History Powered by Atlassian Statuspage