Github Insights still not working

[RayBytes]

Select Topic Area

Question

Body

Over multiple days now, whenever visiting insights for my github repository, I keep seeing this:
Referring sites and popular content are temporarily unavailable or may not display accurately. We're actively working to resolve the issue.

I understand that according to the message they are working on it, but its been almost 5 days of me seeing this message. Is this a problem with my account or a general site wide problem?

[VictorMoni]

Hi @RayBytes,

This isn’t an issue with your account. GitHub Insights has been experiencing a site-wide problem where traffic and referring site data are temporarily unavailable. If you’re still seeing that message after several days, it means the outage is ongoing.

You can keep track of the current status here: https://www.githubstatus.com.

So no need to worry, it should start working again once GitHub resolves it.

[RayBytes]

Hi @RayBytes,

This isn’t an issue with your account. GitHub Insights has been experiencing a site-wide problem where traffic and referring site data are temporarily unavailable. If you’re still seeing that message after several days, it means the outage is ongoing.

You can keep track of the current status here: https://www.githubstatus.com.

So no need to worry, it should start working again once GitHub resolves it.

Hey, thanks for the reply. Do you know if analytics are still being tracked or not?

[RayBytes]

Also I don't appear to see anything regarding analytics on GitHub's status page?

[VictorMoni]

Hi @RayBytes,

Yes — the data is usually still being tracked in the background. What’s broken is the display/reporting, so once GitHub fixes it the stats should appear again.

[LostBeard]

You can keep track of the current status here: https://www.githubstatus.com.

That link says everything is working normally All Systems Operational, but Traffic stats are still showing the same error message that has been showing for days.

[mietzen]

Hi @VictorMoni, could you give us a update? Will this really only be fixed after the azure migration?

[GabrieleMessina]

Hi, I’m experiencing the same issue, and it seems to have been happening for over a week now. Since only data from the past two weeks is displayed, this is causing a significant problem.

[RobertGawron]

I also have the same issue, it's been one or two weeks.

[queenofcorgis]

@mccharliesins:

We’ve clarified our stance on using generative AI tools like ChatGPT within our Community via this announcement. Please review the guidelines to ensure your post meets them as failure to adhere to those rules can result in action taken by our moderator team.  You can read our updated Code of Conduct and the announcement for more details. Thank you for helping us maintain an authentic and beneficial space for everyone.

[LostBeard]

Hope this helps everyone understand the situation better! Let me know if you need clarification on any of these points or want help with specific workarounds. 🚀

That AI generated answer does not help at all and, if anything, it is a big waste of time. Unsubbing here. It will work, if they ever decide to fix it (been about a month now.) Not interested in spam like ^^^ that.

[1bl4z3r]

Can anyone shed a light if Insights is working or not?
I am seeing same page for last 20 days or so

[queenofcorgis]

@owneraniex: We’ve clarified our stance on using generative AI tools like ChatGPT within our Community via this announcement. Please review the guidelines to ensure your post meets them as failure to adhere to those rules can result in action taken by our moderator team.  You can read our updated Code of Conduct and the announcement for more details. Thank you for helping us maintain an authentic and beneficial space for everyone.

[duckeydev]

Welp, still the same thing, cant even see stats for my trending github repo

[mfactory-osaka]

same here, started when they updated the UI with the graphs

[Peixotim]

Hi! @RayBytes 👋

That message is not specific to your account — it’s a known issue on GitHub’s side. The Insights > Traffic section (referring sites and popular content) can sometimes go offline for maintenance or while they fix a data pipeline problem.

It doesn’t affect your repository itself, just the reporting.
Unfortunately, there’s nothing you can do from your end to “fix” it.

👉 The best thing is to keep an eye on the GitHub Status page
where they post updates about incidents. Once the issue is resolved, the traffic data should start displaying again automatically.

[kimmknight]

👉 The best thing is to keep an eye on the GitHub Status page

The GitHub Status page this whole time:

[ArseniiPetrovich]

Same here, please fix it!!!

[LostBeard]

Referring sites and popular content are temporarily unavailable or may not display accurately. We're actively working to resolve the issue.

I think someone doesn't know what temporarily means. 🤦‍♂️

[friflo]

In my case temporarily means two or three months. I guess we may accept it will be two or three years.

[sleeyax]

Nothing is as permanent as a temporary fix...

[shriyansX]

Hi @RayBytes, This issue isn’t specific to your account — it’s a site-wide problem currently affecting GitHub Insights. The message “Referring sites and popular content are temporarily unavailable…” appears for many users and is linked to an ongoing backend update to the traffic analytics system.

There’s no action required on your end. GitHub’s engineering team is aware and working on restoring full functionality. You can monitor the status at https://www.githubstatus.com/
— look under “API and Webhooks” → “Repository Insights / Traffic.”

Once resolved, your Insights data will update automatically.

[arkivanov]

The status page is all green, but I'm still not able to view insights for any of my repositories and the "temporarily unavailable" notice message is still there.

[peff74]

Same problem here, since 2025-08-27...
Please fix it!!!

[sleeyax]

Hey, I’m just another person following this thread, but all the “+1” comments are flooding inboxes without adding anything useful. If you want this to get more attention, hitting the "upvote" button on the original post actually helps. The more upvotes, the more visible it is. All of the "+1" comments don’t do anything except annoy everyone getting notifications. Thanks!

[ArseniiPetrovich]

It helps my mental state to see I'm not alone in this mess :D

[freakynit]

It seems this is the only alternative we have left to amass more community members to get this fixed. The original post already has sufficient number of upvotes and any more on that is useless. But what's not useless is getting more people to realize how wrong this all is.

In general other cases, I agree with you. But not on this one.

[jasperf]

This has been an issues for more than 6 months at least I think, not just two months so it is high time something does get done about it. To check for "Referring sites and popular content " is something that is very useful and so should be restored sooner rather than later. I did upvote the original post all the way at the top, but I think it is also still useful to write and leave a comment here to show this is still bothering (paid) users.

[davidmezzetti]

This has been ongoing for me for weeks now. Perhaps this is what we get with "vibe coding"?

While the functionality is not critical, it's nice to know how users are finding your repository and we're totally blind at the moment to that.

[chadhyatt]

Could always be deliberate.. 🙃

[freakynit]

Seems that way... pay us to get advanced insights

[LostBeard]

Nothing will be fixed while they are moving GitHub to Azure. They said so themselves. The link is in this thread ^. 🤷‍♂️

[CEXT-Dan]

I read this
I guess bugs are features too

[kimmknight]

Nothing will be fixed while they are moving GitHub to Azure. They said so themselves. The link is in this thread ^. 🤷‍♂️

Oh good. Nobody panic, they'll have it fixed in 18-24 months...

[john-k-walton]

this hasn't worked for MONTHS for me.

[rcrogers]

I have a record of past traffic data stored by https://app.repohistory.com/. Referrer/content data was last available on September 9 -- so yes, two months and counting.

[davidmezzetti]

It is surprising that it seems like it might never be fixed or that there is no sense of urgency to fix this. It's extremely valuable to know how people are finding your project.

[flaneurette]

Still not fixed. It has been at least a month, maybe more if I recall correctly (about 1.5 months). Github Status says that all systems are working fine, yet the message still appears.

[vaindil]

Hi everyone, GitHub employee here, I apologize that there's been no update. We have been actively working on fixing this, but spinning up the replacement service for these stats has taken longer than I hoped. The page should be working again within the next couple of weeks.

[patrick-knight]

I want to apologize for the lack of communication and updates regarding this issue. You're right to expect more frequent updates from us, especially when an issue persists for this long. One take away is ensuring we have a better process around status updates for situations like this in the future so it is clear we are aware, engaged and are communicating timeline more concretely.

On the technical side we ran into some unexpected issues here that delayed our ability to restore the referring sites and popular content as quickly as we had anticipated. The service we were migrating off of had reached capacity limits before our migration and spent time on mitigates there that were ultimately not fruitful. As @vaindil mentioned we are nearing completion of the new service that will allow us to scale that we were previously unable to do and should be back up soon.

[freakynit]

Thanks for the updates @vaindil and @patrick-knight This was the least all of us expected out of Github.. status updates, at least every few weeks.

We hope the service is restored soon. Knowing your referring sites is incredibly useful for all of us.

[PKHarsimran]

Anyday +1

[mmiscool]

Really. 6 months?

[davidmezzetti]

I appreciate the updates.

I am surprised how the importance of the functionality was underestimated. In general breaking things without a migration path is only done for something that is deemed unimportant.

[patrick-knight]

Quick update: Current plan is service restoration is expected to start in early December and insight restoration across repos will roll out progressively over time.