[Outages-discussion] [outages] FiOS issue in NYC Area?

Izzy Goldstein - TeleGo igoldstein at telego.net
Thu Feb 18 15:07:30 EST 2021 

i basically wasn't seeing any packets from our data center, reaching our
clients Phone System,
the phone system couldn't register to our registration server

the phone system was sending a register request, my server would receive
and respond to it, but the phone system wasn't getting the packet, i was
seeing it leave our edge device in the data center....


On Thu, Feb 18, 2021 at 12:40 PM Ethan Hayon <ethan at naturalwireless.com>
wrote:

> I have a number of endpoints behind a cogent IP transit circuit. My office
> has a FiOS business circuit.
>
> I am seeing sporadic reachability issues from specific IPs behind my
> Cogent circuit, to specific IPs behind my office FiOS circuit.
>
> And the reachability issues start and stop for different IPs at various
> times.
>
> Are you seeing similar issues to what we saw in May 2019? (this is pretty
> much identical to what we saw at that time)
>
> Thanks,
>
> --
> Ethan Hayon
> Natural Wireless
> [T] 201-438-2865 x416
>
>
> On Thu, Feb 18, 2021 at 12:37 PM Izzy Goldstein - TeleGo <
> igoldstein at telego.net> wrote:
>
>> i have that contact from verizon,. and i am trying to work with him
>> he emailed me saying to retest and it should work, (but the issues i've
>> had on my end, is still present)
>>
>> What issues are you having?
>>
>> On Thu, Feb 18, 2021 at 12:33 PM Ethan Hayon <ethan at naturalwireless.com>
>> wrote:
>>
>>> Hi Izzy,
>>>
>>> Yes, we are still seeing issues. I contacted Verizon a few days ago and
>>> they were supposed to be escalating to a "network specialist" - they never
>>> reached back out to me.
>>>
>>> Last time we saw this issue in 2019, I know someone reached out to a
>>> contact at Verizon, who was able to resolve the issue. I don't recall who
>>> had the proper contact at VZ.
>>>
>>> Thanks,
>>>
>>> --
>>> Ethan Hayon
>>> Natural Wireless
>>> [T] 201-438-2865 x416
>>>
>>>
>>> On Thu, Feb 18, 2021 at 12:14 PM Izzy Goldstein - TeleGo <
>>> igoldstein at telego.net> wrote:
>>>
>>>> Thank you for explaining, well noted
>>>>
>>>>
>>>> Ethan, are you still experiencing issues ?
>>>>
>>>> On Tue, Feb 16, 2021 at 6:58 PM Jeremy Chadwick <jdc at koitsu.org> wrote:
>>>>
>>>>> Several backbone providers define DNS PTR records (reverse) of their
>>>>> routers interface IPs, but not A records (forward).
>>>>> Verizon/MCI/Alter/UUnet is notorious for this; it's nothing new.
>>>>>
>>>>> traceroute doesn't "involve DNS" as part of how the actual protocol
>>>>> (methodology) works -- the traceroute client only sees IPs in ICMP
>>>>> time-exceeded responses to initial UDP or TCP probes.  Thus, the
>>>>> traceroute/tracert client issues PTR record lookups (on *IX usually by
>>>>> gethostbyaddr()) and shows whatever the results are.  Forward lookups
>>>>> aren't usually done (though some "enhanced" traceroute clients like mtr
>>>>> and WinMTR do).  Otherwise, tell your traceroute client to only show IP
>>>>> addresses, and not do reverse lookups.
>>>>>
>>>>> $ dig a 8-1-2.b2.nyc4.alter.net
>>>>> ...
>>>>> ;; Got answer:
>>>>> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 29284
>>>>>
>>>>> $ dig ptr 201.110.179.152.in-addr.arpa
>>>>> ...
>>>>> ;; ANSWER SECTION:
>>>>> 201.110.179.152.in-addr.arpa. 21427 IN  PTR
>>>>> 8-1-2.BR2.NYC4.ALTER.NET.
>>>>>
>>>>> Now you're going to ask: "how did you find IP 152.179.110.201 ?"
>>>>> The answer is: Googling "8-1-2.b2.nyc4.alter.net" and hoping someone
>>>>> on the Internet provided traceroute results that contained IPs in
>>>>> addition to PTR -- in this case, 4 search results were good enough.
>>>>>
>>>>> There are other ways of determining this as well, but I'm intentionally
>>>>> omitting that procedure, as it's brute-force and not always reliable.
>>>>>
>>>>> --
>>>>> | Jeremy Chadwick                                 jdc at koitsu.org |
>>>>> | UNIX Systems Administrator                      PGP 0x2A389531 |
>>>>> | Making life hard for others since 1977.                        |
>>>>>
>>>>> On Tue, Feb 16, 2021 at 12:45:44PM -0500, Izzy Goldstein - TeleGo via
>>>>> Outages wrote:
>>>>> > 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>
>>>>>
>>>>> > _______________________________________________
>>>>> > Outages mailing list
>>>>> > Outages at outages.org
>>>>> > https://puck.nether.net/mailman/listinfo/outages
>>>>>
>>>>> _______________________________________________
>>>>> Outages-discussion mailing list
>>>>> Outages-discussion at outages.org
>>>>> https://puck.nether.net/mailman/listinfo/outages-discussion
>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> 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>
>>
>

-- 

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-discussion/attachments/20210218/e43ea217/attachment-0001.htm>

More information about the Outages-discussion mailing list