- Detected by Pingoru
- Aug 25, 2026, 01:01 PM UTC
- Resolved
- Aug 25, 2026, 02:05 PM UTC
- Duration
- 1h 4m
Affected: Dashboard
Timeline · 4 updates
-
investigating Aug 25, 2026, 01:01 PM UTC
We're aware that the Sevalla dashboard is currently inaccessible and are investigating the cause.
-
identified Aug 25, 2026, 01:14 PM UTC
We've identified the root cause of the issue affecting dashboard access and are now working on a fix. We'll post another update once it's resolved.
-
monitoring Aug 25, 2026, 01:45 PM UTC
A fix has been deployed and the dashboard is accessible again. We're monitoring the situation to confirm everything remains stable.
-
resolved Aug 25, 2026, 02:05 PM UTC
This incident has been resolved. The dashboard is fully accessible and has remained stable since the fix was deployed.
Read the full incident report →
- Detected by Pingoru
- Jun 22, 2026, 11:19 AM UTC
- Resolved
- Jun 22, 2026, 03:53 PM UTC
- Duration
- 4h 34m
Affected: Dashboard
Timeline · 5 updates
-
investigating Jun 22, 2026, 11:19 AM UTC
We are currently investigating an issue causing elevated load times on the Sevalla dashboard. Some users may also experience intermittent errors or difficulty accessing the dashboard entirely. Our team is actively working to identify the root cause and restore full performance.
-
investigating Jun 22, 2026, 01:52 PM UTC
We are continuing our investigation into the elevated load times and accessibility issues affecting the Sevalla dashboard. Our engineering team is currently analyzing performance metrics and infrastructure logs to isolate the root cause. We appreciate your patience.
-
identified Jun 22, 2026, 02:50 PM UTC
As part of our ongoing investigation, we need to temporarily take the Sevalla dashboard offline to apply a necessary fix. We expect this downtime to be short. Please note that all hosted customer applications and APIs remain fully operational and unaffected by this maintenance. We will provide an update as soon as the dashboard is brought back online.
-
monitoring Jun 22, 2026, 03:21 PM UTC
We have implemented a fix to resolve the underlying performance issues and are currently restoring access to the Sevalla dashboard. Initial metrics show that load times have returned to normal operating parameters. We are closely monitoring the system to ensure stability before fully closing this incident.
-
resolved Jun 22, 2026, 03:53 PM UTC
The performance and accessibility issues affecting the Sevalla dashboard have been resolved. Thank you for your patience and understanding while we worked to resolve this.
Read the full incident report →
- Detected by Pingoru
- Jun 19, 2026, 03:09 PM UTC
- Resolved
- Jun 20, 2026, 07:07 PM UTC
- Duration
- 1d 3h
Affected: Claude Claude API (api.anthropic.com)
Timeline · 4 updates
-
identified Jun 19, 2026, 03:09 PM UTC
We are currently experiencing an issue where our AI support assistant is failing to respond to user inquiries. This is due to upstream request timeouts with our LLM provider (Anthropic).
-
identified Jun 19, 2026, 06:54 PM UTC
We are continuing to experience upstream request timeouts with Anthropic, which is causing our AI support assistant to remain unresponsive.
-
monitoring Jun 20, 2026, 06:48 PM UTC
We have implemented a temporary workaround to bypass the ongoing Anthropic timeout issues. Our AI support assistant is once again responding to user inquiries. We are closely monitoring system performance, error rates, and response times to ensure stability.
-
resolved Jun 20, 2026, 07:07 PM UTC
The issues affecting our AI support assistant have been fully resolved. The upstream Anthropic request timeouts have subsided, and our system metrics have returned to normal, healthy levels.
Read the full incident report →
- Detected by Pingoru
- Jun 19, 2026, 07:03 AM UTC
- Resolved
- Jun 19, 2026, 07:09 AM UTC
- Duration
- 6m
Affected: ApplicationsStatic sites
Timeline · 3 updates
-
investigating Jun 19, 2026, 07:03 AM UTC
We're investigating issues affecting Git deployments and builds. The database backing our deployment service is experiencing degraded performance, which may cause builds to queue, run slowly, or fail. Running applications and previously deployed sites are not affected.
-
monitoring Jun 19, 2026, 07:04 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 19, 2026, 07:09 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 11, 2026, 11:45 AM UTC
- Resolved
- Jun 11, 2026, 12:06 PM UTC
- Duration
- 21m
Affected: Static sites
Timeline · 3 updates
-
identified Jun 11, 2026, 11:45 AM UTC
Since June 11, 2026, 04:14 UTC, an update to the Static Site deployment pipeline contains a regression that causes _redirects rules to be ignored on newly completed deployments. Affected sites may see: - 404 errors on all pages except files that exist in the build output - most visibly on single-page applications relying on a /* /index.html 200 fallback - Custom redirect rules (301/302), rewrites, and proxy rules not taking effect Who is affected Only sites that completed a deployment after June 11, 2026, 04:14 UTC and use a _redirects file. Sites that have not deployed since then are not affected. Site files themselves are served normally and no data was lost. _headers rules are not affected.
-
monitoring Jun 11, 2026, 11:54 AM UTC
The fix is fully deployed. Static Site deployments completed between June 11, 04:14 UTC and 11:52 UTC did not apply `_redirects` rules (custom redirects, rewrites, and SPA fallbacks), which could cause unexpected 404 errors. Deployments outside this window were not affected. If your site was deployed during this window, simply trigger a new deployment - redirects will work again immediately. No repository or configuration changes are needed. We are monitoring deployments and confirming full recovery. If you still see issues after redeploying, please contact support.
-
resolved Jun 11, 2026, 12:06 PM UTC
We have monitored deployments since the fix and confirmed redirects are working correctly. We apologize for the disruption.
Read the full incident report →
- Detected by Pingoru
- Jun 06, 2026, 07:53 PM UTC
- Resolved
- Jun 06, 2026, 08:52 PM UTC
- Duration
- 58m
Affected: Applications
Timeline · 4 updates
-
investigating Jun 06, 2026, 07:53 PM UTC
We are currently investigating an issue causing active deployments to become stuck in the europe-west2 region. Impact: Existing applications attempting to redeploy or update may experience indefinite hangs. Initial (first-time) deployments are unaffected. Workaround: If this is severely impacting your operations, you can bypass the issue by cloning your application and triggering a fresh deployment on the cloned instance. Our engineering team is actively hunting for the root cause. We will provide next updates as soon as we have more information.
-
identified Jun 06, 2026, 08:09 PM UTC
The root cause of the stuck deployments in europe-west2 has been identified. Our engineering team is currently working on a fix to restore normal deployment behavior.
-
monitoring Jun 06, 2026, 08:25 PM UTC
A fix has been implemented and deployed to resolve the stuck deployment issues in europe-west2. Deployments are now processing normally, and the previous workaround (cloning the application) is no longer required. We are monitoring the platform closely to ensure full stability.
-
resolved Jun 06, 2026, 08:52 PM UTC
The deployment issues in europe-west2 have been fully resolved. All deployment pipelines are operating normally. We appreciate your patience while we worked through this.
Read the full incident report →
- Detected by Pingoru
- Jun 01, 2026, 06:46 AM UTC
- Resolved
- Jun 01, 2026, 11:51 AM UTC
- Duration
- 5h 4m
Affected: Dashboard
Timeline · 7 updates
-
investigating Jun 01, 2026, 06:46 AM UTC
We are currently investigating an issue causing the Sevalla dashboard to be inaccessible. Our team is actively looking into the root cause, and we will provide updates here as soon as we have more information.
-
identified Jun 01, 2026, 07:12 AM UTC
We have identified the root cause of the dashboard inaccessibility. The issue stems from a disruption with our Apollo GraphQL integration. We are actively working together with the Apollo team to resolve the issue and restore full access as quickly as possible.
-
identified Jun 01, 2026, 07:46 AM UTC
We are continuing to work closely with the Apollo team to resolve the integration issue and restore full access to the dashboard.
-
identified Jun 01, 2026, 08:28 AM UTC
We have deployed a temporary workaround that should restore dashboard access for most users, but the underlying issue is not yet fully resolved and may surface again. We are continuing to work toward a permanent fix.
-
identified Jun 01, 2026, 08:52 AM UTC
Apollo has also officially acknowledged the underlying issue on their status page: Incident 01KT155KMJ3T4HB9G7AW1ZCKR3. The errors they are reporting match what we are seeing on our side. Our team remains actively engaged and is tracking their progress to ensure full dashboard functionality is permanently restored as soon as their platform stabilizes.
-
monitoring Jun 01, 2026, 10:48 AM UTC
A permanent fix has been successfully deployed, and dashboard access is fully restored. We are now monitoring the platform closely to ensure long-term stability and to confirm that the integration with Apollo GraphQL remains stable.
-
resolved Jun 01, 2026, 11:51 AM UTC
The issue has been fully resolved and all systems are operating normally. The permanent fix is holding, and our monitoring shows that dashboard access is fully stable. Thank you for your patience throughout this incident.
Read the full incident report →
- Detected by Pingoru
- Apr 29, 2026, 09:52 AM UTC
- Resolved
- Apr 29, 2026, 11:30 AM UTC
- Duration
- 1h 37m
Affected: Applications
Timeline · 3 updates
-
investigating Apr 29, 2026, 09:52 AM UTC
We are currently investigating an issue causing disrupted app deployments across the platform. During this time, you may notice varied behavior, including deployments becoming stuck in an "in-progress" state, duplicating, or failing to complete. Our engineering team is actively looking into the root cause of these disruptions and working toward a resolution.
-
monitoring Apr 29, 2026, 11:14 AM UTC
Our engineering team has identified the root cause of the deployment disruptions, and we've rolled out a series of fixes to address the issue. We are already observing a reduction in deployment errors and anticipate continued improvement as these fixes propagate. We are actively monitoring the situation to ensure platform stability and will provide another update as we confirm the system is fully recovering.
-
resolved Apr 29, 2026, 11:30 AM UTC
The fixes implemented for the recent deployment disruptions have been verified, and our systems are fully stabilized. Application deployments are now processing normally and are no longer experiencing issues with getting stuck, duplicating, or failing. Thank you for your patience while our team worked to resolve this incident. If you encounter any further issues with your deployments, please do not hesitate to contact our support team for assistance.
Read the full incident report →
- Detected by Pingoru
- Apr 28, 2026, 08:31 PM UTC
- Resolved
- Apr 28, 2026, 09:25 PM UTC
- Duration
- 54m
Affected: Applications
Timeline · 4 updates
-
investigating Apr 28, 2026, 08:31 PM UTC
We are currently investigating an issue where application deployments are getting stuck in an "in-progress" state. Because of this, subsequent deployment requests are being queued and are currently blocked. Our engineering team is actively identifying the root cause and working toward a resolution to clear the queue and restore deployment functionality.
-
identified Apr 28, 2026, 08:54 PM UTC
We have identified the root cause of the issue preventing application deployments from completing and causing subsequent deployments to be blocked. Our engineering team is currently working on implementing a fix to resolve the underlying issue and clear the backlog of queued deployments.
-
monitoring Apr 28, 2026, 09:10 PM UTC
We have implemented a fix and are monitoring system performance to ensure stability. As part of our recovery process, pending deployment tasks have been marked as "Skipped" to safely restore normal operations to the platform. The system is now accepting new deployment requests. If you have an urgent change for an application that was affected by this incident, please initiate a new deployment. We apologize for the inconvenience and appreciate your patience while we restored service.
-
resolved Apr 28, 2026, 09:25 PM UTC
We have confirmed that our deployment systems are fully stabilized and operating as expected. Following our earlier fix and the subsequent monitoring period, no further issues have been detected. Thank you for your patience during this incident. If you continue to experience any difficulties with your deployments, please reach out to our support team for further assistance.
Read the full incident report →
- Detected by Pingoru
- Apr 16, 2026, 09:00 AM UTC
- Resolved
- Apr 16, 2026, 09:10 AM UTC
- Duration
- 10m
Affected: Dashboard
Timeline · 3 updates
-
investigating Apr 16, 2026, 09:00 AM UTC
We are currently investigating the issue.
-
monitoring Apr 16, 2026, 09:08 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 16, 2026, 09:10 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 31, 2026, 02:54 PM UTC
- Resolved
- Mar 31, 2026, 07:00 PM UTC
- Duration
- 4h 6m
Affected: ApplicationsDatabasesAPI
Timeline · 3 updates
-
identified Mar 31, 2026, 02:54 PM UTC
Application and database resource metrics (CPU, memory, storage, instance count, restarts) are currently unavailable in the europe-west3 (Frankfurt) region. This affects both the Sevalla dashboard and the API. All other regions and traffic-based metrics (bandwidth, response times, requests) are not affected.
-
monitoring Mar 31, 2026, 06:44 PM UTC
We have deployed a potential fix for the issue affecting application and database resource metrics in the europe-west3 (Frankfurt) region. We are currently monitoring the systems to verify that data is populating correctly in both the dashboard and API. We will provide another update once we can confirm the issue is fully resolved.
-
resolved Mar 31, 2026, 07:00 PM UTC
The issue affecting application and database resource metrics in the europe-west3 (Frankfurt) region has been successfully resolved. All metric data is now populating correctly in both the Sevalla dashboard and the API. Thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Mar 12, 2026, 09:23 AM UTC
- Resolved
- Mar 12, 2026, 12:49 PM UTC
- Duration
- 3h 26m
Affected: Static sites
Timeline · 5 updates
-
investigating Mar 12, 2026, 09:23 AM UTC
We are investigating reports of intermittent 404 errors affecting our Static Site Hosting service. Our team is working to identify the root cause.
-
identified Mar 12, 2026, 10:04 AM UTC
Update: We have identified that this issue specifically affects domains using a Cloudflare "Orange-to-Orange" (proxied) setup. Workaround: Disabling the Cloudflare proxy (switching to "DNS only" / Grey Cloud) for affected domains resolves the 404 errors. Customers using Cloudflare for DNS only, or those not using Cloudflare, remain unaffected. We are continuing to investigate the underlying cause and will provide further updates as they become available.
-
identified Mar 12, 2026, 11:31 AM UTC
We are continuing to investigate the root cause and are working toward a resolution.
-
monitoring Mar 12, 2026, 11:49 AM UTC
We have deployed a fix for the 404 errors affecting proxied domains. We are currently monitoring the results. If you are still experiencing issues with your proxied setup, please let us know.
-
resolved Mar 12, 2026, 12:49 PM UTC
We now consider this incident resolved. If you disabled your Cloudflare proxy as a workaround, you may now try to safely re-enable it.
Read the full incident report →
- Detected by Pingoru
- Feb 03, 2026, 11:30 AM UTC
- Resolved
- Feb 03, 2026, 02:08 PM UTC
- Duration
- 2h 38m
Affected: Applications
Timeline · 5 updates
-
identified Feb 03, 2026, 11:30 AM UTC
We are currently experiencing an issue where a subset of customers are unable to view build and runtime logs for their applications. The root cause has been identified, and our engineering team is actively working on a solution. Note: This issue affects log visibility only; application uptime and performance are not impacted.
-
identified Feb 03, 2026, 12:10 PM UTC
We are continuing to implement the solution for this issue.
-
identified Feb 03, 2026, 01:14 PM UTC
We are continuing to implement the solution for this issue.
-
monitoring Feb 03, 2026, 01:32 PM UTC
A fix has been deployed and we are currently monitoring the results. Customers should see build and runtime logs beginning to reappear in the dashboard.
-
resolved Feb 03, 2026, 02:08 PM UTC
This issue has been resolved, and build and runtime logs are now fully available for all applications. We have confirmed that the underlying service is stable. We apologize for the interruption to your workflow.
Read the full incident report →
- Detected by Pingoru
- Feb 02, 2026, 04:30 PM UTC
- Resolved
- Feb 03, 2026, 10:00 AM UTC
- Duration
- 17h 30m
Timeline · 1 update
-
resolved Feb 03, 2026, 11:40 AM UTC
We have resolved an issue causing our public API endpoints to return 404 errors. The disruption was caused by a faulty deployment, which has been successfully reverted. All endpoints are now functioning normally. We apologize for any inconvenience this may have caused.
Read the full incident report →
- Detected by Pingoru
- Dec 20, 2025, 08:10 AM UTC
- Resolved
- Dec 20, 2025, 11:33 AM UTC
- Duration
- 3h 23m
Affected: ApplicationsDatabases
Timeline · 8 updates
-
investigating Dec 20, 2025, 08:10 AM UTC
We are currently investigating reports of service interruptions affecting applications and databases. Users may experience timeouts, error messages, or an inability to access the applications/databases.
-
investigating Dec 20, 2025, 08:25 AM UTC
We are continuing to investigate the root cause. Please be aware that service availability may be intermittent (coming online and going offline repeatedly).
-
investigating Dec 20, 2025, 08:45 AM UTC
We are continuing to investigate the root cause of the service interruption. Our team is trying to identify the issue.
-
investigating Dec 20, 2025, 09:20 AM UTC
We are continuing to investigate the root cause of the service interruption. Our team is trying to identify the issue.
-
identified Dec 20, 2025, 09:56 AM UTC
We have identified the root cause of the service disruption affecting. Our team is currently working on implementing a solution to restore full service.
-
identified Dec 20, 2025, 10:23 AM UTC
We are continuing our efforts to implement a solution for the identified issue.
-
monitoring Dec 20, 2025, 11:09 AM UTC
We have deployed a solution to address the issue, and early metrics indicate that services are recovering. The team will remain in a monitoring state to verify that stability holds and no regressions occur.
-
resolved Dec 20, 2025, 11:33 AM UTC
Our monitoring systems are showing healthy signals, and we have confirmed that all services are fully operational. We are now marking this incident as resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 19, 2025, 12:36 PM UTC
- Resolved
- Dec 19, 2025, 02:22 PM UTC
- Duration
- 1h 45m
Affected: DashboardApplicationsStatic sites
Timeline · 5 updates
-
identified Dec 19, 2025, 12:36 PM UTC
Our upstream provider, Cloudflare, is currently experiencing network issues that are affecting some of our services. Customers may encounter downtime for their workloads or have difficulty accessing our dashboard at app.sevalla.com. You can see the latest updates from Cloudflare over here: https://www.cloudflarestatus.com/incidents/msv92vykgtvp
-
identified Dec 19, 2025, 01:15 PM UTC
Cloudflare deployed a potential fix and is currently monitoring the outcome. We will continue to track Cloudflare's status and provide updates as they become available.
-
monitoring Dec 19, 2025, 02:03 PM UTC
Cloudflare has marked the incident as resolved. We will continue to monitor the situation closely to ensure everything remains stable.
-
monitoring Dec 19, 2025, 02:21 PM UTC
Our analytics show healthy response levels, so we are now closing this incident.
-
resolved Dec 19, 2025, 02:22 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 05, 2025, 09:12 AM UTC
- Resolved
- Dec 05, 2025, 10:39 AM UTC
- Duration
- 1h 26m
Affected: ApplicationsStatic sitesObject storageCloudflare API
Timeline · 3 updates
-
identified Dec 05, 2025, 09:12 AM UTC
We are currently investigating an issue with an upstream provider (Cloudflare) regarding their API availability. While our core services remain online, this is currently affecting the following management features: Static Sites: New deployments will likely fail. Application Deployments: Users may experience intermittent failures or delays. Domain Management: All domain-related settings are currently non-functional. We are monitoring the situation and will provide an update as soon as the upstream issue is resolved.
-
monitoring Dec 05, 2025, 09:24 AM UTC
Cloudflare has implemented a fix for the underlying API issues. We are currently observing our services returning to healthy operation, including deployments and domain management. We have updated our status to Monitoring and will confirm full resolution once we verify stability over the next few minutes.
-
resolved Dec 05, 2025, 10:39 AM UTC
The upstream issue with the Cloudflare API has been fully resolved. We have confirmed that domain settings, static site deployments, and application deployments are all functioning normally again.
Read the full incident report →
- Detected by Pingoru
- Nov 21, 2025, 11:32 AM UTC
- Resolved
- Nov 21, 2025, 01:56 PM UTC
- Duration
- 2h 23m
Affected: Applications
Timeline · 5 updates
-
investigating Nov 21, 2025, 11:32 AM UTC
We are investigating the issue.
-
identified Nov 21, 2025, 11:36 AM UTC
The issue has been identified, we are working on the solution.
-
identified Nov 21, 2025, 12:30 PM UTC
Our team is continuing to work on a resolution for this issue.
-
monitoring Nov 21, 2025, 12:54 PM UTC
We have deployed a fix for the issue and are continuing to monitor the situation to ensure stability.
-
resolved Nov 21, 2025, 01:56 PM UTC
We are no longer observing any errors and consider this incident resolved.
Read the full incident report →
Critical November 18, 2025 - Detected by Pingoru
- Nov 18, 2025, 11:45 AM UTC
- Resolved
- Nov 18, 2025, 04:22 PM UTC
- Duration
- 4h 37m
Affected: DashboardApplicationsStatic sitesObject storage
Timeline · 7 updates
-
identified Nov 18, 2025, 11:45 AM UTC
Initial findings indicate this is caused by an ongoing incident with our upstream provider, Cloudflare, which is affecting traffic routing. Our team is actively monitoring their status and we are ready to restore full service as soon as their systems recover.
-
identified Nov 18, 2025, 11:46 AM UTC
The outage is impacting applications, static sites, and object storage. Cloudflare's status page is updated. You can follow the progress there as well: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7
-
identified Nov 18, 2025, 12:47 PM UTC
Cloudflare is still actively continuing its investigation to determine the root cause of the issue.
-
monitoring Nov 18, 2025, 02:46 PM UTC
Cloudflare has updated its status to Monitoring. We are seeing our services come back online, but we continue to closely monitor Cloudflare's updates.
-
monitoring Nov 18, 2025, 03:34 PM UTC
We are still seeing errors, but at a much lower rate, and will continue to monitor the situation.
-
monitoring Nov 18, 2025, 03:57 PM UTC
While our Cloudflare edge-response error counts haven't fully returned to pre-incident levels, our charts look much healthier. We will continue to monitor the situation.
-
resolved Nov 18, 2025, 04:22 PM UTC
Our error counts are returning to normal levels, so we consider this incident resolved. If you notice anything unusual, please reach out to our support team. Thank you for your patience!
Read the full incident report →
- Detected by Pingoru
- Nov 04, 2025, 04:40 PM UTC
- Resolved
- Nov 04, 2025, 05:32 PM UTC
- Duration
- 51m
Affected: Static sites
Timeline · 3 updates
-
identified Nov 04, 2025, 04:40 PM UTC
We are currently investigating an issue with our static site build pipeline. You may experience build delays or failures, and site updates may not deploy as expected. Our team is working on a fix.
-
monitoring Nov 04, 2025, 05:25 PM UTC
We've deployed a potential fix for the issue and are now monitoring deployments.
-
resolved Nov 04, 2025, 05:32 PM UTC
We have confirmed the fix is stable. We recommend that anyone who experienced a failed deployment retry it now.
Read the full incident report →
- Detected by Pingoru
- Oct 15, 2025, 10:09 AM UTC
- Resolved
- Oct 15, 2025, 11:08 AM UTC
- Duration
- 58m
Affected: ApplicationsStatic sites
Timeline · 3 updates
-
investigating Oct 15, 2025, 10:09 AM UTC
We received reports of issues with Git authentication in Sevalla that are affecting connecting new Git accounts to our Application and Static Site hosting. The existing accounts are not affected. We are investigating the issue.
-
monitoring Oct 15, 2025, 10:36 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Oct 15, 2025, 11:08 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 30, 2025, 07:36 AM UTC
- Resolved
- Sep 30, 2025, 08:05 AM UTC
- Duration
- 28m
Affected: Applications
Timeline · 2 updates
-
identified Sep 30, 2025, 07:36 AM UTC
We are currently experiencing an issue that is preventing the creation of any new applications or preview deployments. This is due to hitting our DNS record quota on our Cloudflare account, which is blocking the automated DNS entry creation required for new application deployment. Existing applications are unaffected and continue to operate normally. Our team is actively working to resolve this. We are in the process of escalating a request with Cloudflare to increase our quota and are also auditing existing DNS records for potential cleanup.
-
resolved Sep 30, 2025, 08:05 AM UTC
We are happy to confirm that the issue affecting the provisioning of new applications and preview deployments has been resolved. Our infrastructure provider, Cloudflare, has successfully increased our DNS record quota. All deployment operations should now be functioning normally. We apologize for the service disruption and thank you for your patience while we worked to resolve this with our vendor.
Read the full incident report →
- Detected by Pingoru
- Sep 02, 2025, 09:55 AM UTC
- Resolved
- Sep 02, 2025, 12:53 PM UTC
- Duration
- 2h 58m
Affected: DashboardApplicationsDatabasesObject storageGoogle Cloud Platform Google Cloud SQL
Timeline · 5 updates
-
investigating Sep 02, 2025, 09:55 AM UTC
We're currently investigating an issue with one of our internal databases. You may experience failed queries on our dashboard pages.
-
identified Sep 02, 2025, 10:32 AM UTC
One of our Cloud SQL database instances fails to perform properly, so we are migrating to a new one. The Sevalla dashboard's features may be unresponsive until this process is complete and we provide a new update.
-
identified Sep 02, 2025, 11:54 AM UTC
This issue also affects our applications, database, and object storage products. They cannot be deployed, and the application, database, and object storage settings cannot be updated at the moment. We keep working on finding a solution.
-
monitoring Sep 02, 2025, 12:31 PM UTC
We've successfully migrated our database and have begun restoring our services. We will continue to monitor the solution. This change will allow for service updates and deployments to resume on the platform.
-
resolved Sep 02, 2025, 12:53 PM UTC
All system metrics are now healthy, and our services are fully operational again.
Read the full incident report →
- Detected by Pingoru
- Jul 18, 2025, 03:38 PM UTC
- Resolved
- Jul 18, 2025, 05:35 PM UTC
- Duration
- 1h 56m
Affected: ApplicationsDatabases
Timeline · 5 updates
-
investigating Jul 18, 2025, 03:38 PM UTC
We experience failed requests in us-east1 cluster. We are investigating the issue.
-
identified Jul 18, 2025, 04:06 PM UTC
Google Cloud has updated its status page to indicate elevated latency issues and error rates in us-east1, possibly due to a hardware problem. We are continuing to monitor this incident and apologize for any inconvenience caused.
-
monitoring Jul 18, 2025, 04:52 PM UTC
Based on GCP status page the fix has been implemented and released. https://status.cloud.google.com/incidents/8cY8jdUpEGGbsSMSQk7J
-
monitoring Jul 18, 2025, 04:52 PM UTC
We are continuing to monitor for any further issues.
-
resolved Jul 18, 2025, 05:35 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 02, 2025, 01:02 PM UTC
- Resolved
- Jul 02, 2025, 01:04 PM UTC
- Duration
- 1m
Affected: Applications
Timeline · 2 updates
-
investigating Jul 02, 2025, 01:02 PM UTC
App deployments are failing due to Ubuntu registry incident: https://status.canonical.com/
-
resolved Jul 02, 2025, 01:04 PM UTC
This incident has been resolved.
Read the full incident report →