# Is Google Chrome 155 end-of-life?

As of 2026-10-13: No. Google Chrome 155 is supported; its end-of-life date is 2026-10-20 (in 7 days).

## Google Chrome release cycles

Status of every cycle as of 2026-10-13, newest first: supported, security-only (active support ended), eol or unknown.

| Cycle | Status |
|---|---|
| 155 | supported |
| 154 | eol |
| 153 | eol |
| 152 | eol |
| 151 | eol |
| 150 | eol |
| 149 | eol |
| 148 | eol |
| 147 | eol |
| 146 | eol |
| 145 | eol |
| 144 | eol |
| 143 | eol |
| 142 | eol |
| 141 | eol |
| 140 | eol |
| 139 | eol |
| 138 | eol |
| 137 | eol |
| 136 | eol |
| 135 | eol |
| 134 | eol |
| 133 | eol |
| 132 | eol |
| 131 | eol |
| 130 | eol |
| 129 | eol |
| 128 | eol |
| 127 | eol |
| 126 | eol |
| 125 | eol |
| 124 | eol |
| 123 | eol |
| 122 | eol |
| 121 | eol |
| 120 | eol |
| 119 | eol |
| 118 | eol |
| 117 | eol |
| 116 | eol |
| 115 | eol |
| 114 | eol |
| 113 | eol |
| 112 | eol |
| 111 | eol |
| 110 | eol |
| 109 | eol |
| 108 | eol |
| 107 | eol |
| 106 | eol |
| 105 | eol |
| 104 | eol |
| 103 | eol |
| 102 | eol |
| 101 | eol |
| 100 | eol |
| 99 | eol |
| 98 | eol |
| 97 | eol |
| 96 | eol |
| 95 | eol |
| 94 | eol |
| 93 | eol |
| 92 | eol |
| 91 | eol |
| 90 | eol |
| 89 | eol |
| 88 | eol |
| 87 | eol |
| 86 | eol |
| 85 | eol |
| 84 | eol |
| 83 | eol |
| 81 | eol |
| 80 | eol |
| 79 | eol |
| 78 | eol |
| 77 | eol |
| 76 | eol |
| 75 | eol |
| 74 | eol |
| 73 | eol |
| 72 | eol |
| 71 | eol |
| 70 | eol |
| 69 | eol |
| 68 | eol |
| 67 | eol |
| 66 | eol |
| 65 | eol |
| 64 | eol |
| 63 | eol |
| 62 | eol |
| 61 | eol |
| 60 | eol |
| 59 | eol |
| 58 | eol |
| 57 | eol |
| 56 | eol |
| 55 | eol |
| 54 | eol |
| 53 | eol |
| 52 | eol |
| 51 | eol |
| 50 | eol |
| 49 | eol |
| 48 | eol |
| 47 | eol |
| 46 | eol |
| 45 | eol |
| 44 | eol |
| 43 | eol |
| 42 | eol |
| 41 | eol |
| 40 | eol |
| 39 | eol |
| 38 | eol |
| 37 | eol |
| 36 | eol |
| 35 | eol |
| 34 | eol |
| 33 | eol |
| 32 | eol |
| 31 | eol |
| 30 | eol |
| 29 | eol |
| 28 | eol |
| 27 | eol |
| 26 | eol |
| 25 | eol |
| 24 | eol |
| 23 | eol |
| 22 | eol |
| 21 | eol |
| 20 | eol |
| 19 | eol |
| 18 | eol |
| 17 | eol |
| 16 | eol |
| 15 | eol |
| 14 | eol |
| 13 | eol |
| 12 | eol |
| 11 | eol |
| 10 | eol |
| 9 | eol |
| 8 | eol |
| 7 | eol |

## Dates, LTS and versions from the API

This page shows the status only. The signed API answer has every cycle with its release, support and end-of-life dates, LTS flag and latest version: [GET /v1/eol/chrome](https://g5joilnmeep4ntz3nwezxt5dmu.srv.us/v1/eol/chrome) ($0.001 per call, paid with x402 in USDC; no account, no API key).

- `GET /v1/eol/{product}/{cycle}`: one cycle, $0.001.
- `POST /v1/eol/check`: up to 50 product versions in one call, $0.01.
- `GET /v1/eol/image?image=node:18-alpine3.19`: a container image, its runtime and base OS, $0.005.
- `POST /v1/stack/check`: up to 50 product versions, 50 packages (purls) checked against OSV.dev and 100 CVEs checked against CISA KEV in one call, $0.012.
- `POST /v1/stack/watch`: the same stack check, then only what changed on each re-check with its signed token (an end-of-life date passed or near, a new KEV listing, a new advisory), $0.012.
- Free: [/v1/eol/preview](https://g5joilnmeep4ntz3nwezxt5dmu.srv.us/v1/eol/preview) (signed sample) and [/v1/validate?dataset=eol&id=chrome](https://g5joilnmeep4ntz3nwezxt5dmu.srv.us/v1/validate?dataset=eol&id=chrome).

## Source

Data from endoflife.date (https://endoflife.date), Copyright 2020 endoflife.date contributors, MIT License.

Snapshot `eol-20261012T184922Z-7ffc80b4`, data as of 2026-10-12T18:49:22Z, source last checked 2026-10-12T18:49:22.000Z.

Licences and attribution: [/licences](https://g5joilnmeep4ntz3nwezxt5dmu.srv.us/licences). How snapshots are made and verified: [/provenance](https://g5joilnmeep4ntz3nwezxt5dmu.srv.us/provenance).

Data is provided as is, without warranty of any kind. Payments are final. A 200 response is charged per request even if some items are reported unknown; 4xx/5xx are never charged. Every dataset is normalised (modified) from the sources named here, and no source endorses this service.
