# Grype-DB has no new Ubuntu data since 19 June **URL:** \ **Category:** Grype\ **Created:** [June 24, 2026, 6:17am UTC](https://anchorecommunity.discourse.group/t/grype-db-has-no-new-ubuntu-data-since-19-june/653 "2026-06-24T06:17:13Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![floric](https://yyz2.discourse-cdn.com/free1/user_avatar/anchorecommunity.discourse.group/floric/32/428_2.png) [@floric](https://anchorecommunity.discourse.group/u/floric)\ **Post date:** [June 24, 2026, 6:17am UTC](https://anchorecommunity.discourse.group/t/grype-db-has-no-new-ubuntu-data-since-19-june/653/1 "2026-06-24T06:17:13Z")
Hey 🙂 unfortunately the Grype-DB ist outdated since 06/19. Can you check it? > > > \*\*What happened\*\*: > > The Daily Data Sync and Incremental Data Sync GH Actions hav…e been failing since 6/19 on the ubuntu provider update. > > https://github.com/anchore/grype-db/actions/workflows/incremental-data-sync.yaml > https://github.com/anchore/grype-db/actions/workflows/daily-data-sync.yaml > > This is similar to an issue that happened a few weeks ago with the same provider > > \*\*What you expected to happen\*\*: > > The Daily Data Sync and Incremental Data Sync GH Actions succeed or are quickly actioned when they fail. Kind regards ---
**Author:** ![willmurphy](https://yyz2.discourse-cdn.com/free1/user_avatar/anchorecommunity.discourse.group/willmurphy/32/12_2.png) [@willmurphy](https://anchorecommunity.discourse.group/u/willmurphy)\ **Post date:** [June 24, 2026, 11:21am UTC](https://anchorecommunity.discourse.group/t/grype-db-has-no-new-ubuntu-data-since-19-june/653/2 "2026-06-24T11:21:36Z")
Hi @floric, thanks for the message! The ubuntu provider is indeed out of date since 6/19 and we are working on it. All other data sources are current. If you’re scanning images based on Ubuntu you are affected, but not otherwise. ## Some more details If you click into the data sync jobs, for example [Daily Data Sync · anchore/grype-db@fcee046 · GitHub](https://github.com/anchore/grype-db/actions/runs/27994317145) , you’ll see that only Ubuntu is failing. If you run `grype db update` and then `grype db providers` you’ll see this: ```auto grype db providers NAME VERSION PROCESSOR DATE CAPTURED INPUT DIGEST alma 1 vunnel@0.59.0.post3+53fcd5d 2026-06-24 00:47:53.137644 +0000 UTC xxh64:800e2a628f5e6a45 alpine 1 vunnel@0.59.0.post3+53fcd5d 2026-06-24 00:47:58.283033 +0000 UTC xxh64:8293380b449992a6 amazon 1 vunnel@0.59.0.post3+53fcd5d 2026-06-24 00:48:04.745742 +0000 UTC xxh64:46136a05bc533005 arch 1 vunnel@0.59.0.post3+53fcd5d 2026-06-24 00:47:31.61597 +0000 UTC xxh64:4b688d1121a3f939 bitnami 1 vunnel@0.59.0.post3+53fcd5d 2026-06-24 00:47:22.799018 +0000 UTC xxh64:42668095ff23f455 chainguard 1 vunnel@0.59.0.post3+53fcd5d 2026-06-24 00:47:29.172101 +0000 UTC xxh64:bff6223dcdf54ea7 chainguard-libraries 1 vunnel@0.59.0.post3+53fcd5d 2026-06-24 00:47:24.602654 +0000 UTC xxh64:de490fdd5e2c49bf debian 1 vunnel@0.59.0.post3+53fcd5d 2026-06-24 00:48:07.177664 +0000 UTC xxh64:815f1d4ceaa8ec3c echo 1 vunnel@0.59.0.post3+53fcd5d 2026-06-24 00:47:40.803571 +0000 UTC xxh64:d2dd8ecfcd899e7c eol 1 vunnel@0.59.0.post3+53fcd5d 2026-06-24 00:47:31.653371 +0000 UTC xxh64:16b3b7e97dca2c1d epss 1 vunnel@0.59.0.post3+53fcd5d 2026-06-24 00:48:19.431228 +0000 UTC xxh64:df0c0b590f165a1d fedora 1 vunnel@0.59.0.post3+53fcd5d 2026-06-24 00:47:37.177632 +0000 UTC xxh64:59de5af8cb4bec77 github 2 vunnel@0.59.0.post3+53fcd5d 2026-06-24 00:48:14.349678 +0000 UTC xxh64:13d059021ba988bf govulndb 1 vunnel@0.59.0.post3+53fcd5d 2026-06-24 00:47:35.725244 +0000 UTC xxh64:4073f908e994c171 hummingbird 2 vunnel@0.59.0.post3+53fcd5d 2026-06-24 00:47:39.36463 +0000 UTC xxh64:3034775c7c087ba6 kev 1 vunnel@0.59.0.post3+53fcd5d 2026-06-24 00:47:29.695445 +0000 UTC xxh64:d23917cb2ed85b59 mariner 1 vunnel@0.59.0.post3+53fcd5d 2026-06-24 00:47:52.922455 +0000 UTC xxh64:849baa4c47278594 minimos 1 vunnel@0.59.0.post3+53fcd5d 2026-06-24 00:47:59.021295 +0000 UTC xxh64:5cf0d21c744f8a95 nvd 2 vunnel@0.59.0.post3+53fcd5d 2026-06-24 00:48:18.140497 +0000 UTC xxh64:ebcb462639b257f9 oracle 1 vunnel@0.59.0.post3+53fcd5d 2026-06-24 00:47:38.859105 +0000 UTC xxh64:875cc1877f184e93 photon 1 vunnel@0.59.0.post3+53fcd5d 2026-06-24 00:47:32.931339 +0000 UTC xxh64:9d13e61685257d8f rhel 1 vunnel@0.59.0.post3+53fcd5d 2026-06-24 00:48:45.633416 +0000 UTC xxh64:02e2b15aabaf6e6f secureos 1 vunnel@0.59.0.post3+53fcd5d 2026-06-24 00:47:33.155303 +0000 UTC xxh64:27f86a7f7f78bae5 sles 1 vunnel@0.59.0.post3+53fcd5d 2026-06-24 00:48:04.858961 +0000 UTC xxh64:e28c864cf93683f9 ubuntu 3 vunnel@0.59.0.post3+53fcd5d **2026-06-19** 01:08:48.114406 +0000 UTC xxh64:71c1a6cf1bf7e431 wolfi 1 vunnel@0.59.0.post3+53fcd5d 2026-06-24 00:47:23.874056 +0000 UTC xxh64:19e4639259e0962a ``` Notice that only the ubuntu provider (I added `**` in the output) is out of date. We are actively working on a rewrite of the Ubuntu provider to help it be more operationally stable.