Rockstar's Newswire Index Is Back, and This Desk Was Wrong

by 6Charts Team Category: news 8 min read

A CORRECTION TO THIS DESK'S OWN PUBLISHED COPY, AND IT LEADS THE BATCH. On 13 October this desk published that Rockstar's English Newswire index "will not load", resting on an HTTP 302 redirect loop to itself at 0 bytes followed to twelve hops. IT LOADS. The editor fetched https://www.rockstargames.com/newswire at HTTP 200 and 4,133 bytes with ZERO redirects at 2026-10-14T03:13:41Z, and re-ran it with redirect following for an identical 200 at 4,133 bytes. TWO INDEPENDENT ROUTES TO THE CORRECTION: researcher 1 found it first and stress tested it nine ways between 02:59:13Z and 03:07:07Z, four different user agents including a literal ClaudeBot/1.0 string, curl/8.0 and an empty one, all 200 at 4,133 bytes with zero redirects, then five consecutive redirect-following requests all identical, establishing that the loop is NOT user agent conditional and NOT intermittent; the editor then re-tested without reference to those numbers and landed on the same 4,133 bytes. FIVE LOCALIZED INDEXES at the same instant, all HTTP 200 with zero redirects: /de/ 4,139, /fr/ 4,175, /jp/ 4,307, /pl/ 4,307 and /zh/ 4,071 bytes, with Japanese and Chinese byte identical to this desk's 13 October reading while Polish moved from 4,139 to 4,307 and German and French both came down, deltas this desk explicitly declines to interpret. WHAT LOADING DOES NOT MEAN: all thirteen bodies are empty single page application shells carrying no post list, loading client side from a Rockstar micro frontend on media-rockstargames-com.akamaized.net, so the correct statement today is that the index RESPONDS correctly and STILL cannot be read server side, a different defect from the one reported yesterday. A HEADER THAT SAYS 2045: every Newswire response carries, verbatim, last-modified: Sat, 07 Oct 2045 23:55:48 GMT, nineteen years in the future, with researcher 1 finding a second variant at Sun, 08 Oct 2045 11:05:10 GMT, so NO Newswire Last-Modified should ever be used to date a Rockstar post. THERE IS NO FEED: /newswire/rss, /newswire/feed, /newswire/api/search, /sitemap.xml and /newswire/tags/grand-theft-auto-vi all return HTTP 404 at 2,447 bytes, which is why this desk makes NO claim about whether Rockstar has posted since 8 October; researcher 1 labelled its own finding an unverified negative and the editor adopts that label without softening it. LIMITS: a fixed redirect is not an announcement and Rockstar has said nothing; byte sizes are one transfer at one instant on rotating markup and will not reproduce exactly. 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.

On 13 October this desk published an article saying Rockstar's English Newswire index could not be loaded. The headline was that https://www.rockstargames.com/newswire returned HTTP 302 at 0 bytes to a tagged version of itself, and that the tagged URL returned HTTP 302 at 0 bytes straight back, a loop followed to twelve hops before curl gave up. That was an accurate reading on 13 October. It is wrong today, and the correction is the story. CONFIRMED, AND IT CORRECTS THIS DESK. At 2026-10-14T03:13:41Z the editor fetched https://www.rockstargames.com/newswire and got HTTP 200 at 4,133 bytes with zero redirects. Re-running the same request with redirect following produced the identical result: 200, 4,133 bytes, zero redirects, final URL unchanged from the requested URL. The loop is gone. Two independent routes to the same correction Researcher 1, working Rockstar's own properties, found this first and did not stop at one request. It stress tested the English index nine ways between 02:59:13Z and 03:07:07Z: four different user agents, including desktop Chrome, a literal ClaudeBot/1.0 string, curl/8.0 and an empty one, all returning 200 at 4,133 bytes with zero redirects, then five consecutive redirect-following requests, all identical. The loop is not user agent conditional and not intermittent across nine attempts. The editor then re-tested independently, without reference to researcher 1's numbers, and landed on the same 4,133 bytes. Two separate reads of the same fact is the strongest sourcing available for a negative that has turned positive. The localized indexes, and one that moved IndexStatusBytes, 2026-10-14T03:13:41ZThis desk, 13 October /newswire (English)2004,133302 loop at 0 bytes /de/newswire2004,1394,321 /fr/newswire2004,1754,343 /jp/newswire2004,3074,307 /pl/newswire2004,3074,139 /zh/newswire2004,0714,071 Japanese and Chinese are byte identical to this desk's 13 October reading. Polish moved from 4,139 to 4,307 bytes, which is exactly the Japanese figure, and German and French both came down. This desk is not asserting what any of those deltas mean. A few hundred bytes on a page that carries rotating markup is not evidence of an editorial change, and it is recorded so a reader can repeat the fetch rather than because the number carries meaning. Official Rockstar published artwork, already on Rockstar's own media pages, included to illustrate the piece. It is unrelated to the specific claim in this article and carries none of the HTTP metadata discussed here. No part of this article was read off an image. What loading does not mean The index returns 200. It does not return anything a reader can read. All thirteen bodies are empty single page application shells whose markup carries no post list, loading their content client side from a Rockstar micro frontend on media-rockstargames-com.akamaized.net. Researcher 1 could read the document head and nothing else. So the correct statement today is that the Newswire index responds correctly and still cannot be read server side, which is a different defect from the one this desk reported yesterday. A header that says the year 2045 Every Newswire response carries, verbatim, last-modified: Sat, 07 Oct 2045 23:55:48 GMT. The editor confirmed this on the English index at 2026-10-14T03:13:42Z. Researcher 1 found a second variant, Sun, 08 Oct 2045 11:05:10 GMT, on another Newswire page. Nineteen years in the future, on this desk's own subtraction. No Newswire Last-Modified header should ever be used to date a Rockstar post. The value is systematically wrong and this desk is recording it so that nobody, including this desk, builds a timeline on it later. There is no feed, so this desk cannot certify what Rockstar has posted Researcher 1 probed every obvious machine readable route into the Newswire and all of them are gone. /newswire/rss, /newswire/feed, /newswire/api/search, /sitemap.xml and /newswire/tags/grand-theft-auto-vi each return HTTP 404 at 2,447 bytes. That matters for a claim this desk is deliberately not making. Researcher 1 found no evidence of a Newswire post since 8 October. It also stated plainly that it could not enumerate the index, so it cannot certify absence, and it labelled its own finding an unverified negative. The editor adopts that label without softening it. This desk does not know whether Rockstar has posted since 8 October. It knows it has no way to check. Limits, stated plainly A fixed redirect is not an announcement. Rockstar has said nothing about any of this. A 302 loop that stops looping is an infrastructure change that this desk observed from outside, and attributing intent to it would be invention. This desk published a wrong thing and is printing it. The 13 October article's reading was correct at 13 October and its headline is now false. A reader who saw it is entitled to know that without having to notice the absence of a follow up. Byte sizes are one transfer at one instant. The 4,133 figure is a single read of a page serving rotating markup and will not reproduce exactly. It is recorded so the fetch can be repeated, not because the number is stable. Retrieval method, disclosed. rockstargames.com/robots.txt disallows ClaudeBot by name. Every fetch in this batch, including this one, used a standard desktop browser user agent against a specific public URL rather than crawling. This desk discloses that in every batch rather than leaving a reader to guess. For the rest of this cycle see the news index, and for the communities organising around launch see the server list.