We are undergoing temporary maintenance
Timeline · 2 updates
- monitoring Sep 26, 2026, 04:35 AM UTC
We will inform when this maintenance is concluded.
- resolved Sep 26, 2026, 05:14 AM UTC
This incident has been resolved.
Gastby had 12 outages in the last 2 years totaling 8h 0m of downtime — averaging 0.5 incidents per month.
There were 12 Gastby outages since February 27, 2025 totaling 8h 0m of downtime. Each is summarised below — incident details, duration, and resolution information.
We will inform when this maintenance is concluded.
This incident has been resolved.
We are currently investigating this incident.
This incident has been resolved.
We are currently investigating this incident..
This incident has been resolved..
We are currently investigating this incident..
An issue in our job scheduling system was identified and mitigated. Monitoring is being instrumented in order to detect potential issues with this system in the future..
We are currently investigating this incident..
We implemented a fix and are currently monitoring the result..
This incident has been resolved..
We are currently investigating this incident..
We are continuing to work on a fix for this incident..
This incident has been resolved..
We are currently investigating this incident..
An issue with an infrastructure upgrade has caused API to be unavailable. A fix is in progress..
We implemented a fix and are currently monitoring the result. Access to the platform looks stable..
This incident has been resolved..
We are currently investigating this incident..
We implemented a fix and are currently monitoring the result..
This incident has been resolved..
We are currently investigating this incident..
We implemented a fix and are currently monitoring the result..
This incident has been resolved..
We are currently investigating this incident..
This incident has been resolved..
We are continuing to work on a fix for this incident..
This incident has been resolved..
We are currently investigating this incident..
We are continuing to work on a fix for this incident..
This incident has been resolved..