Why is the DC hammering my network?
2 Likes
Million dollar question. Open a ticket so they can track it. I have the same issue randomly too.
2 Likes
I don’t know… maybe it’s trying to upload the bitcoin it’s been mining.
(This is a joke. 
)
3 Likes
My ticket number is #125453. I encourage others to report theirs here so they can more easily correlate and track the issue. While it’s not causing me problems (that I am aware of) with my equipment, I know it was/is for others.
2 Likes
#131079 I’ll report back.
2 Likes
A reboot will fix it. I’ve been tracking this since May. There a couple threads with some good theories on what’s happening. Yarbo claims to have identified a bug. But there has been no fix to date.
1 Like
Not sure what your picture displays.
I checked the datacenter ethertnet port on my router and it looks like this. Spikes are when the yarbo is mowing an area.
Does not seem like excessive usage ir something
(the no-traffic area is when the main ISP router died)
1 Like
For sure but is it causing YARBO do things it shouldn’t, interfering with the unit with needless computations, contstant GPS signal swapping, etc.
I’m just making up terms by the way. Haha
2 Likes
To keep everyone updated — as we discussed in your support ticket, if the HaLow signal becomes slightly weak or distorted, the Data Center will automatically switch to the backend server tunnel to maintain stable communication. When this happens, it continuously pings your router to keep the tunnel active and ensure the positioning data is transmitted correctly without interruption. What you’re seeing is simply part of that process.
2 Likes
Does it generate a new MAC address for every ping?
2 Likes
More likely for each established .
Probably not closing the bad tunnel.
Just my theory.
1 Like
In my case, when the DC goes rouge, Yarbo flips to 4G until I restart the DC. I didn’t see any other Yarbo issues. It causes havoc on my internal network though.
3 Likes
Same here.
2 Likes
Absolutely nothing would surprise me at this point in life. 
1 Like
Challenge accepted. Hold my beer! 
2 Likes
Would love a response to your question. “simply part part of the process” isn’t holding water.
2 Likes
My guess is that they don’t know yet and I see it so sporadically that by the time I report it and they actually can look into it, it’s stopped happening again. Really hard to troubleshoot that way (and weird issues like this to begin with). I hope that the more of us that can report it can help them narrow down the commonalities and zero in on the root cause.
1 Like
Appreciate what you’re saying. but it’s pretty basic for me. Plug in the the DC and wait 2 to 4 weeks for it to fail. I opened I ticket, they closed with an offer to replace the DC. I declined. New hardware will not solve a software issue. They know it’s crashing.
3 Likes
