NeurIPS, one of the largest annual AI research conferences, rebuilt parts of its 2026 peer review. Researchers say the OpenReview platform NeurIPS uses to route rebuttals did not surface their paper to reviewers.
NeurIPS is one of the largest annual AI research conferences. A paper accepted there is read by hiring committees, grant reviewers, and journalists, and the lead authors are often PhD students or early-career researchers whose job-market decisions depend on the cycle. For the 2026 cycle organizers rebuilt parts of the peer review process. A new Area Chair pilot added pre-rebuttal initial meta-reviews, a "Responsible AC'ing" rule withholds an AC's own reviews until their meta-reviews are in, and a parallel AI-Assisted Reviewing Experiment is randomly assigning some reviewer-paper pairs to unassisted, open-ended LLM-assisted, or structured LLM-assisted conditions. An area chair (AC) is the senior reviewer who oversees a batch of papers and the reviewers assigned to them. The window for authors to respond to reviewers, the rebuttal, opened July 27 Anywhere on Earth. According to researchers posting on r/MachineLearning, the OpenReview path the venue uses to surface a rebuttal to a reviewer or an AC did not surface the submission to the humans assigned to read it.
In a thread titled "NeurIPS 2026: ACs and reviewers have disappeared" on r/MachineLearning, an account describes submitting through the venue's "Rebuttal" button before the discussion window officially opened. When the window opened, they say, no rebuttal-notification email arrived, all four reviewers and the area chair went silent, and meta-comments, reviewer reminders, and a message to the program chairs produced no visible response. They believed the paper's initial scores put it in oral-or-spotlight range; roughly one day was left in the window.
A second [r/MachineLearning thread, "NeurIPS reviewers not engaging [D]"](https://www.reddit.com/r/MachineLearning/comments/1va5io6/neurips_reviewers_not_engaging_d/), describes the same pattern in the same window, and NeurIPS's official X account posted during the rebuttal period to clarify the timing. That is evidence of a cross-channel disruption, not a single-author complaint.
The NeurIPS 2026 conference page confirms a separate, on-the-record operational event: "Due to a technical issue during release, we are currently re-releasing all reviews and initial meta-reviews. Reviews will be temporarily offline during that time." The post is dated July 23, 2026, four days before the discussion window opened and in the same week as the Reddit reports. The page does not name the OpenReview notification path, and does not say whether the re-release is the cause of any missed rebuttal notification.
The AC pilot, the AI reviewing experiment, and the July 23 re-release all sit on the same OpenReview path the author has to hit to be heard. The pilot withholds an AC's access to their own reviews until the AC's meta-reviews are in, a deliberate friction that depends on the system knowing which paper a human is on. The AI experiment asks ACs to score a review blind to whether it was written with LLM help, an extra round of work for the same humans. The re-release re-runs review delivery in the week before the rebuttal. If any of those steps lands a fraction of a second before or after a notification is sent, the difference between "your paper has been read" and "no human was notified" can come down to the timestamp on a click of the "Rebuttal" button.
The volume of affected papers is not known. The Reddit reports are first-person accounts from affected authors in at least two separate threads; the venue has confirmed the re-release but not the notification path. Oral and spotlight acceptances are scheduled to be communicated on September 24, 2026 AoE, and the NeurIPS 2026 schedule keeps the AC workflow inside its high-load window until then. Other conferences running on the same OpenReview tooling face the same question before their own rebuttal windows open: does the path from "author clicks Rebuttal" to "human reviewer sees it" still hold when the system is told to do three new things at once?