Wifi Extender 2 stuck on 11a

[jav6]

---

@casohio2mn wrote:

Same issue here. We are also in a known dead zone and have 3 Verizon 4g extenders in our house all stuck on 11a of 14. From reading posts and past experience we will not even try to reboot. We will take the wait and hope strategy......

---

People are reporting the Verizon extender outage on https://downdetector.com/status/verizon/

Maybe a VZW agent here can get (pro)active and follow up with Technical Support for an update?

[PJODEN]

Such an inconvenience. I work from home and rely heavily on this for my cell phone. Call support and they don't have a clue. Hopefully someone gets on it soon to get it fixed.

[PJODEN]

I have and still have the issue.

[awack1]

Same issue here. Ugh

[RaiderMarine3]

Me Too

[Mwniswonger]

I woke up this morning with the same issue. Stuck on step 11a.

Worked fine last night.

[jav6]

Tracing the route to the Security Gateway, sg.vzwfemto.com completes.  A continuous ping to the SG shows instability in responding.  Hopefully, they'll resolve it soon.

Microsoft Windows [Version 10.0.18363.959]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Users\Joe>ping -t 69.78.33.148

Pinging 69.78.33.148 with 32 bytes of data:
Reply from 69.78.33.148: bytes=32 time=1558ms TTL=49
Reply from 69.78.33.148: bytes=32 time=1575ms TTL=49
Request timed out.
Request timed out.
Reply from 69.78.33.148: bytes=32 time=1593ms TTL=49
Reply from 69.78.33.148: bytes=32 time=1574ms TTL=49
Request timed out.
Request timed out.
Reply from 69.78.33.148: bytes=32 time=1588ms TTL=49
Reply from 69.78.33.148: bytes=32 time=1584ms TTL=49
Reply from 69.78.33.148: bytes=32 time=1588ms TTL=49
Reply from 69.78.33.148: bytes=32 time=1601ms TTL=49
Request timed out.
Request timed out.
Reply from 69.78.33.148: bytes=32 time=1591ms TTL=49
Reply from 69.78.33.148: bytes=32 time=1588ms TTL=49
Request timed out.
Reply from 69.78.33.148: bytes=32 time=1602ms TTL=49
Request timed out.
Reply from 69.78.33.148: bytes=32 time=1618ms TTL=49
Reply from 69.78.33.148: bytes=32 time=1584ms TTL=49
Reply from 69.78.33.148: bytes=32 time=1590ms TTL=49
Reply from 69.78.33.148: bytes=32 time=1581ms TTL=49
Request timed out.
Reply from 69.78.33.148: bytes=32 time=1577ms TTL=49
Reply from 69.78.33.148: bytes=32 time=1582ms TTL=49
Reply from 69.78.33.148: bytes=32 time=1588ms TTL=49
Reply from 69.78.33.148: bytes=32 time=1586ms TTL=49
Request timed out.
Request timed out.
Reply from 69.78.33.148: bytes=32 time=1565ms TTL=49
Reply from 69.78.33.148: bytes=32 time=1536ms TTL=49
Reply from 69.78.33.148: bytes=32 time=1602ms TTL=49
Request timed out.
Reply from 69.78.33.148: bytes=32 time=1601ms TTL=49
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 69.78.33.148: bytes=32 time=1589ms TTL=49
Reply from 69.78.33.148: bytes=32 time=1627ms TTL=49
Request timed out.
Request timed out.
Reply from 69.78.33.148: bytes=32 time=1558ms TTL=49
Reply from 69.78.33.148: bytes=32 time=1602ms TTL=49
Reply from 69.78.33.148: bytes=32 time=1597ms TTL=49
Request timed out.
Request timed out.
Reply from 69.78.33.148: bytes=32 time=1601ms TTL=49
Request timed out.
Reply from 69.78.33.148: bytes=32 time=1616ms TTL=49
Request timed out.
Request timed out.
Reply from 69.78.33.148: bytes=32 time=1606ms TTL=49
Request timed out.
Request timed out.
Reply from 69.78.33.148: bytes=32 time=1617ms TTL=49
Reply from 69.78.33.148: bytes=32 time=1578ms TTL=49
Request timed out.
Request timed out.
Reply from 69.78.33.148: bytes=32 time=1620ms TTL=49
Reply from 69.78.33.148: bytes=32 time=1573ms TTL=49
Reply from 69.78.33.148: bytes=32 time=1556ms TTL=49
Reply from 69.78.33.148: bytes=32 time=1585ms TTL=49
Reply from 69.78.33.148: bytes=32 time=1581ms TTL=49
Reply from 69.78.33.148: bytes=32 time=1587ms TTL=49
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 69.78.33.148: bytes=32 time=1618ms TTL=49
Request timed out.
Reply from 69.78.33.148: bytes=32 time=1553ms TTL=49
Reply from 69.78.33.148: bytes=32 time=1581ms TTL=49
Reply from 69.78.33.148: bytes=32 time=1597ms TTL=49

Ping statistics for 69.78.33.148:
Packets: Sent = 77, Received = 43, Lost = 34 (44% loss),
Approximate round trip times in milli-seconds:
Minimum = 1536ms, Maximum = 1627ms, Average = 1588ms
Control-C
^C
C:\Users\Joe>

[Mwniswonger]

Horrible ping times. Hopefully Verizon gets it fixed soon. I have no landlines and need my service operating.

[chefgf]

Same issue here.

[jav6]

Just talked with Technical Support who provided latest update:

"Ticket opened early this morning, escalated to 'highest level' network team.  No estimated timeframe yet for resolution"