Repository Traffic stopped updating after Sep 23, 2026

[AhmedYehia-M23]

🏷️ Discussion Type

Bug

Body

Repository Traffic appears to be stuck.

For multiple repos, both:

• Insights → Traffic
• REST API traffic/views and traffic/clones

stop at Sep 23, 2026.

No data appears for Sep 24 onward.

Is anyone else seeing the same issue?

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[kurupdevs]

Same pattern here — multiple repos, same Sept 23 cutoff, both the UI and the API affected. That combination points at GitHub's traffic analytics pipeline, not anything on your side. Traffic data comes from a separate pipeline behind the repo, so there's no repo setting, re-push, or API call that would unstick it.

What I'd do:

1. Open a support ticket with the repo names and the endpoints you checked (traffic/views, traffic/clones). The more reports that land with the same Sept 23 cutoff, the faster it gets routed to the right team.
2. Keep an eye on githubstatus.com, though traffic-pipeline stalls don't always show up there.
3. Don't assume the data is lost — when these pipeline stalls get fixed, the missing window is usually backfilled.

There's nothing actionable on your end for this one; it's GitHub-side.

[AhmedYehia-M23]

Thanks — that matches exactly what I'm seeing.

I also tried opening a GitHub Support ticket, but it was auto-closed and redirected me back to Community Discussions.

Still no traffic data after Sep 23 on any of the affected repos.

[karmenti]

Same here
Both the UI and traffic/views/traffic/clones still return 2026-09-10 to 2026-09-23. The repo had real activity after that (0 → 9 stars, 1 → 17 release downloads since 24.09), so the missing days aren't empty.
My support ticket was auto-closed too.

[facebey]

I’ve had the same problem since September 23rd; the metrics for my public repo are frozen.

[reddy895]

I’m seeing the same kind of behavior as well. If multiple repositories are all stopping at the same date, while the repositories themselves continue receiving activity, that points more toward a GitHub Traffic reporting/processing issue than an individual repository configuration problem.

It would be useful to know whether the missing data eventually backfills or whether the REST API and Insights dashboard remain stuck at September 23. If others can reproduce it across multiple repositories, that should help confirm it’s a platform-wide issue.