Mailing List Archive

Verizon in Seattle WA
Hi,

I have customer with Verizon having either DNS resolution issues or
return traffic back to them is not being received.  I suspect that the
Verizon DNS resolvers are going though the same path that the return
traffic is going down. I have/am working on contacting my upstreams. The
numbers I have found to call version have failed as I do not have an
account.

Maybe someone here has some information, or has a way to help?

two know IP's that I am unable to reach are: 72.83.97.146 and 100.18.11.5

Sample traceroute from me 208.77.208.1 / AS13438:

traceroute to 72.83.97.146 (72.83.97.146), 30 hops max, 40 byte packets
 1  216.243.28.217  11.431 ms  11.387 ms  11.933 ms
 2  174.127.149.137  12.008 ms  11.941 ms  11.902 ms
 3  69.174.9.189  11.294 ms  11.293 ms  11.237 ms
 4  89.149.130.78  11.126 ms 89.149.130.54  12.343 ms  14.100 ms
 5  204.148.146.45  11.284 ms  11.216 ms  11.262 ms
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * * (Repeating)

This does not seem to be isolated to me. One of my upstreams confirmed
they could not ping one of the above IP's and if you check out this
remote IP testing site you can see it doesn't seem to be able to reach
it from the two Seattle ISP's. (You can click "Show" on the line to see
traceroute details)

https://ping.pe/72.83.97.146

https://ping.pe/100.18.11.5

Thank you to anyone in advance that reviews or looks into this.

Sincerely,

--
Mark Keymer
President
Vivio Technologies
Toll Free: 1-877-448-4846
Local: 1-509-593-4207

_______________________________________________
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages
Re: Verizon in Seattle WA [ In reply to ]
Seems to be only having issues in the US, looking at Globalping:
https://www.jsdelivr.com/globalping

Kind regards,

Wieger Bontekoe
Principal Site Reliability Engineer
wieger.bontekoe@productsup.com

Op do 4 apr 2024 19:49 schreef Mark Keymer via Outages <outages@outages.org
>:

> Hi,
>
> I have customer with Verizon having either DNS resolution issues or
> return traffic back to them is not being received. I suspect that the
> Verizon DNS resolvers are going though the same path that the return
> traffic is going down. I have/am working on contacting my upstreams. The
> numbers I have found to call version have failed as I do not have an
> account.
>
> Maybe someone here has some information, or has a way to help?
>
> two know IP's that I am unable to reach are: 72.83.97.146 and 100.18.11.5
>
> Sample traceroute from me 208.77.208.1 / AS13438:
>
> traceroute to 72.83.97.146 (72.83.97.146), 30 hops max, 40 byte packets
> 1 216.243.28.217 11.431 ms 11.387 ms 11.933 ms
> 2 174.127.149.137 12.008 ms 11.941 ms 11.902 ms
> 3 69.174.9.189 11.294 ms 11.293 ms 11.237 ms
> 4 89.149.130.78 11.126 ms 89.149.130.54 12.343 ms 14.100 ms
> 5 204.148.146.45 11.284 ms 11.216 ms 11.262 ms
> 6 * * *
> 7 * * *
> 8 * * *
> 9 * * *
> 10 * * * (Repeating)
>
> This does not seem to be isolated to me. One of my upstreams confirmed
> they could not ping one of the above IP's and if you check out this
> remote IP testing site you can see it doesn't seem to be able to reach
> it from the two Seattle ISP's. (You can click "Show" on the line to see
> traceroute details)
>
> https://ping.pe/72.83.97.146
>
> https://ping.pe/100.18.11.5
>
> Thank you to anyone in advance that reviews or looks into this.
>
> Sincerely,
>
> --
> Mark Keymer
> President
> Vivio Technologies
> Toll Free: 1-877-448-4846
> Local: 1-509-593-4207
>
> _______________________________________________
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
Re: Verizon in Seattle WA [ In reply to ]
Update:

I had a off-list DM which mentioned things were looking for for them via
same path(Always appreciate the helpful DM's ;) ). And we also are
starting to get word back from clients that things are working.

I do not know if someone here helped. But if you did I very much
appreciate it.

Sincerely,

Mark Keymer
President
Vivio Technologies
Toll Free: 1-877-448-4846
Local: 1-509-593-4207

On 4/4/2024 11:06 AM, Wieger Bontekoe wrote:
> Seems to be only having issues in the US, looking at Globalping:
> https://www.jsdelivr.com/globalping
>
> Kind regards,
>
> Wieger Bontekoe
> Principal Site Reliability Engineer
> wieger.bontekoe@productsup.com
>
> Op do 4 apr 2024 19:49 schreef Mark Keymer via Outages
> <outages@outages.org>:
>
> Hi,
>
> I have customer with Verizon having either DNS resolution issues or
> return traffic back to them is not being received.  I suspect that
> the
> Verizon DNS resolvers are going though the same path that the return
> traffic is going down. I have/am working on contacting my
> upstreams. The
> numbers I have found to call version have failed as I do not have an
> account.
>
> Maybe someone here has some information, or has a way to help?
>
> two know IP's that I am unable to reach are: 72.83.97.146 and
> 100.18.11.5
>
> Sample traceroute from me 208.77.208.1 / AS13438:
>
> traceroute to 72.83.97.146 (72.83.97.146), 30 hops max, 40 byte
> packets
>   1  216.243.28.217  11.431 ms  11.387 ms  11.933 ms
>   2  174.127.149.137  12.008 ms  11.941 ms  11.902 ms
>   3  69.174.9.189  11.294 ms  11.293 ms  11.237 ms
>   4  89.149.130.78  11.126 ms 89.149.130.54  12.343 ms 14.100 ms
>   5  204.148.146.45  11.284 ms  11.216 ms  11.262 ms
>   6  * * *
>   7  * * *
>   8  * * *
>   9  * * *
> 10  * * * (Repeating)
>
> This does not seem to be isolated to me. One of my upstreams
> confirmed
> they could not ping one of the above IP's and if you check out this
> remote IP testing site you can see it doesn't seem to be able to
> reach
> it from the two Seattle ISP's. (You can click "Show" on the line
> to see
> traceroute details)
>
> https://ping.pe/72.83.97.146
>
> https://ping.pe/100.18.11.5
>
> Thank you to anyone in advance that reviews or looks into this.
>
> Sincerely,
>
> --
> Mark Keymer
> President
> Vivio Technologies
> Toll Free: 1-877-448-4846
> Local: 1-509-593-4207
>
> _______________________________________________
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>