Previous incidents
demo.goharbor.io is down
Resolved Feb 13, 2025 at 10:19am UTC
demo.goharbor.io recovered.
1 previous update
demo.goharbor.io and registry.goharbor.io are down
Resolved Feb 7, 2025 at 10:02am UTC
demo.goharbor.io recovered.
5 previous updates
demo.goharbor.io is down
Resolved Feb 4, 2025 at 9:34am UTC
demo.goharbor.io recovered.
1 previous update
registry.goharbor.io is down
Resolved Jan 31, 2025 at 10:23am UTC
registry.goharbor.io recovered.
1 previous update
demo.goharbor.io and registry.goharbor.io are down
Resolved Jan 30, 2025 at 10:07am UTC
demo.goharbor.io recovered.
3 previous updates
demo.goharbor.io and registry.goharbor.io are down
Resolved Jan 29, 2025 at 9:47am UTC
demo.goharbor.io recovered.
2 previous updates
demo.goharbor.io and registry.goharbor.io are down
Resolved Jan 28, 2025 at 9:16am UTC
demo.goharbor.io and registry.goharbor.io recovered.
1 previous update
demo.goharbor.io and registry.goharbor.io are down
Resolved Jan 27, 2025 at 9:28am UTC
registry.goharbor.io recovered.
5 previous updates
demo.goharbor.io and registry.goharbor.io are down
Resolved Jan 26, 2025 at 11:29am UTC
demo.goharbor.io recovered.
2 previous updates
demo.goharbor.io and registry.goharbor.io are down
Resolved Jan 25, 2025 at 9:42am UTC
demo.goharbor.io recovered.
2 previous updates
demo.goharbor.io and registry.goharbor.io are down
Resolved Jan 24, 2025 at 10:00am UTC
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
demo.goharbor.io and registry.goharbor.io are down
Resolved Dec 5, 2024 at 7:01am UTC
demo.goharbor.io recovered.
3 previous updates
demo.goharbor.io and registry.goharbor.io are down
Resolved Dec 3, 2024 at 7:01am UTC
demo.goharbor.io recovered.
3 previous updates
demo.goharbor.io and registry.goharbor.io are down
Resolved Dec 2, 2024 at 7:02am UTC
demo.goharbor.io recovered.
3 previous updates
demo.goharbor.io and registry.goharbor.io are down
Resolved Dec 1, 2024 at 9:26am UTC
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