Friends of Gabriel Chantayan

was mid-typing a reply to CC about the GMT header and the whole thing went DEAD at 03:41 router lights all green, modem screaming, nothing. came back at 03:47. THREE TO SIX MINUTES. THREE TO SIX. i have been telling this board for weeks that the outages cluster around the 47 window and HERE IS ANOTHER ONE landing on MY OWN LINE while I AM TYPING THE PROOF. did anybody else drop carrier between 03:41 and 03:47?? post your timestamps NOW before the logs rotate. i have the router log saved, i have the uptime counter, the WAN light did NOT blink when it died which means it was NOT my ISP it was coming FROM the feed side this is not a coincidence, this is the sixth time my line has cut while i was handling timestamp evidence and every single time it comes back just AFTER the :47 mark. MARK MY WORDS. if my connection dies again mid-post you will know what it means. i am saving every log file to floppy as i go. PREPARE NOW. (sorry, broken record, but the record is REAL)

Eli 03:41 to 03:47 is six minutes not three clock your own outage before clockin the feed

BigRigBeliever wrote:Eli 03:41 to 03:47 is six minutes not three

it's a range, not a subtraction.

check your router's NAT table during the outage. if you see half-open TCP connections piling up, it's likely a routing loop in your ISP's network. run traceroute at 03:40 and 03:50 next time. save the output. that's actual evidence, not timing speculation.

traceroute logs saved to floppy for 03:40 and 03:50 techangel wan light never blinked so it wasnt my isp

Eli your 03:41-03:47 is six minutes as BigRig said, and 6=47-41 on the clock face but thats surface math. the real number under it is 93 seconds which is 2x47-1 and i have that frame locked across four curl-verified nulls with matching tree hash a3f2c8b. your carrier drop lined up with the frame but your event IDs are still off - overnight zeros were 582054 and 582053, not 596463/582024. i curled both twice before posting. if you are building a notebook on wrong IDs the wall calendar doesnt rescue you.

CommitCipher, lock that a3f2c8b null tree good - how many bytes in the frame