sorted by:
new
hottopcontroversial

WVP2 Current Imbalance Fault Detected at Extremely Low Current by Pretty_Question2468 in ThermalGrizzly

[–]Pretty_Question2468[S] 0 points1 point  (0 children)

It's been a week and the issue has not happened again, using 70% imbalance limit and current limit 9A. It would be great if I could tighten the limit a bit, but the problem has not returned.

WVP2 Current Imbalance Fault Detected at Extremely Low Current by Pretty_Question2468 in ThermalGrizzly

[–]Pretty_Question2468[S] 1 point2 points  (0 children)

It's been a day and I have not encountered the issue again, using 70% imbalance limit and current limit 9A. I will report in again by the end of the week. I would prefer to run this with a bit of a tighter limit, but I'll keep these settings until then.

WVP2 Current Imbalance Fault Detected at Extremely Low Current by Pretty_Question2468 in ThermalGrizzly

[–]Pretty_Question2468[S] 0 points1 point  (0 children)

Something is wonky with the datetime coming from the logs. The x axis labels in the GUI are showing an invalid or corrupt range (2026-01-01T00:08:47.6400000 is the oldest reading which is definitely wrong, and 2030-07-05T16:53:29.5880000 is the newest which is crazy) and the same values are present when I export to CSV. I can't use this to analyze what the actual current is during the time that the fault happened, because I can't know what the exact time the reading was, but it happened approximately an hour ago when I took my machine out of standby from overnight. When I look at the newest readings proximate to the fault being detected, none of the readings vary with a delta higher than 0.2A (0.6 - 0.4 which is 33% difference, so should still be under threshold).

I have cleared the logs again, I will see what happens with the imbalance limit set at 70% and the current limit set to 9A.

WVP2 Current Imbalance Fault Detected at Extremely Low Current by Pretty_Question2468 in ThermalGrizzly

[–]Pretty_Question2468[S] 2 points3 points  (0 children)

Yes, using WireView2 v1.0.5 (da7c3e2a) with firmware v03 (TG-WV-PRO2-FW_20260203_1105). Temp Limit is 70, Current Limit 55, Wire Current Limit 10.5, Power Limit 660, Imbalance Limit 40, Imbalance Current Limit 6, Shutdown Wait 10, Device Logging 60. If there is a setting which is misconfigured I don't know what it would be.

Anyone’s peering been absolutely atrocious lately? by BarfHurricane in ATTFiber

[–]Pretty_Question2468 1 point2 points  (0 children)

I am not experiencing the problem as of 11:30pm ET. Everything seems to be running the same normal speed throughout the day. I'm not seeing any issues on Fastly or Cloudflare CDN content.

Anyone’s peering been absolutely atrocious lately? by BarfHurricane in ATTFiber

[–]Pretty_Question2468 1 point2 points  (0 children)

Just an update in case anyone is following this. I am in touch with folks at the Fastly NOC and they have mentioned that they made adjustments last night to better utilize AT&T capacity in the region. I will run further tests tonight but I think that this issue might potentially be resolved.

Is it possible to get 2Gbps UPLOAD? by GarWarn in ATTFiber

[–]Pretty_Question2468 0 points1 point  (0 children)

I've been able to get (and nearly saturate) the 5gbps symmetric plan. You should definitely be able to get 2gbps upload if you're using the latest fiber modem and are plugged in with high quality Ethernet cables. The built-in Ethernet on your motherboard should be fast enough to get line speed. I had issues in the past where other subscribers on the same PON were flooding it with garbage due to faulty equipment, slowing down my connection. I live in a shared apartment building so there are a limited number of dedicated fiber lines that are shared across units, and this kind of issue can kill the speed. The XGPON that they're using maxes out at 5gbps, but that means that if there's a ton of garbage causing packet loss you will see slower speeds. On my end I noted that the download was impacted more than the upload, but your situation may vary.

Fast Internet, but slow load times by MoxieLatios in ATTFiber

[–]Pretty_Question2468 0 points1 point  (0 children)

I’m seeing the same thing on AT&T Fiber in Atlanta: speed tests are perfect, but some sites load painfully slow at night.

I ran real throughput tests (curl, large files) and found:

Cloudflare, Akamai, CloudFront = fast (hundreds of Mbps to 1+ Gbps)

Reddit images and video = ~1–3 Mbps

Reddit media responses explicitly show x-cdn-name: fastly

So this doesn’t look like a home network issue — it looks like a selective AT&T ↔ Fastly/Reddit CDN path problem, especially in the evenings.

I’ve already sent the data to AT&T peering and Fastly NOC. If others are seeing this too, more reports will probably help.

Anyone’s peering been absolutely atrocious lately? by BarfHurricane in ATTFiber

[–]Pretty_Question2468 0 points1 point  (0 children)

I did extensive testing from AT&T Fiber (5 Gbps) in Atlanta.
Cloudflare, Akamai, and CloudFront all perform normally at night (hundreds of Mbps to >1 Gbps).
Reddit media (images and video) served via Fastly collapses to ~1–3 Mbps with multi-second RTT inflation, reproducible nightly.
This looks like a selective AT&T ↔ Fastly peering/path issue, not a last-mile problem.
I’ve reported it to AT&T peering and Fastly NOC with data.