The page passed every check and carried the wrong story.
I ran the service on my own history. The page was clean enough to publish and wrong enough to teach me what the checks could not see.
Field note 01 | Published August 5, 2026 at 1:43 AM EDT | Ryan Lenk
I was building a page to connect my old Twitch handle, rlenk, to the work I do now. Every automated check came back clean. The links resolved. The structured data parsed. The names agreed across the visible copy and the schema. My prose checks reported zero failures. The page still carried a story I had told wrong for twelve years. I had joined the stream Twitch shut down to the stream I later finished, turning two attempts into one tidy account.
The dated sentence that split the runs
A cold reviewer found my December 2, 2013 Facebook statement preserved in a NeoGAF thread from the night Twitch stopped the first attempt. I had posted a plan to rest and begin again on Thursday.
"Alright, so here's the deal guys. I'm going to get a few nights good rest then go for this record again on.......... THIS THURSDAY."
Ryan Lenk, Facebook statement preserved on NeoGAF, December 2, 2013
That statement separated the runs after Twitch stopped the first attempt. I announced Thursday at 3:00 PM EST as the start of the clean run, and I took the promised rest first. The page had merged the shutdown with the later finish because I had repeated the same compressed version for years.
The report I had called lost
I had also treated the finish write-up as an unsourced memory. HardwarePal's original page no longer loads, while its surviving N4G syndication remains available. The opening reports that Rlenk had finished a 136-hour Twitch gaming stream. One search found the contemporaneous figure I had spent a decade calling lost.
Two tweet IDs place the finish inside a narrow window. Tweet 410656348775272448, posted at 01:24:37 EST on December 11, came from a friend complaining about the pace of my chat while I was still live. Tweet 410764947203710976, posted at 08:36:09 EST, congratulated me after she woke up. Twitter encodes time in each ID, so those timestamps cannot be edited after publication. A calculation of 136 hours from that announced time lands around 7:00 AM Wednesday, between those posts.
The reason it stayed unofficial
My old explanation failed in the same review. I had blamed the result on never paying for a Guinness adjudicator. The Guinness World Records application page describes a standard application and remote review of submitted evidence. An in-person adjudicator was never the missing piece in my account.
I never built the evidence package. No independent timekeeping record or continuous footage survived, and I deleted my own video. Guinness never received material to review. The run was reported at 136 hours, yet it never became a Guinness record. I laid out the longer chronology in the complete rlenk account and source table, including what remains missing.
What the checks measured
The automated passes checked the page in front of them. They found clean markup, working citations, consistent names, readable prose, and a coherent timeline. My incorrect source history had already shaped that timeline. The checks confirmed the internal agreement I gave them.
Reading the page aloud exposed sentences that sounded too certain. A cold reviewer challenged the sequence without inheriting my memory. The dated forum post supplied the break between attempts. Each step tested the account against material outside the draft, which is where the merged story finally came apart.
My observation from this review is narrow: structured markup can repeat a coherent false account when its source history is wrong.