About

What it is

EOL Watch is one timeline of things that are ending or changing in a cloud estate: service retirements, end of support for runtimes and versions, and breaking changes in infrastructure as code tools. It covers Azure, AWS, Google Cloud and Oracle Cloud. The timeline shows items that are upcoming or that ended within the last 90 days. Items that ended earlier are not shown there. A retirement or an end of support counts as ended. A breaking change does not end. It takes effect on its date and stays on its service page. A breaking change in an infrastructure as code tool is also listed for 7 days under "IaC this week" on the home page.

Retirement notices usually reach subscription administrators and owners, not the engineers who run the workload, and each vendor publishes its dates in a different place. This site puts those dates in one list.

Every item has:

• A link to its source: the vendor's page, or endoflife.date for the few products that have no other source.
• The effective date with its precision. A date the vendor gives as a month stays a month and carries the "approx." tag. Its countdown runs to the first day of that month, and the date counts as passed after the last day.
• A plain description of what is affected.
• The migration path the vendor documents, or a note that the vendor documents none.
• The date the item was last checked against its source.

EOL Watch is not affiliated with Microsoft, Amazon Web Services, Google or Oracle.

Methodology

Sources

Most items are built from an official source: vendor documentation, a vendor update feed, a vendor GitHub repository or the Terraform registry. Some version dates come from endoflife.date, a community project that links the vendor policy behind each date. For a few products there is no other source.

How items are verified

• Dates are read from the source by a script and recorded with the exact sentence or table cell they came from.
• Where endoflife.date and the vendor's own page both carry a date, the two are compared. A disagreement is held for a human decision instead of being published.
• Automated collection never publishes directly. A person reviews each new or changed item first.
• The description of each item (what breaks, what to do) is drafted with AI assistance from the vendor's text. Every sentence is tied to a quote from the official source, a script checks each quote against the live page, AI models from three different labs review the text, and a person approves it before it is published.

Check frequency

Each source is rechecked once a day. New and changed items wait for a person's review before they are published. The "Last checked" date on each item is the record of when that last happened for that item.

Sources policy

Items come from official vendor sources, plus endoflife.date for some version dates. For a few products there is no other source. Nothing is typed from memory. A value the vendor does not state is shown as "Not stated by vendor", and a date the vendor gives as a month, a quarter or a year is never narrowed to a day. For an item tracked through endoflife.date alone, the label reads "Not stated in the source".

Corrections policy

Anyone can report a missed or wrong item with the report form. A report needs a link that starts with https://. Add the link to the vendor's page if you have one. A report without a vendor link is flagged and takes longer to review. A person reviews each report before anything is published or changed. Changes to published items (added, date changed, updated, withdrawn) are listed in the changelog.

Sponsorship policy

Sponsors never affect which items are listed or how they are described. Every sponsor placement is labeled. No vendor pays to be listed. The site carries no affiliate links.

Privacy

The estate check runs in your browser. The files you give it are read on your device and nothing is uploaded.

Page views are counted without cookies, by page path, referring site (its host name), country and day. No IP address is stored for page views and no third-party tracker is loaded. "Do Not Track" and "Global Privacy Control" signals turn counting off.

A path is counted as written when it has the shape of an address of this site: lowercase letters, digits, dots and hyphens between slashes. The part after a question mark is never counted. Any other address, for example one with capital letters, a space or an at sign, is counted as one shared not-found entry. A mistyped address that has that shape is counted as written.

A search that finds nothing is stored as its text, with no address and no user agent, so missing coverage shows up. It is not stored when the browser sends Do Not Track or Global Privacy Control, or when the text looks like an identifier (a GUID, a resource path that starts with /subscriptions/, or anything with an at sign).

The Markdown and JSON forms of the pages, the data addresses and the MCP endpoint, listed on the agent access page, need no cookie and set none. The site itself stores nothing about a request to them: no IP address, no user agent and no search text. The hosting platform may keep its own access logs.

The report form and the sponsor form store what you enter. To limit repeated submissions they may also store a keyed hash of your IP address that changes every day. A hash older than one day is erased at the next daily run, so none is kept longer than two days. The address itself is never stored.

Credits

endoflife.date is the community project whose API supplies and cross-checks some version dates.

How we compare

endoflife.date documents end of life dates and support lifecycles for a wide range of products, and offers the data through an API, with iCalendar support.

Azure Updates is Microsoft's page of updates on Azure products and features, with filters for product, status and update type.

EOL Watch adds one cross-cloud timeline that also carries service retirements and infrastructure as code breaking changes, with the migration path the vendor documents where there is one.