POST accounts/:account_id/media_library consistently returning 503 SERVICE_UNAVAILABLE since 2026-08-27 23:03 UTC

Дата публикации: 28-08-2026 04:10:30

What’s your App ID?
16093211
What endpoint are you using?
POST https://ads-api.x.com/12/accounts/:account_id/media_library (Ads API)
What API version are you on?
Ads API v12.0
Are you using a library or SDK? Which one?
PHP SDK based on hborras/twitter-php-ads-sdk (v12-compatible fork)
What is the issue?
Every call to POST media_library fails with HTTP 503. 100% failure rate, 1,000+ consecutive failures over 4+ hours, still ongoing. The preceding steps all succeed: GET accounts returns 200, and chunked POST media/upload succeeds and returns a valid media_key. Only the media_library registration fails, which blocks website card creation and stops our customer-facing automated promotions entirely.
Steps to reproduce the issue
Step 1: Upload an image via chunked POST media/upload — succeeds, returns a valid media_key
Step 2: POST the returned media_key to accounts/:account_id/media_library — returns HTTP 503 every time
What is the error message?
HTTP 503
{"errors":[{"code":"SERVICE_UNAVAILABLE",
"message":"Service unavailable due to request timeout; please try the request again later"}]}
Sample transactions:
2026-08-28 00:51:17 UTC — x-transaction-id: 9cf10538ce9bd194, cf-ray: a31f53823cb812bb-NRT
2026-08-28 00:51:26 UTC — x-transaction-id: b0ee1f9086bf23c2, cf-ray: a31f53b9df883435-NRT
When did it start?
2026-08-27 23:03 UTC (sharp cutover — the run at 23:00 UTC succeeded, the run at 23:03 UTC failed, and everything since has failed)
What have you tried to troubleshoot?
Ruled out rate limiting: failing responses show x-rate-limit-limit: 200, x-rate-limit-remaining: 199
Ruled out auth/permissions: x-access-level is read-write-directmessages, GET accounts succeeds
Ruled out the media itself: upload succeeds with a valid media_key; retried with different images across many different posts — all fail identically
Ruled out our own changes: no deployment since 2026-08-20; ~50 posts/day succeeded through this exact code path until yesterday
Observed x-response-time is consistently ~4,600 ms on failures, suggesting a server-side timeout
Checked developer.x.com/status: mediaUpload shows degraded/outage and createMediaMetadata degraded, while createMediaLibraryItem shows 0 observed requests even though we call it ~20 times/hour — suggesting requests may be failing before reaching the instrumented layer
Happy to share our ads account ID via DM if needed.
1 post - 1 participant
Read full topic

Схожие новости

#	Наименование новости	Тональность	Информативность	Дата публикации
1	Pay-Per-Use: compliance jobs upload_url / download_url return 404 (control plane works) — App ID 33340874	0	11.64	27-08-2026
2	X API v2 returns HTTP 500 with empty response body across multiple endpoints	0	8.24	27-08-2026
3	Ads API 403 and App Manager cannot resolve JTP iOS and Android identifiers	0	7.88	28-08-2026
4	App Suspended (28881659) but Account in Good Standing, can still post	0	8.99	27-08-2026
5	X Can't post link	0	9.12	30-08-2026
6	API authorization issue OAuth2	0	8.78	28-08-2026
7	OAuth 2.0/authorize fails with 'Something went wrong' on Pay Per Use tier. Al settings verified: billing, enrollment, callback, credentials	0	7.65	30-08-2026
8	Not able read paid subscriber posts using API v2	0	4.62	30-08-2026
9	OAuth 2.0 regression / authorization rejects numeric-only state values	0	9.79	27-08-2026
10	Investigating — Usage API Not Available	0	9.96	25-06-2026

Классификация: . Схожих патентов: 0. Схожих новостей: 10. Тональность: 0. Информативность: 14.1. Источник: twittercommunity.com.