The connectivity issues with our data provider, Tinybird, have been fully resolved. All systems are back to normal operation. We apologize for any inconvenience caused and thank you for your patience.

We are currently experiencing connectivity issues with our data provider, Tinybird. Our team is actively investigating the root cause. We will provide updates as more information becomes available. We apologize for any inconvenience this may cause.

The degraded performance affecting the Dashboard and Status Pages has been resolved. All systems are back to normal. We apologize for any inconvenience caused and thank you for your patience while we worked through the issue.

We are currently investigating degraded performance affecting the Dashboard and Status Pages. The issue appears to be related to our infrastructure provider (Fly/Turso). Our team is actively looking into the root cause.

The issue affecting access to the status page has been fully resolved. All systems are back to normal. We apologize for any inconvenience caused.

We are currently investigating reports of users being unable to access the status page. Our team is actively looking into the issue and will provide updates as we learn more.

The issue with our hosting provider has been resolved. Ping delays from our NRT (Tokyo, Japan) and BOM (Mumbai, India) Fly.io probes have returned to normal. All systems are operating as expected. We apologize for any inconvenience this may have caused.

We are currently investigating increased latency and delayed pings originating from our NRT (Tokyo, Japan) and BOM (Mumbai, India) Fly.io probes. This appears to be related to an issue with our hosting provider. Our team is actively monitoring the situation and will provide further updates as they become available.

The issue with our providers has been fully resolved.

A longer postmortem is coming in the next few days.

Due to some errors with our providers, we are seeing delays in cron jobs and connectivity issues with the dashboard.

We've noticed an issue where our uptime checker cron job has significantly failed between 16:01 CET and 23:27 CET. During that period, no monitor has been pinged.

The changes that have caused the issue have been rolled back.

All systems are now back online. We are continuously monitoring the situation.

We experienced an issue with our cloud infrastructure provider, which caused our database hosting provider to go down, affecting our APIs, status pages, and internal speed checker probes.

The database provider has since recovered, and our APIs and status pages are back online. However, we're still monitoring the ongoing outage with our cloud provider to restore our checker probes.

We have encountered a bug in out API that has updated all the monitors with a specific configuration. It occured yesterday, 22. July at 23h30 UTC. Until this morning, 23. July at 8h30 UTC, most monitors have experienced downtime. All monitors created past 23h30 UTC are not affected.

We have reverted the changes from a DB backup from the incident time and have fixed the bug.

We apologize for any inconvenience. To encounter such issue, we will increase the test coverage of our API to mitigate future issues.

A push has been fixed

We are experiencing an issue with data display on the dashboard. The root cause has been identified, and we are currently working on a solution.