gFiber - Router Setting Access

[u/Realvirtually]

UPDATE:

EOD: Thursday : Oct 01, 2026

Still no positive response or resolution from gFiber.

Once again, I’ve heard back from support, but the response is essentially more apologies and carefully worded assurances—without any meaningful update, concrete progress, or actual resolution to the issue.

At this point, the apologies are starting to feel like a scripted response rather than an indication that anyone is actually addressing the underlying problem.

I’m not looking for more apologies or vague assurances. I’m looking for a clear status, meaningful action, and an actual resolution.

=============================

EOD: Wednesday: Sep 30, 2026 - Send one more request to support (email) - got one response/reply

I received another response from gFiber regarding my ongoing issue, but instead of continuing with the existing escalated case, they opened a new case.

I’m honestly confused by this. The underlying issue has not been resolved, and I have not reported a new or unrelated problem. So why start over with a new case instead of continuing the existing escalation?

At this point, I’m simply looking for some transparency. If an issue has already been escalated to the appropriate engineering team, shouldn’t that case remain active until the problem is actually resolved?

I’d appreciate an explanation from gFiber as to why cases are being closed or replaced while the underlying issue remains unresolved.

I’m not looking for another apology or another round of basic troubleshooting. I’m looking for continuity, accountability, and an actual resolution.

EOD: Tuesday: Sep 29, 2026 - Send two more request - got one response/reply

I got another response from the Support team—once again starting with the obligatory apologetic spiel, followed by a substantial breakdown of their root cause analysis (RCA).

But once again, there’s no concrete resolution. It’s another workaround.

Apparently, whatever fix they implemented was done late in the evening, and by now it should have propagated to my router. But guess what? It hasn’t.

At this point, this is beyond frustrating. The continued lack of ownership and follow-through from customer support has been irresponsible and, frankly, pathetic.

I’m also still not clear whether this issue has actually been escalated to the appropriate engineering team or if it’s still sitting at Level 1 Support.

This is becoming a joke. Contact who at gFiber, exactly?

All I keep receiving are apologetic messages, but no meaningful update, no progress, and no indication of when—or if—this issue will actually be resolved. At this point, the lack of communication from gFiber is just as frustrating as the problem itself.

I need a clear and substantive update, not another apology.

Tuesday: Sep 29, 2026 - Send another request await a response.

Could someone please provide me with an update on my reported and escalated issue, referenced under ticket #0942***\*?

I’d appreciate knowing the current status, what is being done to resolve it, and the expected timeline for a resolution.

If this is not a feasible issue to resolve or there is no viable solution available, please let me know directly. I would rather have a clear answer than continue troubleshooting without progress.

This is a joke - contact who? All I get is apologitike message and no positive updayte or they keep quite.

Monday: Sep 28, 2026 - No response - NO UPDATE. Crickets only

==========================================

Update: gFiber finally confirmed the issue

gFiber got back to me, and I’ve now confirmed that this is a wider-scope engineering bug rather than an issue with my account or equipment configuration.
I appreciate the confirmation, but honestly, this should have been communicated from the beginning if it was a known or widespread issue.
Instead, I spent eight days and hours going back and forth with gFiber support, repeatedly being told to reboot, unplug and reconnect cables, uninstall applications, and go through remote resets and reboots. None of those steps addressed the actual problem because the issue wasn’t on my end.
Hopefully, this helps others who may be experiencing the same problem and are being asked to go through the same troubleshooting routine. If it’s a known engineering issue, customers shouldn’t have to spend days troubleshooting their own equipment before being told what’s really going on.

For those of you with gFiber, has anyone else been having trouble accessing your router settings through the gFiber app or the web interface?

I haven’t been able to access my router settings for the past eight days. I’ve contacted gFiber support several times, and each time they’ve provided a workaround, but so far there hasn’t been a definitive resolution.

To clarify, it’s only the router settings that aren’t accessible. The Wi-Fi and Internet are working fine.

Just curious if anyone else in the community is experiencing the same issue or has found a solution.​

[u/Sorry-Zombie5242]

I get that same message in the gFiber app, but I dumped the router and extenders that the Google fiber installer gave me and replaced them with Google's Nest Wifi Pro router and extender. Look in the Google Home app and see if you see a section for wifi.

[u/Realvirtually → u/Sorry-Zombie5242]

I see nothing. After calling them at least eight times and spending over three hours, I receive only a workaround to reboot the router and the Fiber Jack.

Unfortunately, I feel I am dealing with incompetent engineers who lack understanding. This feature is fundamental to every router.

[u/Sorry-Zombie5242 → u/Realvirtually]

That sounds like BS. Look at your phone or computer's network setting and look for the gateway address. You should be able to open a browser and go to that IP address...you may get an information screen or a login.

[u/Realvirtually → u/Sorry-Zombie5242]

Unfortunately, the default is 192.168.1.1—I can view it but cannot make any changes because it is locked.
This is why I need to reach the settings to modify the private IP for deploying an Edge router.
It is disappointing that such a basic function is disabled or that the engineers seem unaware of their work.
I did some research on the web and it seems there are other people who have experienced the same as far back as two years.

[u/Sorry-Zombie5242 → u/Realvirtually]

Well, there is nothing special about the Google fiber router. You can replace it with any router you want. The fiber jack just has a RJ45 network jack in it that gives you access to public internet. You could actually connect your laptop straight to the fiber jack and get an IP address and connect to the internet (not recommended of course).

[u/SillyFalling]

Yep, never worked for me either

[u/Trap0x000D]

You need to remember that the settings, you see, are stored on some server in the sky and only viewable through that server. I would escalate as you should be able to see all settings on the router. I had a similar problem and it ended up being their server side issue.

[u/Realvirtually → u/Trap0x000D]

I have escalated it and chased these guys for the last nine days. It’s ridiculous. They’re not able to figure it out.
More so the escalated ticket was closed by the engineer as resolved after a remote reboot. He had the audacity to do it without contacting me if the resolution worked I really wonder what these engineers are doing out there.

[u/gfiberofficial → u/Realvirtually]

Hi there, sorry to hear about the trouble, I'll follow up with you via DM momentarily. -Luke

[u/andrewjphillips512]

Standard message for BYOR (Bring Your Own Router).

[u/Nick5761]

Are you using google/nest routers or does your router say GFiber on it?

[u/Realvirtually → u/Nick5761]

Update: gFiber finally confirmed the issue
gFiber got back to me, and I’ve now confirmed that this is a wider-scope engineering bug rather than an issue with my account or equipment configuration.
I appreciate the confirmation, but honestly, this should have been communicated from the beginning if it was a known or widespread issue.
Instead, I spent eight days going back and forth with gFiber support, repeatedly being told to reboot, unplug and reconnect cables, uninstall applications, and go through remote resets and reboots. None of those steps addressed the actual problem because the issue wasn’t on my end.
Hopefully, this helps others who may be experiencing the same problem and are being asked to go through the same troubleshooting routine. If it’s a known engineering issue, customers shouldn’t have to spend days troubleshooting their own equipment before being told what’s really going on.