Amazon Ads revised its Support Center article on the Amazon Ads status page on November 20, 2026, and the revised text describes a smaller, newer-sounding service than the one it documents. According to the help article, the status page shows "the current status of services like campaign creation and campaign management, ad delivery, and reporting for sponsored ads and DVA+." It lists nine features in four groups and names 19 countries across three regions. On the morning of November 21, the page at status.ads.amazon.com displayed 17 components in six groups, filed programmatic buying under the heading "Amazon DSP", and kept a row for Posts, the brand content feed Amazon closed in July 2025.
In Short
Amazon updated the help page for its Amazon Ads status page, the public site that shows whether campaign tools, ad delivery and reports are working, on November 20, 2026. The page is what advertisers, agencies and software makers check when something breaks, yet the help text lists nine monitored features in 19 countries while the live page shows 17 components, still says Amazon DSP instead of DVA+, and still tracks the discontinued Posts feature. The status page's machine-readable feed uses the older names as well, so monitoring tools built on it see "Amazon DSP" and "Creative management", not the labels in Amazon's newer documentation.
What the November 20 help page says
The article sits in the Support Center under Troubleshooting, beneath the Amazon Ads Agent header carried by Amazon's recent help pages. Its summary line is a single sentence: "Stay updated with the latest health status information of Amazon Ads services using the Amazon Ads Status page." When a disruption occurs, according to the page, the status site gives "more details about the event, including the description and status updates for that service."
Coverage is organised by region rather than by country. "The page shows the status of Amazon Ads at a region level," according to Amazon. "The status will apply to all countries in the region unless mentioned otherwise."
| Region | Countries named on the November 20 help page | Count |
|---|---|---|
| North and Latin America | Brazil, Canada, Mexico, United States | 4 |
| Europe, Middle East, and North Africa | Belgium, Egypt, France, India, Italy, Netherlands, Poland, Saudi Arabia, Spain, Sweden, United Arab Emirates, United Kingdom | 12 |
| Asia Pacific | Australia, Japan, Singapore | 3 |
| Total | 19 (PPC Land count) |
The page then states: "Current status will be provided for the following features." Four groups follow. Sponsored ads carries campaign creation, campaign management and ad delivery. DVA+ carries campaign creation, campaign management, "Ad (formerly known as Creative) Management" and ad delivery. A group headed "Measurements and Reports" carries Reports. Brand content carries Stores. That is nine features in all.
Four status levels can appear, according to the help page: No known issues, marked with a green tick; Informational, with a blue "i"; Degraded, with an orange warning triangle; and Disrupted, with a red exclamation mark. A note explains that the Last updated field records the time the status was last refreshed on the page, and that every time is displayed in the viewer's local time zone.
How Amazon says a status entry reads
The help page walks through one example entry and labels five parts of it. The example is a sponsored ads campaign creation problem, flagged with a red exclamation mark, carrying the message "We're having some issues with campaign creation and are working to fix them. We're sorry for any inconvenience." Its timestamp reads March 08, 2023 at 12:02 - two months before Amazon's public launch note for the status page, dated May 10, 2023. According to Amazon, the five parts are:
- Impacted area: "The status and message apply to sponsored ads."
- Impacted activity: "The status and message apply to campaign creation."
- Date: "The date and time the status and message were published."
- Impact: "The status is applicable to both Amazon Ads console and Amazon Ads API." In the example, this line reads "Impacts console and API".
- Message: "This is the current published message and additional information about the status."
The fourth field is the one that matters most to agencies running campaigns through software rather than the browser. The status page's data schema allows three values for it: console only, api only and both console and api. An outage that hits only the API would leave a team clicking through the console untouched, and the reverse is also possible.
Seventeen rows on the live page
At 08:24 GMT+1 (07:24 UTC) on November 21, 2026, the status page showed green ticks for all three regions and for every component in the North and Latin America view. It also showed two tabs, Current Status and History, an English (US) language selector, and three links at the foot of the page: Status JSON, Schema and RSS. Every component carried the same 08:24 timestamp except Streams, which read 08:25.
The live page is organised into six groups, not four. The comparison below sets the help page against the page it describes and against the published data schema behind it.
| Group on the live page | Components on the live page (November 21) | Help page (November 20) | Data schema |
|---|---|---|---|
| Sponsored ads | Campaign creation, Campaign management, Ad delivery, Bulksheets | Campaign Creation, Campaign Management, Ad Delivery | Category Sponsored ads; Bulksheets is a listed subcategory |
| Amazon DSP | Campaign creation, Campaign management, Creative management, Ad delivery, Bulksheets | Listed as DVA+: Campaign Creation, Campaign Management, Ad (formerly known as Creative) Management, Ad Delivery | Category Amazon DSP; subcategory Creative management; no DVA+ value |
| Measurement & Reporting | Reports, Amazon Marketing Cloud | Listed as "Measurements and Reports": Reports | Category Measurement & Reporting; Reports only, no Amazon Marketing Cloud value |
| Brand content | Stores, Posts | Stores | Stores and Posts |
| Amazon Marketing Stream | Streams | Not listed | Category Amazon Marketing Stream; subcategory Streams |
| Account Management & Access | Billing Issues, User Access & Permissions, Account Registration | Not listed | No category or subcategory values |
| Components | 17 (PPC Land count) | 9 | 6 categories, 9 subcategory values |
Eight live components do not appear in the help text: bulksheets for both sponsored ads and Amazon DSP, Amazon Marketing Cloud, Posts, Streams, and the three account rows. Some are long-standing products. Spreadsheet-based bulk editing arrived in the DSP in January 2024, when Amazon DSP introduced Bulksheets for contextual campaign creation, and the Sponsored Products version picked up an off-Amazon serving column on June 8, 2026. Amazon Marketing Cloud is Amazon's clean room for querying advertising and shopping signals. Amazon Marketing Stream pushes hourly advertising metrics into advertisers' own AWS accounts, so a stalled stream can leave bidding software working from stale numbers without any visible error in the console.
Posts, nearly 16 months on
The Posts row is harder to explain. Posts was Amazon's free, social-style feed for brands. In June 2025, PPC Land reported that Amazon was discontinuing it, citing Amazon's advertising API release notes: deprecation announced on June 3, 2025, existing users barred from creating new posts from June 16, and complete termination on July 31, 2025. The status page still lists Posts under Brand content, 478 days after that termination date (PPC Land calculation), and its schema still accepts Posts as a subcategory. Neither the page nor the help article says what the row now monitors.
Two names for the same row
The help page's DVA+ group lists campaign creation, campaign management, ad management and ad delivery. Those are the Amazon DSP rows on the live page, under different names, minus bulksheets.
The new labels follow Amazon's own rebranding. Amazon retired the Amazon DSP name on September 29, 2026, the same day it put a four-step DVA+ campaign builder into US closed beta. DVA+ buys display, video and audio from one objective, one budget and one campaign. The switch from "creative" to "ad" shows up in reporting too: the Support Center page on unified reporting dimensions, covered by PPC Land on November 12, maps Ad ID and Ad name back to their former DVA+ names, Creative ID and Creative name.
The status page has not followed. Fifty-two days after the rename (PPC Land calculation, September 29 to November 20), the live page and the schema both say Amazon DSP and Creative management. That is not the only place where Amazon's two vocabularies overlap. An Amazon launch note for six new DVA+ locales, dated November 10, pointed advertisers to an Amazon DVA+ console while the console view it illustrated still carried the Amazon DSP header. And a Support Center primer updated on November 19 gave Amazon DSP two successors, describing DVA+ campaigns as formerly known as Amazon DSP in its subtitle and Amazon Ads Agent as formerly known as Amazon DSP in a worked example.
For a person reading the page during an outage, the mismatch is a minor translation exercise. For software, it is a contract question. A monitoring script written against the documentation would look for DVA+ and find nothing; one written against the schema will keep receiving Amazon DSP.
Nineteen countries, 15 fewer than in 2023
The country list is shorter than any Amazon has published for the service before. Amazon's launch note for "Amazon Ads Status (beta)", dated May 10, 2023, listed 34 countries in five regional groups. A second note, dated November 13, 2024, listed 33, the same set without Switzerland.
| Source | Date | Countries listed | Germany | Turkey | Ireland | Where India sits |
|---|---|---|---|---|---|---|
| Amazon launch note, Amazon Ads Status (beta) | May 10, 2023 | 34 | Yes | Yes | Yes | Asia Pacific |
| Amazon launch note, event history and preferred language | November 13, 2024 | 33 | Yes | Yes | Yes | Asia Pacific |
| Support Center, "Amazon Ads status page" | November 20, 2026 | 19 | No | No | No | Europe, Middle East, and North Africa |
Every country on the November 20 list also appears in the 2023 list. The 15 that dropped out are Germany, Austria, Switzerland, Luxembourg, Ireland, Denmark, Finland, Norway, Turkey, Kuwait, Bahrain, Morocco, Israel, New Zealand and China (PPC Land count). The 2023 list matches, country for country, the 34 markets in which Amazon offered VAST 4 support on third-party supply from September 2, 2026, and its size equals the 34 countries covered by a single global DSP account from July 30, 2026.
Germany is the most conspicuous gap. The help page's own rule - status applies to all countries in a region "unless mentioned otherwise" - suggests that a missing country is not necessarily an excluded one, but the page does not say whether the shorter list is deliberate. Ireland and South Africa, two of the six countries Amazon named for DVA+ on November 10, are both absent. India has also changed region, from Asia Pacific in both earlier notes to Europe, Middle East, and North Africa.
The feed behind the page
The status page is a JavaScript application, and the data that drives it is published in machine-readable form. At 07:20:33 UTC on November 21, the file status.json contained three fields: a timestamp, a language value of english, and an empty status array. According to its schema, an empty array means exactly what the green ticks mean: where no status is present for a region, category or subcategory, the status can be taken as "No known issues".
The schema, written to the JSON Schema 2020-12 standard and titled Amazon Ads Status json, sets out what an incident record looks like. Five fields are required for each entry: timestamp, statusType, region, systemImpacted and category. Three status types are allowed: Informational, Degraded and Disrupted. Six categories are defined: Sponsored ads, Amazon DSP, Measurement & Reporting, Status announcement, Brand content and Amazon Marketing Stream. The nine subcategory values are Ad delivery, Bulksheets, Campaign creation, Campaign management, Creative management, Reports, Stores, Posts and Streams. A "Status announcement" entry carries no subcategory, and its message applies to any entry that arrives without one of its own.
Three details in the schema do not line up with the rest. It has no value for the Account Management & Access group or for Amazon Marketing Cloud, so it does not describe how an incident in billing, user permissions, registration or the clean room would appear in the feed. It caps the status array at 27 entries while its own explanation gives a maximum of eight statuses in each of three regions, which is 24 (PPC Land calculation). And it describes the language field as an ISO 639-1 code, giving en as the example for English, while the live file says english. The schema also states that English is the only supported language for the feed, although the page itself has offered a language switcher since November 2024.
The RSS feed is thinner still. Titled "Amazon Ads Status" and generated with a Node.js library, it contained no items on November 21, and its last build time was 17:29:10 GMT on Wednesday, November 4, 2026.
History is published separately. According to Amazon's November 13, 2024 note, the History tab shows status updates from the past six months, the same record is available as history.json with its own schema, and a language choice made on the page is saved for later visits. Until then, according to the note, all status messages had been available only in English. The 2023 launch note pitched the service at advertisers and API integrators who needed status information without logging in to the advertising console or the DSP.
What outside monitors have logged
StatusGator, a commercial service that polls official status pages and says it has tracked Amazon's since January 2024, lists five officially acknowledged incidents on its Amazon Ads page, which it last refreshed on October 30, 2026. Two were in Europe, Middle East, and North Africa on July 16, 2026: a period StatusGator labels as down, lasting 1 hour 45 minutes, followed by a 6 hour 35 minute warning period. Three were in North and Latin America: a warning period of 1 day 19 hours 15 minutes from August 13, a down period of 7 hours 40 minutes from September 1, and a warning period of 1 day 21 hours from September 2. All five were marked as affecting console and API. The down and warning labels and the durations are StatusGator's, not Amazon's. StatusGator's Amazon Marketing Cloud page, refreshed on November 21, gives the last officially acknowledged outage as November 4, 2026 - the same day as the RSS feed's last build.
Why the gaps matter
Status pages earn their keep on bad days, and the advertising business has had several. The AWS failure in US-EAST-1 on October 19 and 20, 2025 lasted more than 15 hours and degraded ad tech running on Amazon's cloud. When Google Ads broke in 2024, its Ads status dashboard put the start at 23:54 UTC on July 30, though Google announced the incident only on August 1. In January 2026, publishers reported revenue drops of 50% to 90% as Google Ad Manager and Ad Exchange failures stacked up over three days. And during the Microsoft 365 outage of November 12 and 13, 2026, Microsoft's advisory appeared roughly 50 minutes after traffic began falling, with the service health page eventually listing 19 affected services.
Other platforms publish similar pages with their own limits. Google's Search Status Dashboard covers crawling, indexing, ranking and serving. When Google launched a Merchant Center status dashboard in February 2022, it said support engineers verify incidents before posting, which can delay a notice. Amazon's help page says nothing about how incidents are verified, how quickly they are posted or who posts them.
The timing gives the documentation more weight than usual. Amazon's own AI assistant does not fill the gap: on November 18, an agency chief executive published an exchange in which Amazon's ad agent said it could not see why three campaigns had stopped serving, because it could read reporting data but not campaign status, budgets or bids. Reporting itself is being rebuilt, with the legacy sponsored ads and DVA report pages due to shut on January 31, 2027. And Amazon's help centre has been changing quickly; the help page for the Account Transparency Log disappeared between November 13 and 14 without explanation. A status page that carries one set of names, a help page that carries another and a feed that carries a third is workable for a person. Is it workable for the automated tools Amazon is encouraging agencies to build?
What the help page does not say
The page has no change log, so what changed on November 20 is not stated. It does not explain why its country list is 15 shorter than Amazon's 2023 list, whether Germany is covered, or why India now sits in the Europe, Middle East, and North Africa region. It does not mention the History tab, the JSON and RSS feeds, bulksheets, Amazon Marketing Cloud, Amazon Marketing Stream, Posts or the three account rows, and it gives no commitment on posting times or follow-up incident reports.
Key facts
- Source document: Amazon Ads Support Center, "Amazon Ads status page", breadcrumb Support Center > Troubleshooting, "Updated on Nov 20, 2026"; listed among 12 troubleshooting topics including DVA+ delivery troubleshooting, traffic validation and IVT discrepancies.
- Service: Amazon Ads Status, https://status.ads.amazon.com/
- Live page state: "Last updated: November 21, 2026 at 08:24 AM GMT+1" (07:24 UTC); no known issues in North and Latin America; all three region tabs ticked.
- Machine-readable files: status.json (timestamp 2026-11-21T07:20:33.696Z, empty status array), status.schema.json (JSON Schema 2020-12, "Amazon Ads Status json"), status-feed.rss (no items, last built November 4, 2026, 17:29:10 GMT); history.json and history.schema.json per Amazon's November 13, 2024 note.
- Regions: North and Latin America; Europe, Middle East, and North Africa; Asia Pacific.
- Countries named on the help page: 19 (4, 12 and 3 by region).
- Features on the help page: 9 in 4 groups (Sponsored ads, DVA+, Measurements and Reports, Brand content).
- Components on the live page: 17 in 6 groups (Sponsored ads, Amazon DSP, Measurement & Reporting, Brand content, Amazon Marketing Stream, Account Management & Access).
- Status levels: No known issues, Informational, Degraded, Disrupted; the schema's statusType allows the last three.
- Impact values in the schema: console only, api only, both console and api.
- Example entry date on the help page: March 08, 2023 at 12:02.
- Launch: Amazon Ads Status (beta), launch note dated May 10, 2023 (34 countries); event history (six months) and preferred language, launch note dated November 13, 2024 (33 countries).
- Posts: termination date July 31, 2025, per Amazon's API release notes as reported by PPC Land.
- Amazon DSP name retired: September 29, 2026, per PPC Land.
Timeline
- March 8, 2023: Date on the example status entry later used in Amazon's help page.
- May 10, 2023: Amazon publishes a launch note for Amazon Ads Status (beta), listing 34 countries in five regional groups.
- January 2024: Amazon DSP introduces Bulksheets for contextual campaign creation.
- November 13, 2024: Amazon adds a History tab covering six months of status updates, a language switcher and a history.json feed.
- December 2024: PPC Land describes Amazon Marketing Stream's hourly metrics delivery into AWS.
- June 3 to July 31, 2025: Amazon announces the deprecation of Posts and terminates it on July 31.
- October 19-20, 2025: AWS US-EAST-1 outage lasts more than 15 hours.
- June 8, 2026: Sponsored Products bulksheets gain an off-Amazon serving column.
- July 16, 2026: StatusGator logs two officially acknowledged incidents in Europe, Middle East, and North Africa.
- July 30, 2026: Amazon announces a single global DSP account across 34 countries.
- August 13 and September 1-2, 2026: StatusGator logs three officially acknowledged incidents in North and Latin America.
- September 2, 2026: Amazon DSP adds VAST 4 support on third-party supply in 34 markets.
- September 29, 2026: Amazon retires the Amazon DSP name and puts a four-step DVA+ builder into US closed beta.
- November 4, 2026: Last build of the status page's RSS feed; StatusGator records the last officially acknowledged outage on the same day.
- November 10, 2026: Amazon names six new DVA+ locales, including Ireland and South Africa.
- November 12, 2026: PPC Land maps Amazon's 156 unified reporting dimensions, including Creative ID renamed Ad ID, and reports the January 31, 2027 shutdown of legacy report pages.
- November 12-13, 2026: Microsoft 365 outage hits 19 services.
- November 13-14, 2026: Amazon's Account Transparency Log help page is removed.
- November 18, 2026: Amazon's ad agent says it cannot see why three campaigns stopped serving.
- November 19, 2026: Amazon's DVA+ primer gives Amazon DSP two successor names.
- November 20, 2026: Amazon updates the Support Center article "Amazon Ads status page": nine features, 19 countries, DVA+ naming.
- November 21, 2026, 07:20-07:24 UTC: status.json carries an empty status array; the live page shows no known issues across 17 components, under the Amazon DSP heading, with Posts still listed.
Related PPC Land coverage
- Amazon calls its ad platform an agent, but the agent is still closed beta - How Amazon retired the Amazon DSP name on September 29, 2026 while its conversational agent stayed in closed beta.
- One goal per campaign: Amazon's DVA+ primer lists 15 KPIs - Amazon's November 19 primer, which gives Amazon DSP two different successor names.
- Amazon advertisers in Ireland and five other countries get DVA+ - The November 10 locale note that repeated a September Amazon DSP announcement under the DVA+ name.
- 85 of Amazon's 156 unified report dimensions apply to Sponsored Products - The reporting dimensions page that maps former DSP names, including Creative, to the new vocabulary.
- Amazon Posts officially discontinued - Amazon's June 2025 schedule for shutting down Posts, ending on July 31, 2025.
- Amazon DSP gains VAST 4 support on third-party supply in 34 markets - The 34-market list, including Germany and Turkey, that matches Amazon's 2023 status page country list.
- Amazon DSP advertisers gain a single global account across 34 countries - Amazon's July 30, 2026 move to one DSP account across 34 countries.
- Amazon's ad agent can't see why three campaigns stopped serving - An agency exchange showing the limits of Amazon's AI assistant when campaigns stop delivering.
- Amazon advertisers will lose unmigrated reports on January 31, 2027 - The shutdown schedule for Amazon's legacy sponsored ads and DVA report pages.
- Amazon outage breaks the internet: Snapchat, Fortnite, banks go dark - The October 2025 AWS US-EAST-1 failure and its effect on services built on Amazon's cloud.
- Google Ads suffers major outage, exposing competitor data to some advertisers - A 2024 Google Ads incident timed by Google's own status dashboard.
- Google launches a Merchant Center Status Dashboard - Google's 2022 status page for Merchant Center, feeds and the Content API.
- Microsoft's Outlook is back, and it brought 18 hours of mail with it - How Microsoft's status updates lagged outside measurements during the November 2026 outage.
Summary
Who: Amazon Ads, which runs the Amazon Ads status page and its Support Center documentation, and the advertisers, agencies and software makers who use the page and its data feed to check whether sponsored ads, DSP and reporting services are working.
What: A revised help article describes the status page as covering nine features in four groups across 19 countries, using the DVA+ name. The live page shows 17 components in six groups, still labels programmatic buying as Amazon DSP, still lists Posts, which Amazon shut in July 2025, and publishes a JSON schema that uses the older names and has no values for account management or Amazon Marketing Cloud.
When: The help article was updated on November 20, 2026. The live page and its JSON file were checked between 07:20 and 07:24 UTC on November 21, 2026. The status page itself has been public since Amazon's beta launch note of May 10, 2023.
Where: The Amazon Ads Support Center and the status site at status.ads.amazon.com, which reports by three regions: North and Latin America; Europe, Middle East, and North Africa; and Asia Pacific.
Why: A status page is the outside view of a platform's health when the console or API fails. When the documentation, the page and the machine-readable feed use different names, different country lists and different component sets, people and tools that rely on them can read the same incident differently, or miss it.
Discussion