Feeds and data exports
The site-wide and per-cloud feeds, calendar files and data exports, with their addresses. Copy an address into a feed reader, a calendar application or a script. Each item page also offers a calendar file for that single item.
All items
RSS feed
The most recently added items from all clouds that are upcoming or were added in the last 30 days, at most 100, in RSS format. The JSON and CSV exports carry every published item.
https://eolwatch.dev/feed.xmlAtom feed
The most recently added items from all clouds that are upcoming or were added in the last 30 days, at most 100, in Atom format. The JSON and CSV exports carry every published item.
https://eolwatch.dev/atom.xmlCalendar (iCalendar)
Upcoming effective dates as all-day events, all clouds.
https://eolwatch.dev/calendar.icsSubscribe in Outlook or Google Calendar: choose the option to add a calendar from a URL and paste the address. A date known only to the month, quarter or year is placed on the first day of that period, and the event title says the exact day is not stated. Items without an effective date are not in the calendar.
RSS feeds by cloud
Azure RSS feed
The most recently added Azure items that are upcoming or were added in the last 30 days, at most 100, in RSS format.
https://eolwatch.dev/feeds/azure.xmlAWS RSS feed
The most recently added AWS items that are upcoming or were added in the last 30 days, at most 100, in RSS format.
https://eolwatch.dev/feeds/aws.xmlGCP RSS feed
The most recently added GCP items that are upcoming or were added in the last 30 days, at most 100, in RSS format.
https://eolwatch.dev/feeds/gcp.xmlOCI RSS feed
The most recently added OCI items that are upcoming or were added in the last 30 days, at most 100, in RSS format.
https://eolwatch.dev/feeds/oci.xml
Calendars by cloud
Azure calendar
Upcoming Azure effective dates as all-day events.
https://eolwatch.dev/feeds/azure.icsSubscribe in Outlook or Google Calendar: choose the option to add a calendar from a URL and paste the address. A date known only to the month, quarter or year is placed on the first day of that period, and the event title says the exact day is not stated. Items without an effective date are not in the calendar.
AWS calendar
Upcoming AWS effective dates as all-day events.
https://eolwatch.dev/feeds/aws.icsSubscribe in Outlook or Google Calendar: choose the option to add a calendar from a URL and paste the address. A date known only to the month, quarter or year is placed on the first day of that period, and the event title says the exact day is not stated. Items without an effective date are not in the calendar.
GCP calendar
Upcoming GCP effective dates as all-day events.
https://eolwatch.dev/feeds/gcp.icsSubscribe in Outlook or Google Calendar: choose the option to add a calendar from a URL and paste the address. A date known only to the month, quarter or year is placed on the first day of that period, and the event title says the exact day is not stated. Items without an effective date are not in the calendar.
OCI calendar
Upcoming OCI effective dates as all-day events.
https://eolwatch.dev/feeds/oci.icsSubscribe in Outlook or Google Calendar: choose the option to add a calendar from a URL and paste the address. A date known only to the month, quarter or year is placed on the first day of that period, and the event title says the exact day is not stated. Items without an effective date are not in the calendar.
Data exports
JSON export
Published items as JSON. The file is one object: the items are in its items array, with the fields listed below, next to generated_at (when the file was built), site (the name and address of this site), count, license and schema.
https://eolwatch.dev/data/items.jsonCSV export
Published items as CSV: a header row, then one row per item. The X-Generated-At response header says when the file was built.
https://eolwatch.dev/data/items.csvEstate check rules
The rules the estate check runs in your browser, as JSON: the published items that carry match rules, and the tracked Terraform providers with their breaking releases.
https://eolwatch.dev/data/rules.json
For an agent or a script there is more than these files: every item, service, provider, cloud and category page has a Markdown and a JSON form, the JSON export answers filtered lists, and an MCP endpoint serves the same data. The agent access page lists the addresses.
Files for crawlers and tools
llms.txt
The index for agents: how to read the site, then links to the lists as Markdown and to the data addresses.
https://eolwatch.dev/llms.txtllms-full.txt
Every upcoming item in one text, with its effective date, cloud, service and type, its source and the address of its Markdown form. Its first lines say whether the summary of each item is in it.
https://eolwatch.dev/llms-full.txt
Export fields
The JSON and CSV exports carry the same fields, in this order.
| Field | Description |
|---|---|
| slug | Stable identifier of the item. Never changes once published. |
| title | Short headline of the lifecycle change. |
| summary | One or two plain sentences describing the change. |
| cloud | Cloud the item belongs to: azure, aws, gcp, oci or multi. |
| service | Display name of the affected service. |
| service_slug | URL-safe identifier of the service. |
| category | Kind of thing affected, for example service, runtime, kubernetes or database. |
| type | Kind of change: retirement, end_of_support or breaking_change. |
| announced_date | Date the vendor announced the change (YYYY-MM-DD), or null when not stated. |
| effective_date | Date the change takes effect (YYYY-MM-DD), or null when not announced. For month, quarter and year precision this is the first day of the period. |
| effective_precision | How exact effective_date is: day, month, quarter or year. |
| impact | What stops working and who is affected. |
| migration_path | Steps to take before the effective date. May contain Markdown. |
| replacement | Recommended replacement, or null when the vendor names none. |
| affected_versions | Versions affected. Array in JSON, joined with "; " in CSV. |
| source_url | Page the item was verified against: an official vendor page, or the endoflife.date page for the few products where it is the only source of the date. |
| extra_source_urls | Additional sources: official pages, or an endoflife.date page. Array in JSON, joined with "; " in CSV. |
| vendor_ref | Vendor reference for the announcement, or null. |
| last_checked_at | Timestamp (ISO 8601, UTC) of the last successful recheck against the source. |
| created_at | Timestamp (ISO 8601, UTC) when the item was first published here. |
| updated_at | Timestamp (ISO 8601, UTC) of the last change to the item. |
| url | Page for this item on the site. |
License
License: Not decided yet. The license for these exports has not been chosen yet, so no reuse terms are stated. Ask the site owner before you redistribute the data. Version dates taken from or cross-checked with endoflife.date remain subject to the license of that project.
Project behind those version dates: endoflife.date.
Calendar subscriptions with webcal addresses are on the calendar page.