[outages] FiOS issue in NYC Area?

Izzy Goldstein - TeleGo igoldstein at telego.net
Tue Feb 16 12:45:44 EST 2021


C:\Users\Izzy>tracert 8-1-2.BR2.NYC4.ALTER.NET
Unable to resolve target system name 8-1-2.BR2.NYC4.ALTER.NET.

C:\Users\Izzy>

On Mon, Feb 15, 2021 at 12:41 PM Ethan Hayon <ethan at naturalwireless.com>
wrote:

> Traffic is getting dropped through node: 8-1-2.BR2.NYC4.ALTER.NET
>
>  1. <redacted>
>  2. <redacted>
>  3. te0-0-0-14.nr01.b026191-1.jfk01.atlas.cogentco.com
>
>  4. te0-3-0-11.rcr24.jfk01.atlas.cogentco.com
>
>  5. be2897.ccr42.jfk02.atlas.cogentco.com
>
>  6. be3496.ccr31.jfk10.atlas.cogentco.com
>
>  7. 8-1-2.BR2.NYC4.ALTER.NET
>
>  8. ???
>
> Occasionally a packet or two will get through 8-1-2.BR2.NYC4.ALTER.NET
>
> What's strange is the issue is only occurring with specific IPs on my
> office FiOS circuit (even within the same /24).
>
> These are the same symptoms we experienced in May 2019 [
> https://puck.nether.net/pipermail/outages/2019-May/012266.html]
>
> I was under the impression that Verizon has made a change on their end to
> resolve the issues.
>
> Thanks,
>
> --
> Ethan Hayon
> Natural Wireless
> [T] 201-438-2865 x416
>
>
> On Mon, Feb 15, 2021 at 12:36 PM Izzy Goldstein - TeleGo <
> igoldstein at telego.net> wrote:
>
>> What issue are you seeing ?
>>
>> On Sun, Feb 14, 2021 at 11:40 AM Ethan Hayon via Outages <
>> outages at outages.org> wrote:
>>
>>> This issue just started back up for us. Anyone else seeing this again?
>>>
>>> Seeing issues at node: 8-1-2.BR2.NYC4.ALTER.NET
>>>
>>> Thanks,
>>>
>>> --
>>> Ethan Hayon
>>> Natural Wireless
>>> [T] 201-438-2865 x416
>>>
>>>
>>> On Tue, May 14, 2019 at 11:04 AM Dovid Bender <dovid at telecurve.com>
>>> wrote:
>>>
>>>> I got an email from someone at Verizon late last night that I should
>>>> re-check and see if it is working. If anyone is still having issues let me
>>>> know and I will reach out to them.
>>>>
>>>>
>>>>
>>>> On Tue, May 14, 2019 at 10:38 AM Ethan Hayon <ethan at naturalwireless.com>
>>>> wrote:
>>>>
>>>>> It's been stable for us since around 11PM EST last night (5/13)
>>>>>
>>>>> Anyone else still seeing issues?
>>>>>
>>>>> --
>>>>> Ethan Hayon
>>>>> Natural Wireless
>>>>> [T] 201-438-2865 x416
>>>>>
>>>>>
>>>>> On Mon, May 13, 2019 at 11:55 PM Valdis Klētnieks <
>>>>> valdis.kletnieks at vt.edu> wrote:
>>>>>
>>>>>> On Mon, 13 May 2019 14:53:34 -0400, Ethan Hayon via Outages said:
>>>>>>
>>>>>> > Reachability keeps going up and down through this node. Is it 768K
>>>>>> day
>>>>>> > yet???
>>>>>>
>>>>>> I remember 128K day and 256K day, and warnings of impending doom
>>>>>> on both occasions. And both times, there were those who had to
>>>>>> withdraw
>>>>>> from the DFZ and issue emergency purchase orders because they didn't
>>>>>> plan ahead for their CAPEX needs...
>>>>>>
>>>>> _______________________________________________
>>> Outages mailing list
>>> Outages at outages.org
>>> https://puck.nether.net/mailman/listinfo/outages
>>>
>>
>>
>> --
>>
>> Izzy Goldstein
>>
>> Chief Technology Officer
>>
>> Main: (212) 477-1000 x 2085 <(212)%20477-1000>
>>
>> Direct: (929) 477-2085
>>
>> Website: www.telego.com <http://www.telego.net/>
>>
>>
>> <http://www.telego.com/>
>>
>>
>> Confidentiality Notice: This e-mail may contain confidential and/or
>> privileged information. If you are not the intended recipient or have
>> received this e-mail in error please notify us immediately by email reply
>> and destroy this e-mail. Any unauthorized copying, disclosure or
>> distribution of the material in this e-mail is strictly forbidden. Any
>> views or opinions presented in this email are solely those of the author
>> and do not necessarily represent those of TeleGo (T). Employees of TeleGo
>> are expressly required not to make defamatory statements and not to
>> infringe or authorize any infringement of copyright or any other legal
>> right by email communications. Any such communication is contrary to TeleGo
>> policy and outside the scope of the employment of the individual concerned.
>> TeleGo will not accept any liability in respect of such communication, and
>> the employee responsible will be personally liable for any damages or other
>> liability arising.
>>
>>
>> TeleGo Hosted PBX <https://youtu.be/DaT8YAZ4V0w>
>>
>

-- 

Izzy Goldstein

Chief Technology Officer

Main: (212) 477-1000 x 2085 <(212)%20477-1000>

Direct: (929) 477-2085

Website: www.telego.com <http://www.telego.net/>


<http://www.telego.com/>


Confidentiality Notice: This e-mail may contain confidential and/or
privileged information. If you are not the intended recipient or have
received this e-mail in error please notify us immediately by email reply
and destroy this e-mail. Any unauthorized copying, disclosure or
distribution of the material in this e-mail is strictly forbidden. Any
views or opinions presented in this email are solely those of the author
and do not necessarily represent those of TeleGo (T). Employees of TeleGo
are expressly required not to make defamatory statements and not to
infringe or authorize any infringement of copyright or any other legal
right by email communications. Any such communication is contrary to TeleGo
policy and outside the scope of the employment of the individual concerned.
TeleGo will not accept any liability in respect of such communication, and
the employee responsible will be personally liable for any damages or other
liability arising.


TeleGo Hosted PBX <https://youtu.be/DaT8YAZ4V0w>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20210216/e87e85a0/attachment.htm>


More information about the Outages mailing list