Previous incidents

February 2025
Feb 03, 2025
1 incident

demo.goharbor.io is down

Downtime

Resolved Feb 04 at 10:34am CET

demo.goharbor.io recovered.

1 previous update

January 2025
Jan 31, 2025
1 incident

registry.goharbor.io is down

Downtime

Resolved Jan 31 at 11:23am CET

registry.goharbor.io recovered.

1 previous update

Jan 30, 2025
1 incident

demo.goharbor.io and registry.goharbor.io are down

Downtime

Resolved Jan 30 at 11:07am CET

demo.goharbor.io recovered.

3 previous updates

Jan 29, 2025
1 incident

demo.goharbor.io and registry.goharbor.io are down

Downtime

Resolved Jan 29 at 10:47am CET

demo.goharbor.io recovered.

2 previous updates

Jan 28, 2025
1 incident

demo.goharbor.io and registry.goharbor.io are down

Downtime

Resolved Jan 28 at 10:16am CET

demo.goharbor.io and registry.goharbor.io recovered.

1 previous update

Jan 27, 2025
1 incident

demo.goharbor.io and registry.goharbor.io are down

Downtime

Resolved Jan 27 at 10:28am CET

registry.goharbor.io recovered.

5 previous updates

Jan 26, 2025
1 incident

demo.goharbor.io and registry.goharbor.io are down

Downtime

Resolved Jan 26 at 12:29pm CET

demo.goharbor.io recovered.

2 previous updates

Jan 25, 2025
1 incident

demo.goharbor.io and registry.goharbor.io are down

Downtime

Resolved Jan 25 at 10:42am CET

demo.goharbor.io recovered.

2 previous updates

Jan 24, 2025
1 incident

demo.goharbor.io and registry.goharbor.io are down

Downtime

Resolved Jan 24 at 11:00am CET

Services are back online.
we have been fetching outdated container images of Redis (not listed anymore on docker hub) and we ran into docker hub rate limit.

3 previous updates

December 2024
Dec 05, 2024
1 incident

demo.goharbor.io and registry.goharbor.io are down

Downtime

Resolved Dec 05 at 08:01am CET

demo.goharbor.io recovered.

3 previous updates

Dec 03, 2024
1 incident

demo.goharbor.io and registry.goharbor.io are down

Downtime

Resolved Dec 03 at 08:01am CET

demo.goharbor.io recovered.

3 previous updates

Dec 02, 2024
1 incident

demo.goharbor.io and registry.goharbor.io are down

Downtime

Resolved Dec 02 at 08:02am CET

demo.goharbor.io recovered.

3 previous updates

Dec 01, 2024
1 incident

demo.goharbor.io and registry.goharbor.io are down

Downtime

Resolved Dec 01 at 10:26am CET

An EKS node was automatically replaced with a new node, this resulted in the rescheduling of PODs. The rescheduling was not successful, as the Node reached the Dockerhub rate limit. This resulted that the pods could not start as expected.

The resolution was to update the service accounts to use a paying dockerhub account. this resolved the problem.

3 previous updates