Any info on AT&T Wireless Outage?

Tom Beecher beecher at beecher.cc
Fri Mar 1 17:02:38 UTC 2024


>
> Erik Prince was on the PBD podcast saying he has a 70% chance in his head
> it was China.
>

Why do we care what his (almost certainly uninformed) opinion is?

On Thu, Feb 29, 2024 at 2:56 PM Javier J <javier at advancedmachines.us> wrote:

> Where did you see this? Erik Prince was on the PBD podcast saying he has a
> 70% chance in his head it was China. I tend to learn towards human error
> from my experience in the IT biz.
>
> - J
>
> On Wed, Feb 28, 2024 at 10:58 AM <joel at joelesler.net> wrote:
>
>> I read it as “someone pushed an ACL that wasn’t properly reviewed and it
>> really screwed things up."
>>
>> On Feb 27, 2024, at 21:41, Mark Seiden <mis at seiden.com> wrote:
>>
>> aside from the official pablum that was released about an “incorrect
>> process used”
>> (which says exactly nothing) does anyone actually know anything accurate
>> and
>> more specific about the root cause?
>>
>> (and why it took 11 hours to recover?)
>>
>> On Feb 22, 2024, at 11:15 AM, John Councilman <jcouncilman at gmail.com>
>> wrote:
>>
>> From what I've read, they lost their database of SIM cards.  I could be
>> wrong of course.
>>
>> On Thu, Feb 22, 2024 at 2:02 PM Dorn Hetzel <dorn at hetzel.org> wrote:
>>
>>> As widespread as it seemed to be, it feels like it would be quite a
>>> trick if it were a single piece of hardware.  Firmware load that ended
>>> badly, I wonder?
>>>
>>>
>>> On Thu, Feb 22, 2024 at 1:51 PM Leato, Gary via NANOG <nanog at nanog.org>
>>> wrote:
>>>
>>>> Do you have the ability to expand on this at all? Do you mean a
>>>> hardware failure of some kind IE router, optitcs, etc?
>>>>
>>>>
>>>>
>>>> *From:* NANOG <nanog-bounces+gleato=advance-trading.com at nanog.org> *On
>>>> Behalf Of *R. Leigh Hennig
>>>> *Sent:* Thursday, February 22, 2024 8:17 AM
>>>> *To:* Robert DeVita <radevita at mejeticks.com>
>>>> *Cc:* nanog at nanog.org
>>>> *Subject:* Re: Any info on AT&T Wireless Outage?
>>>>
>>>>
>>>>
>>>> Word around the campfire is that it’s a Cisco issue.
>>>>
>>>>
>>>>
>>>> On Feb 22, 2024, at 8:03 AM, Robert DeVita <radevita at mejeticks.com>
>>>> wrote:
>>>>
>>>>
>>>>
>>>> Reports have it starting at 4:30 a.m.. SOS on all phones..
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> *Robert DeVita**​**​**​**​*
>>>>
>>>> *CEO and Founder*
>>>>
>>>> t: (469) 581-2160 <(469)%20581-2160>
>>>>
>>>>  |
>>>>
>>>> m: (469) 441-8864 <(469)%20441-8864>
>>>>
>>>> e: radevita at mejeticks.com
>>>>
>>>>  |
>>>>
>>>> w: mejeticks.com <https://www.mejeticks.com/>
>>>>
>>>> a:
>>>>
>>>> 2323 N Akard Street
>>>>
>>>> ,
>>>>
>>>> Dallas
>>>>
>>>> ,
>>>>
>>>> 75201
>>>>
>>>> <https://www.linkedin.com/company/mejeticks/>
>>>>
>>>> <https://twitter.com/mejeticks>
>>>>
>>>> <https://www.facebook.com/mejeticks>
>>>>
>>>> <https://linktr.ee/mejeticks>
>>>>
>>>>
>>>>
>>>>
>>>> The risk of trading futures and options can be substantial. All
>>>> information, publications, and material used and distributed by Advance
>>>> Trading Inc. shall be construed as a solicitation. ATI does not maintain an
>>>> independent research department as defined in CFTC Regulation 1.71.
>>>> Information obtained from third-party sources is believed to be reliable,
>>>> but its accuracy is not guaranteed by Advance Trading Inc. Past performance
>>>> is not necessarily indicative of future results.
>>>>
>>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20240301/d4e607b1/attachment.html>


More information about the NANOG mailing list