Previous incidents
demo.goharbor.io and registry.goharbor.io are down
Resolved Dec 05 at 08:01am CET
demo.goharbor.io recovered.
3 previous updates
demo.goharbor.io and registry.goharbor.io are down
Resolved Dec 03 at 08:01am CET
demo.goharbor.io recovered.
3 previous updates
demo.goharbor.io and registry.goharbor.io are down
Resolved Dec 02 at 08:02am CET
demo.goharbor.io recovered.
3 previous updates
demo.goharbor.io and registry.goharbor.io are down
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
registry.goharbor.io is down
Resolved Nov 30 at 06:55am CET
registry.goharbor.io recovered.
1 previous update
demo.goharbor.io and registry.goharbor.io are down
Resolved Nov 03 at 07:19am CET
demo.goharbor.io recovered.
3 previous updates
demo.goharbor.io is down
Resolved Oct 22 at 02:04pm CEST
demo.goharbor.io recovered.
1 previous update