All Systems Operational

Uptime over the past 90 days. View historical uptime.
API ? Operational
90 days ago
100.0 % uptime
Today
Git Operational
90 days ago
99.97 % uptime
Today
Integrations Operational
90 days ago
100.0 % uptime
Today
Login Operational
90 days ago
100.0 % uptime
Today
Orchestration Operational
90 days ago
100.0 % uptime
Today
Webapp ? Operational
90 days ago
99.97 % uptime
Today
Features Operational
90 days ago
100.0 % uptime
Today
Alerts Operational
90 days ago
100.0 % uptime
Today
Data Exports Operational
90 days ago
100.0 % uptime
Today
Data Tests Operational
90 days ago
100.0 % uptime
Today
Modeling Operational
90 days ago
100.0 % uptime
Today
Publishing Operational
90 days ago
100.0 % uptime
Today
Webhooks Operational
90 days ago
100.0 % uptime
Today
Third Party Infrastructure Operational
Chargebee API Operational
Contentful Assets CDN Operational
Contentful Content Delivery API Operational
Pusher Channels REST API Operational
Pusher Channels Webhooks Operational
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.

May 15, 2025

No incidents reported today.

May 14, 2025

No incidents reported.

May 13, 2025

No incidents reported.

May 12, 2025

No incidents reported.

May 11, 2025

No incidents reported.

May 10, 2025

No incidents reported.

May 9, 2025

No incidents reported.

May 8, 2025
The system is sometimes unable to run dbt models
Resolved - This incident has been resolved.
May 8, 13:00 CEST
Monitoring - We’ve increased the resources for all dbt-related functions and services. Everything is working well now.
We’ll continue to monitor the performance for a while.
May 7, 17:20 CEST
Investigating - Users running builds or orchestrations may get confronted with an error saying "The system was unable to run dbt model. Please retry later or get in touch with Y42 support ". This is usually only affecting a single or a few jobs in a build but lead to the result being unfinished, i.e. not up-to-date.

Users have reported that simply re-running the affected DAG helps in the majority of cases.

We are currently examining the root cause of the issue and will keep you updated.
May 7, 14:27 CEST
May 7, 2025
May 6, 2025

No incidents reported.

May 5, 2025

No incidents reported.

May 4, 2025

No incidents reported.

May 3, 2025

No incidents reported.

May 2, 2025

No incidents reported.

May 1, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage