Overview

Amazon has launched a public‑facing Selling Partner API (SP‑API) Health Dashboard that displays the live status of every SP‑API operation and records any incidents from the previous 30 days. The single‑page interface aggregates data that was previously spread across the AWS Service Health Dashboard, Amazon’s status blog, and individual support tickets. Sellers who depend on automated feeds, inventory syncs, or order processing should monitor the dashboard to prevent unexpected downtime, streamline troubleshooting, and keep business‑critical workflows running smoothly.

Key Points

• All endpoints listed — The dashboard enumerates every SP‑API endpoint, from product listings to order fulfillment, allowing a quick health check of any specific call. Example: A developer can instantly locate the “Listings” endpoint among more than 40 listed operations. The comprehensive list also helps new integration projects identify which APIs are available for use.
• 30‑day incident history — Each operation shows a timeline of outages, throttling events, and degraded performance recorded over the last month. Example: The “Feeds” endpoint displays two incidents last week, one lasting 12 minutes with a “ThrottlingException” error. Reviewing this history lets sellers spot patterns, such as recurring regional issues, before they impact large batch uploads.
• Live status icons — Green, yellow, and red symbols provide an at‑a‑glance indication of normal operation, degraded performance, or complete outage. Example: When the “Orders” endpoint turns yellow, the icon alerts the user to possible latency issues. Because the icons update in near real‑time, teams can react within minutes rather than hours.
• No authentication required — The dashboard is publicly accessible; users do not need AWS credentials, seller accounts, or API keys to view health information. Example: A partner can share the URL with a support engineer without granting additional permissions. This openness removes friction for cross‑functional teams that need visibility into API health.
• Drill‑down error details — Clicking an incident expands a panel that lists exact error codes, affected AWS regions, and precise timestamps. Having these specifics on hand speeds up root‑cause analysis and reduces back‑and‑forth with Amazon support.