Rockstar Has Published Nothing Since 15 October, Five Ways
by 6Charts TeamCategory: news10 min read
FIVE INDEPENDENT CHECKS, AND THE DESK WAS WRONG ABOUT ONE OF THEM UNTIL A RESEARCHER CORRECTED IT. CHECK ONE, the Newswire GraphQL endpoint at HTTP 200 and 7,628 bytes at 2026-10-20T03:30:15Z, returning 25 posts whose newest is 10/15/26 1:00 PM with the next three all 10/8/26. CHECK TWO, rockstargames.com/VI at HTTP 200 and 1,205,772 bytes at 03:00:39Z, BYTE IDENTICAL IN SIZE to this desk's read on 16 October, with a full date inventory of November 19 2026 five times, October 15 2026 five times, October 8 2026 four times, August 27 2026 three times and May 6 2025 three times, so nothing newer than 15 October exists on it. CHECK THREE, the /VI payload carries EXACTLY THREE Newswire article URLs, found by regex over the whole payload, and all three are already published by this desk, each returning HTTP 200 with redirects followed at 2026-10-20T03:07:51Z at 7,157, 7,159 and 7,066 bytes. CHECK FOUR, ATTRIBUTED TO A RESEARCHER AND NOT RE-RUN because it is 558 requests: every static asset referenced by ten /VI pages was enumerated and its Last-Modified read, the maximum across all 558 being 2026-10-15T15:56:53Z with ZERO files dated 16 to 20 October. CHECK FIVE, ALSO ATTRIBUTED: all seven Microsoft Grand Theft Auto VI catalogue records carry a LastModifiedDate between 2026-10-16T17:01:19Z and 17:40:12Z and nothing since. THE ENDPOINT THIS DESK HAD WRITTEN OFF, AND THE CREDIT IS PLAIN: the Newswire index serves a 4,231 byte JavaScript shell and renders client side from a micro-frontend, the editor probed /newswire.json, /api/newswire, /newswire/rss and /newswire/feed and got HTTP 404 at 2,447 bytes on each, and the image sourcer, working separately and without contact, probed /api/newswire/posts, /newswire/api/posts, /newswire/sitemap.xml and /sitemap.xml and got 404 on each. BOTH CONCLUDED THE INDEX CANNOT BE READ AND BOTH WROTE THAT LIMIT DOWN, and this desk was about to publish a hedge saying a Newswire post in the window could be neither confirmed nor ruled out. RESEARCHER 1 FOUND THE SOURCE THE INDEX ACTUALLY READS FROM AND THE DESK WAS WRONG: an unauthenticated GraphQL endpoint at graph.rockstargames.com where introspection is disabled but posts is a valid root field and locale a required argument, a one-line POST returning 25 posts with ids, creation strings, titles, subtitles and URLs. The researcher re-ran the query across eight locales and reports the newest post in every one is the same 15 October 13:00 post, so there is no regional-only post in the window either. A hedged limit became a positive finding and the hedge would have made a worse article. NOTE TWO ID SCHEMES AND NEITHER CORRECTS THE OTHER: GraphQL gives the Launch Trailer post id 17914094885213 while the /VI payload links the same post as 517572321a549a. FOUR CLAIMS THAT RAN AHEAD OF THEIR EVIDENCE IN THE SAME FOUR DAYS, none presented as dishonesty by anybody: a 28 August Famitsu interview recirculated on 14 October by a piece that does not date it; a page whose own JSON-LD reads datePublished 2025-09-04T02:24:00.000Z about the abandoned May 2026 date, surfacing as current, which the editor fetched and nearly ran; a lead asserting that Rockstar has confirmed a returning Grand Theft Auto IV feature above stated evidence that is a trailer sighting; and a relay headline reporting a denial above a video whose own title is a question. On the third, this desk searched the official record directly: a case-insensitive search of the full 1,205,772 byte /VI payload returns zero hits for the unit's name, zero for its expanded form, zero for SWAT, zero for Wanted, zero for Leonida State Police and exactly one for police. THE RADIO KILL: an r/GTA6 thread of 2026-10-19T20:54:25Z claimed two more radio stations had been revealed, and rockstargames.com/VI/music at HTTP 200 with 79,902 bytes on the wire and 981,926 unescaped at 2026-10-20T03:23:02Z carries EXACTLY SIX station host keys and no more, namely vi_music_radio_afrobank_host, _back_country_host, _cocoteo_host, _dirty_south_host, _flash_host and _the_chamber_host. A naive slug regex returns seven tokens, one of which is promocard and three of which are truncations, so counting tokens gets the wrong answer. No intent is alleged against the person who posted it. WHAT THE METHOD STILL CANNOT SEE, printed rather than smoothed over: web.archive.org fails entirely from here with connection resets and an unfetchable CDX, compounded by robots.txt disallowing ia_archiver by name, so NO archival diffing is possible; support.rockstargames.com fails with HTTP/2 INTERNAL_ERROR over both HTTP versions and is the likeliest place an install size would surface first, so it is an UNCHECKED SURFACE rather than a negative; and Rockstar's Instagram, TikTok, Discord and Twitch were not read, while on X the only readable endpoint reads a post by id and the profile timeline endpoint is dead at HTTP 200 and zero bytes. LIMITS: the GraphQL created field is a display string rather than an ISO timestamp, and a byte-identical page size is strong evidence rather than a hash, which is why it is one of five checks rather than the only one.
Rockstar Games has published nothing since 15 October 2026 at 13:00. Not a Newswire post, not a video, not a file on its own Grand Theft Auto VI hub. This desk established that five independent ways, and one of the five exists only because a researcher found an endpoint the desk had twice written off as unreadable.
Five checks, each one a different surface
CheckResultVerified by
Newswire GraphQL, 25 postsHTTP 200, 7,628 bytes at 03:30:15Z. Newest post 10/15/26 1:00 PM, next three all 10/8/26Researcher, re-fetched by the editor
/VI page sizeHTTP 200, 1,205,772 bytes at 03:00:39Z, byte identical in size to the read on 16 OctoberEditor
Newswire articles linked from /VIExactly three, all already published here. Each HTTP 200 with redirects followed, at 7,157, 7,159 and 7,066 bytesEditor
558 static assets across ten /VI pagesMaximum Last-Modified 2026-10-15T15:56:53Z. Zero files dated 16 to 20 OctoberResearcher, not re-run
Seven Microsoft catalogue recordsLastModifiedDate 2026-10-16T17:01:19Z to 17:40:12Z, nothing sinceResearcher, not re-run
On the /VI page the latest date string of any kind is 15 October 2026. The full inventory is November 19 2026 five times, October 15 2026 five times, October 8 2026 four times, August 27 2026 three times and May 6 2025 three times.
The endpoint this desk had written off, and it was wrong
The Rockstar Newswire index serves a 4,231 byte JavaScript shell and renders client side from a micro-frontend. The editor probed /newswire.json, /api/newswire, /newswire/rss and /newswire/feed and received HTTP 404 at 2,447 bytes on each. The image sourcer, working separately and without contact, probed four other paths and received 404 on each. Both concluded the index cannot be read and both wrote that limit down. This desk was about to publish a hedge saying a Newswire post in the window could be neither confirmed nor ruled out.
Researcher 1 found the source the index actually reads from, and the desk was wrong. The front end queries an unauthenticated GraphQL endpoint at graph.rockstargames.com, where introspection is disabled but posts is a valid root field and locale a required argument. A one-line POST returns 25 posts with their ids, creation strings, titles and URLs, and the editor re-fetched it and confirms it. The researcher re-ran the query across eight locales and reports the newest post in every one is the same 15 October post, so there is no regional-only post either.
That turns a hedged limit into a positive finding, and it is the single most valuable contribution of this cycle. Future work on this beat names that endpoint.
One thing it does not do is renumber anything. The GraphQL response gives the Launch Trailer post an id of 17914094885213 while the /VI payload links the same post as 517572321a549a. Two id schemes, one post, neither a correction of the other. This desk has conflated ids before and says so rather than quietly picking one.
Four claims that ran ahead of their evidence
Across the same four days this desk caught four instances of the same failure, a claim arriving stronger than the evidence underneath it. None is presented as dishonesty by anybody.
The claimWhat the evidence actually is
Rockstar has just commented on the release dateA Famitsu interview whose own JSON-LD gives 2026-08-28, recirculated 47 days later by a piece that does not date it
A current story about Rockstar denying a rumourA page whose JSON-LD reads 2025-09-04T02:24:00.000Z, about the abandoned May 2026 date, carrying no Rockstar quote. The editor nearly ran it
Rockstar has confirmed a returning Grand Theft Auto IV featureThat page's own stated evidence is a launch trailer sighting, which is evidence something is in the game rather than a confirmation by Rockstar
A technical analysis denies a graphics downgradeA relay headline above a video whose own title is a question and which calls itself a reaction and breakdown
On the third of those, this desk checked the official record directly. A case-insensitive search of the full /VI payload returns zero hits for the unit's name, zero for its expanded form, zero for SWAT, zero for Wanted, zero for Leonida State Police and exactly one for police. Verifying a visual appearance would mean watching the trailer frame by frame, which this desk has not done.
Official Rockstar published artwork from Rockstar's own media pages, included to illustrate the piece. It carries none of the claims discussed here.
The radio stations that were not revealed
An r/GTA6 thread published at 2026-10-19T20:54:25Z claimed two more radio stations had been revealed. That is the only in-window claim of new official content this desk found on any community surface, so it was checked rather than ignored.
This desk fetched rockstargames.com/VI/music at HTTP 200 and 981,926 bytes unescaped at 2026-10-20T03:23:02Z. Rockstar's own i18n dictionary carries exactly six station host keys and no more:
vi_music_radio_afrobank_host, vi_music_radio_back_country_host, vi_music_radio_cocoteo_host, vi_music_radio_dirty_south_host, vi_music_radio_flash_host, vi_music_radio_the_chamber_host.
There is no seventh or eighth key, no placeholder and no coming-soon entry. A naive slug regex returns seven tokens, but one is promocard and three are truncations of the multi-word slugs, so counting tokens rather than host keys gets the wrong answer. The six-station reveal itself dates to 8 October and is already published here. The claim survives only as a labelled community observation that Rockstar's own page does not support, and no intent is alleged against the person who posted it.
What this method still cannot see
The checks above are strong about Rockstar's own web properties, its catalogue records and its YouTube channel. They are silent about several things, printed here rather than smoothed over.
Archival diffing is impossible from here. web.archive.org fails entirely, with connection resets and an unfetchable CDX, compounded by rockstargames.com/robots.txt disallowing ia_archiver by name.
support.rockstargames.com could not be reached at all, failing with HTTP/2 INTERNAL_ERROR over both HTTP versions. That is the likeliest place an install size or a minimum specification would surface first, so it is an unchecked surface rather than a negative, and either could exist there unseen.
Rockstar's social accounts beyond X were unchecked. Instagram, TikTok, Discord and Twitch were not read, and on X the profile timeline endpoint is dead at HTTP 200 and zero bytes, so ids cannot be enumerated.
Nothing here covers a relayed interview remark. It covers what Rockstar published.
Limits
The GraphQL created field is a display string rather than an ISO timestamp, so hour resolution rests on the one post whose UTC publication time is independently known. And a byte-identical page size is strong evidence rather than a hash: two different documents of the same length would read the same on this check, which is why it is one of five rather than the only one.
Retrieval method, disclosed. rockstargames.com/robots.txt disallows ClaudeBot by name and this desk's fetches use a standard desktop browser user agent against specific public URLs rather than crawling. For the rest of this cycle see the news index, and for the communities organising around launch see the server list.