192.168.1.254 Not Working? AT&T Router Login Fix (2026)

Quick Answer

192.168.1.254 is the default admin address for AT&T-supplied gateways — the BGW210, BGW320, Pace 5268AC, and older 2Wire units. To get in, connect to the gateway's Wi-Fi or Ethernet, type 192.168.1.254 into your browser's address bar, and enter your credentials — often admin, with the password printed on the gateway's label. If the page won't load and you're running your own third-party router behind the AT&T gateway, the most common cause is a subnet conflict, not a wrong address — covered in detail below.

You typed 192.168.1.254 into your browser expecting your router's admin page, and instead got a blank screen, an error, or a page that never loads. This address trips people up more than most default gateways, mainly because of one specific, well-documented conflict that has nothing to do with your password.

I've seen this exact address confuse more people than almost any other default gateway, and it's rarely the AT&T hardware itself that's broken.

First: Is It the Wrong Address, a Subnet Conflict, or Wrong Credentials?

Symptom	Likely cause
Page doesn't load at all, browser shows an error	You may be behind a third-party router whose own LAN range is swallowing this address before it can reach the gateway
Browser redirects to a search results page	You typed the address into the search bar instead of the address bar
Login page loads, but credentials are rejected	Password was changed previously, or you're using the wrong default for your specific model
Works when connected directly to the AT&T gateway, fails through your own router	Confirms a subnet conflict — your router's LAN and the gateway's LAN overlap
Nothing loads on any device, any connection method	Gateway itself may be offline or in a different mode

Why 192.168.1.254 Breaks More Often Than Other Default IPs

This is the part most guides skip, and it's the actual reason a lot of people land on this page.

If you've replaced AT&T's supplied gateway with your own router (running in what AT&T calls Passthrough or IP Passthrough mode) and your own router's LAN also happens to use the 192.168.1.0/24 range, then 192.168.1.254 gets treated as just another address on your router's local network — not as a request destined for the AT&T gateway sitting upstream on the WAN side. Your router simply never forwards the request anywhere, because as far as it's concerned, .254 is a device on its own LAN, not a separate box entirely.

This isn't a bug or a sign anything is broken. It's a routing/addressing coincidence, and it's common enough that it comes up repeatedly in networking forums whenever someone switches to AT&T fiber or U-verse while keeping their own router.

The fix: Change your own router's LAN subnet to something that doesn't overlap — for example 192.168.2.0/24 or 10.0.0.0/24 (use our Subnet Calculator) — instead of leaving it on 192.168.1.0/24. Once your router's LAN no longer includes .254, requests to that address correctly route out to the AT&T gateway on the WAN side instead of being absorbed locally.

Step-by-Step Fix (In the Order That Actually Works)

1Confirm You're on the Right Network

Connect the device you're using directly to the AT&T gateway — either its own Wi-Fi network or an Ethernet cable straight into it — not through a separate router, at least for this first test.

2Type the Address Into the Address Bar

Open any browser.
Click directly into the address bar.
Type 192.168.1.254 and press Enter.

If it redirects to search results, type http://192.168.1.254 with the http:// included to force it as an address rather than a search query.

3Enter Your Login Credentials

AT&T Gateway Model	Default Username	Default Password
BGW210	`admin`	Printed on device label (unique per unit)
BGW320	`admin`	Printed on device label (unique per unit)
Pace 5268AC	`admin`	Printed on device label
2Wire (older)	`admin`	admin or blank

Newer AT&T gateways (BGW210 and later) ship with a unique password printed on the physical label, not a shared generic default like admin/admin. Check the label first, always.

4If You're Behind Your Own Router, Test the Subnet Conflict

Temporarily connect a device straight to the AT&T gateway (bypassing your own router).
Try 192.168.1.254 again.
If it loads now but didn't through your router, you've confirmed the subnet conflict described above — the fix is changing your router's LAN range, not troubleshooting the gateway.

5Try an Incognito Window or a Different Browser

A cached session can cause the login page to load inconsistently. Try a private/incognito window, or a different browser entirely.

6Turn Off Any VPN

VPNs can reroute local traffic in ways that block access to a local gateway address. Disable it before trying again.

7Locked Out? Factory Reset Is the Only Way Back In

Find the small reset button on the gateway — usually recessed.
Press and hold for 10-15 seconds while powered on.
Release and wait 2-3 minutes for it to fully reboot.
Log in with the default credentials from the label.

This wipes all custom settings, including any Passthrough/IP Passthrough configuration you'd set up for a third-party router — you'll need to reconfigure that afterward.

What to Do Once You're Logged In

Enable IP Passthrough: If you're running your own router and want it to receive the public IP directly — found under Firewall or Broadband settings on most AT&T gateways.
Change the admin password: If it's still on a shared/known default.
Update your Wi-Fi network name and password: Especially if you're only using the gateway as a modem behind your own router's Wi-Fi.
Check for a firmware update: Under the device's Diagnostics or System section.

Frequently Asked Questions

Why does 192.168.1.254 not load when I have my own router?

The most common cause is a subnet conflict — if your own router's LAN also uses the 192.168.1.0/24 range, it treats .254 as a local device rather than forwarding the request to the AT&T gateway upstream. Changing your router's LAN range resolves this.

What's the default password for 192.168.1.254?

Newer AT&T gateways (BGW210 and later) use a unique password printed on the device's physical label rather than a shared generic default — check there first rather than trying common admin/admin combinations.

Is 192.168.1.254 only used by AT&T?

It's most strongly associated with AT&T-supplied gateways (BGW210, BGW320, Pace 5268AC, older 2Wire units), though any device can technically be configured to use it — the AT&T association is by far the most common case people are searching for.

Can I use 192.168.1.254 and 192.168.1.1 on the same network?

Only if your own router's LAN subnet is changed to avoid the 192.168.1.0/24 range entirely — otherwise .254 gets absorbed into your router's own LAN and never reaches the AT&T gateway, which is exactly the conflict described above.

I'm locked out — what now?

A factory reset via the recessed reset button is the only reliable path back in if the password was changed and you don't have it. This also resets any custom Passthrough configuration.

Why does my browser show a "Not Secure" warning at 192.168.1.254?

AT&T gateway admin pages typically run over HTTP rather than HTTPS with a trusted certificate, which triggers this warning in modern browsers. This is expected for a local admin page and not a sign of a real security problem, as long as you're on your own network.

The Bottom Line

192.168.1.254 almost always comes down to one of two things: you're behind a third-party router whose LAN range is quietly absorbing the address, or you're using the wrong credentials for an AT&T gateway that actually ships with a unique printed password. Test the direct-connection method first — it isolates the cause faster than anything else on this page.