Sliplane Outage History

Sliplane is up right now

Sliplane had 21 outages in the last 2 years totaling 63h 32m of downtime, averaging 0.9 incidents per month.

There were 21 Sliplane outages since December 13, 2024 totaling 63h 32m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: sliplane.instatus.com

Minor October 21, 2026

Degraded network connectivity in Germany

Detected by Pingoru
Oct 21, 2026, 10:22 AM UTC
Resolved
Oct 21, 2026, 10:42 AM UTC
Duration
20m
Affected: ServerRemote Build Server
Timeline · 2 updates
  1. identified Oct 21, 2026, 10:22 AM UTC

    A core router outage at our infrastructure provider, Hetzner, caused degraded network connectivity for a small subset of users in our German region.

  2. resolved Oct 21, 2026, 10:42 AM UTC

    Network connectivity has been restored. The issue is resolved.

Read the full incident report →

Minor July 8, 2026

Deploys from Github are failing

Detected by Pingoru
Jul 08, 2026, 02:50 PM UTC
Resolved
Jul 08, 2026, 03:10 PM UTC
Duration
19m
Affected: Remote Build Server
Timeline · 2 updates
  1. identified Jul 08, 2026, 02:50 PM UTC

    We are continuing to work on a fix for this incident.

  2. resolved Jul 08, 2026, 03:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 23, 2026

Logs and Metrics unavailable

Detected by Pingoru
Jun 23, 2026, 09:48 AM UTC
Resolved
Jun 23, 2026, 09:52 AM UTC
Duration
3m
Affected: DashboardPublic API
Timeline · 2 updates
  1. investigating Jun 23, 2026, 09:48 AM UTC

    We are currently investigating this incident.

  2. resolved Jun 23, 2026, 09:52 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 23, 2026

API is unreachable

Detected by Pingoru
Apr 23, 2026, 07:42 AM UTC
Resolved
Apr 23, 2026, 07:47 AM UTC
Duration
5m
Timeline · 2 updates
  1. investigating Apr 23, 2026, 07:42 AM UTC

    We are currently investigating this incident..

  2. resolved Apr 23, 2026, 07:47 AM UTC

    This incident has been resolved..

Read the full incident report →

Minor February 4, 2026

Creating new Servers not working

Detected by Pingoru
Feb 04, 2026, 11:08 AM UTC
Resolved
Feb 04, 2026, 11:27 AM UTC
Duration
19m
Timeline · 2 updates
  1. identified Feb 04, 2026, 11:08 AM UTC

    We are continuing to work on a fix for this incident..

  2. resolved Feb 04, 2026, 11:27 AM UTC

    This incident has been resolved..

Read the full incident report →

Minor January 2, 2026

Deploying services does not work on new servers

Detected by Pingoru
Jan 02, 2026, 12:30 PM UTC
Resolved
Jan 02, 2026, 02:12 PM UTC
Duration
1h 42m
Timeline · 3 updates
  1. investigating Jan 02, 2026, 12:30 PM UTC

    We are currently investigating this incident..

  2. monitoring Jan 02, 2026, 02:12 PM UTC

    We implemented a fix and are currently monitoring the result..

  3. resolved Jan 02, 2026, 02:12 PM UTC

    This incident has been resolved..

Read the full incident report →

Minor November 12, 2025

Creation of Base Servers not working

Detected by Pingoru
Nov 12, 2025, 04:38 PM UTC
Resolved
Nov 12, 2025, 05:03 PM UTC
Duration
24m
Timeline · 3 updates
  1. identified Nov 12, 2025, 04:38 PM UTC

    We are continuing to work on a fix for this incident..

  2. monitoring Nov 12, 2025, 04:47 PM UTC

    We implemented a fix and are currently monitoring the result..

  3. resolved Nov 12, 2025, 05:03 PM UTC

    This incident has been resolved..

Read the full incident report →

Minor October 20, 2025

Deploys from DockerHub not working

Detected by Pingoru
Oct 20, 2025, 09:02 AM UTC
Resolved
Oct 20, 2025, 09:45 AM UTC
Duration
43m
Timeline · 2 updates
  1. identified Oct 20, 2025, 09:02 AM UTC

    Due to DockerHub having a widespread outage ( ), deploying from DockerHub on Sliplane is currently not possible..

  2. resolved Oct 20, 2025, 09:45 AM UTC

    This incident has been resolved..

Read the full incident report →

Minor September 22, 2025

Deploys not working on new Servers

Detected by Pingoru
Sep 22, 2025, 12:27 PM UTC
Resolved
Sep 22, 2025, 01:59 PM UTC
Duration
1h 32m
Timeline · 2 updates
  1. investigating Sep 22, 2025, 12:27 PM UTC

    We are currently investigating this incident..

  2. resolved Sep 22, 2025, 01:59 PM UTC

    This incident has been resolved..

Read the full incident report →

Minor September 9, 2025

API Gateway returns 503 errors sometimes

Detected by Pingoru
Sep 09, 2025, 02:45 PM UTC
Resolved
Sep 09, 2025, 08:55 PM UTC
Duration
6h 10m
Timeline · 3 updates
  1. investigating Sep 09, 2025, 02:45 PM UTC

    We are currently investigating this incident..

  2. monitoring Sep 09, 2025, 04:24 PM UTC

    We implemented a fix and are currently monitoring the result..

  3. resolved Sep 09, 2025, 08:55 PM UTC

    This incident has been resolved..

Read the full incident report →

Major June 17, 2025

Github API down

Detected by Pingoru
Jun 17, 2025, 08:00 PM UTC
Resolved
Jun 17, 2025, 08:10 PM UTC
Duration
9m
Timeline · 2 updates
  1. identified Jun 17, 2025, 08:00 PM UTC

    The Github API is completely down. Deploys from Github are currently not possible. Existing services and deploys from DockerHub are not affected..

  2. resolved Jun 17, 2025, 08:10 PM UTC

    This incident has been resolved..

Read the full incident report →

Major June 3, 2025

Creating servers unavailable

Detected by Pingoru
Jun 03, 2025, 12:00 PM UTC
Resolved
Jun 03, 2025, 02:00 PM UTC
Duration
2h
Timeline · 2 updates
  1. identified Jun 03, 2025, 12:00 PM UTC

    Due to a fault in our upstream infrastructure provider creating new servers is currently not possible. Existing servers and services are not affected. We are continuing to work on a fix for this incident..

  2. resolved Jun 03, 2025, 02:00 PM UTC

    This incident has been resolved..

Read the full incident report →

Minor May 1, 2025

Dashboard not available

Detected by Pingoru
May 01, 2025, 07:57 AM UTC
Resolved
May 01, 2025, 08:11 AM UTC
Duration
13m
Timeline · 3 updates
  1. investigating May 01, 2025, 07:57 AM UTC

    We are currently investigating this incident..

  2. monitoring May 01, 2025, 08:10 AM UTC

    We implemented a fix and are currently monitoring the result..

  3. resolved May 01, 2025, 08:11 AM UTC

    This incident has been resolved..

Read the full incident report →

Minor January 31, 2025

Deploys from GitHub failing

Detected by Pingoru
Jan 31, 2025, 08:40 AM UTC
Resolved
Jan 31, 2025, 11:30 AM UTC
Duration
2h 50m
Timeline · 2 updates
  1. investigating Jan 31, 2025, 08:40 AM UTC

    After a successful build, pushing the image to our registry failed and the deploy did not go through. Garbage collection of the registry was not working, which caused the disk to fill up quickly until the registry was not able to process any more uploads. .

  2. resolved Jan 31, 2025, 11:30 AM UTC

    This incident has been resolved..

Read the full incident report →

Major December 18, 2024

Dashboard Unavailable

Detected by Pingoru
Dec 18, 2024, 05:45 AM UTC
Resolved
Dec 18, 2024, 06:45 AM UTC
Duration
1h
Timeline · 2 updates
  1. identified Dec 18, 2024, 05:45 AM UTC

    Hardware failure at our upstream provider..

  2. resolved Dec 18, 2024, 06:45 AM UTC

    This incident has been resolved..

Read the full incident report →

Major December 15, 2024

Dashboard unavailable

Detected by Pingoru
Dec 15, 2024, 04:36 PM UTC
Resolved
Dec 15, 2024, 04:44 PM UTC
Duration
8m
Timeline · 2 updates
  1. investigating Dec 15, 2024, 04:36 PM UTC

    We are currently investigating this incident..

  2. resolved Dec 15, 2024, 04:44 PM UTC

    This incident has been resolved. No customer servers where affected..

Read the full incident report →

Minor December 13, 2024

Github Deploys are failing

Detected by Pingoru
Dec 13, 2024, 09:49 AM UTC
Resolved
Dec 13, 2024, 10:15 AM UTC
Duration
26m
Timeline · 2 updates
  1. identified Dec 13, 2024, 09:49 AM UTC

    Deploys from Github are failing after a successful build during the registry push. Our Falkenstein Docker Registry had capacity issues and did not scale up fast enough..

  2. resolved Dec 13, 2024, 10:15 AM UTC

    This incident has been resolved..

Read the full incident report →