Re: [outages] [ADMIN] Re: [Telnyx #1243282] Twitter API problems Fri/13

[Brett Dikeman via Outages]

On Sat, Jan 14, 2023 at 12:12 AM Jay R. Ashworth via Outages <
outages@outages.org> wrote:

YO, Telnyx!  If you can't keep your ticketing system from replying
> to posters, please unsubscribe it from the list now.
>

They've been doing this for at least three years; I see as far back as '19
their systems have been sending ticket and customer satisfaction survey
emails to authors of list posts.

Please just kick and ban their entire domain; they clearly don't care.
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] Vocus routing US Salesforce.com traffic through Australia?

[Brett Dikeman via Outages]

Yet another reminder this list is not for troubleshooting or diagnostics. This 
belongs on outages-discuss.

> On Sep 8, 2021, at 5:22 PM, Eric Lester via Outages  
> wrote:
> 
> 
> Received latency complaints from one location in Nashville with Centurylink 
> Internet. Traceroutes showed traffic routing through Australia. Looks like 1 
> of 8 Salesforce.com publicly resolved IP’s is currently being routed through 
> San Jose, California and then to Australia before coming back to US. We sent 
> the info to Salesforce.com through a ticket but I’m doubtful of it making it 
> to someone that can figure out what to do with the info.
>  
> Just curious if anyone has insight into what is going on. I am not familiar 
> with Australia ISP’s etc.
>  
> Public IP’s I’m receiving
>  
> NSLOOKUP salesforce.com
> Name:salesforce.com
> Addresses:  23.1.35.132
>   23.1.99.130
>   23.1.106.133
>   104.109.10.129
>   104.109.11.129
>   184.25.179.132
>   184.31.3.130
>   184.31.10.133
>  
> Traceroutes from a couple of public hosts
>  
> Lumen Traceroute
> NASHVILLE TN USA Traceroute results for: 23.1.35.132 
> (a23-1-35-132.deploy.static.akamaitechnologies.com)
>  
> Tracing route to 23.1.35.132 1 ae-2-3605.edge9.SanJose1.Level3.net 
> (4.69.219.65) 61ms 70ms 60ms
> 2 0.0.0.0 (0.0.0.0) * * *
> 3 be100.bdr03.sjc01.ca.us.vocus.network (114.31.199.32) 205ms 205ms 
> be203.cor01.syd11.nsw.vocus.network (114.31.199.40) 208ms
> 4 be101.bdr04.syd03.nsw.vocus.network (114.31.192.47) 208ms 
> be202.cor02.syd04.nsw.vocus.network (114.31.199.42) 205ms 205ms
> 5 static-74.173.255.49.in-addr.VOCUS.net.au (49.255.173.74) 210ms 
> be100.bdr04.syd03.nsw.vocus.network (114.31.192.45) 205ms 
> static-74.173.255.49.in-addr.VOCUS.net.au (49.255.173.74) 223ms
> 6 a23-1-240-228.deploy.static.akamaitechnologies.com (23.1.240.228) 208ms 
> static-74.173.255.49.in-addr.VOCUS.net.au (49.255.173.74) 212ms 212ms
> 7 0.0.0.0 (0.0.0.0) * * a23-1-240-143.deploy.static.akamaitechnologies.com 
> (23.1.240.143) 205ms
> 8 static-73.173.255.49.in-addr.VOCUS.net.au (49.255.173.73) 208ms 0.0.0.0 
> (0.0.0.0) * *
> 9 be114.cor02.syd04.nsw.vocus.network (114.31.192.44) 356ms 356ms 
> static-73.173.255.49.in-addr.VOCUS.net.au (49.255.173.73) 205ms
> 10 be114.cor02.syd04.nsw.vocus.network (114.31.192.44) 356ms 
> be202.bdr03.sjc01.ca.us.vocus.network (114.31.199.43) 359ms 
> be114.cor02.syd04.nsw.vocus.network (114.31.192.44) 357ms
> 11 173.205.35.1 (173.205.35.1) 359ms 356ms 
> be202.bdr03.sjc01.ca.us.vocus.network (114.31.199.43) 356ms
> 12 173.205.35.1 (173.205.35.1) 356ms ae18-3416.cr11-fra2.ip4.gtt.net 
> (89.149.180.134) 356ms ae6.cr6-sjc1.ip4.gtt.net (89.149.180.78) 356ms
> 13 ae18-3416.cr11-fra2.ip4.gtt.net (89.149.180.134) 357ms 354ms ip4.gtt.net 
> (98.124.180.42) 360ms
> 14 ae12.r02.sjc01.icn.netarch.akamai.com (23.207.232.40) 360ms ip4.gtt.net 
> (98.124.180.42) 356ms 356ms
> 15 ae4.r02.ord01.icn.netarch.akamai.com (23.32.63.26) 405ms 425ms 
> ae12.r02.sjc01.icn.netarch.akamai.com (23.207.232.40) 357ms
> 16 ae3.r01.lga01.icn.netarch.akamai.com (23.32.63.4) 425ms 
> ae4.r02.ord01.icn.netarch.akamai.com (23.32.63.26) 405ms 400ms
> 17 ae1.r02.lga01.ien.netarch.akamai.com (23.203.156.37) 426ms 426ms 
> ae3.r01.lga01.icn.netarch.akamai.com (23.32.63.4) 422ms
> 18 ae1.r02.lga01.ien.netarch.akamai.com (23.203.156.37) 423ms 0.0.0.0 
> (0.0.0.0) * ae1.r02.lga01.ien.netarch.akamai.com (23.203.156.37) 423ms
> 19 a23-1-35-132.deploy.static.akamaitechnologies.com (23.1.35.132) 226ms 
> 228ms 0.0.0.0 (0.0.0.0) *
>  
> Hurricane Electric Traceroute
> core2.bna1.he.net> traceroute 23.1.35.132 source 216.218.252.20
> Target
> 23.1.35.132
> Hop Start
> 1
> Hop End
> 30
> Hop
> Packet 1
> Packet 2
> Packet 3
> Hostname
> 1
> 5.469 ms
> 5.579 ms
> 5.586 ms
> 100ge6-2.core1.ind1.he.net (184.105.65.149)
> 2
> 11.324 ms
> 11.347 ms
> 11.391 ms
> 100ge0-33.core2.stl1.he.net (184.104.196.14)
> 3
> 16.556 ms
> 16.854 ms
> 16.982 ms
> 100ge0-68.core2.mci3.he.net (72.52.92.237)
> 4
> 16.800 ms
> 16.811 ms
> 16.930 ms
> 100ge4-1.core1.mci3.he.net (184.104.197.69)
> 5
> 27.761 ms
> 27.783 ms
> 27.788 ms
> 100ge7-2.core1.den1.he.net (184.104.195.213)
> 6
> 51.918 ms
> 50.625 ms
> 50.712 ms
> 100ge0-29.core2.sjc2.he.net (184.105.64.69)
> 7
> 50.842 ms
> 50.672 ms
> 50.647 ms
> 100ge16-1.core1.sjc2.he.net (184.104.192.213)
> 8
> 51.078 ms
> 80.874 ms
> 81.187 ms
> 100ge13-2.core1.sjc1.he.net (184.105.65.113)
> 9
> 52.429 ms
> 52.441 ms
> 52.506 ms
> vocus.gigabitethernet2-13.core1.sjc1.he.net (64.71.184.46)
> 10
> 202.821 ms
> 202.354 ms
> *
> be202.cor02.syd04.nsw.vocus.network (114.31.199.42)
> 21
> 463.994 ms
> 463.937 ms
> 464.130 ms
> 100ge0-33.core2.nyc4.he.net (184.105.81.62)
> 22
> 420.303 ms
> 420.423 ms
> 420.768 ms
> 100ge3-2.core1.bos1.he.net (184.105.64.54)
> 23
> 224.026 ms
> 224.042 ms
> 224.045 ms
> a23-1-35-132.deploy.static.akamaitechnologies.com (23.1.35.132)
>  
>  
> Eric Lester | Vice President of 

Re: [outages] Comcast / xfinity USA MA

[Brett Dikeman via Outages]

Yet another reminder that this list is for announcing outrages. Not for 
surveying, discussion, troubleshooting, etc. Take it to the discussion list.

To everyone else: please do not reply to him on-list.

> On Sep 7, 2021, at 9:38 AM, Jason Kuehl via Outages  
> wrote:
> 
> 
> Anyone else seeing issues with Comcast / Xfinity. Over the past hour, I have 
> gotten several tickets (17) around people not being access to VPN today. 
> Other people in the same locations on RCN/ATT work fine it seems to be only 
> Comcast / Xfinity users.
> 
> Anyone else seeing these odd reports?
> 
> -- 
> Sincerely,
>  
> Jason W Kuehl
> Cell 920-419-8983
> jason.w.ku...@gmail.com
> ___
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] Discord - Guilds/Servers offline

[Brett Dikeman via Outages]

It's more extensive than that; a local gaming group meeting this evening
had to use a different service because audio was so choppy it was useless.
Last week screen sharing was almost unusable.

On Tue, Apr 20, 2021 at 7:46 PM Ben Jackson via Outages 
wrote:

> My son just reported that all of the Discord servers he participates in
> are offline.
>
> Per discordstatus.com:
>
> Investigating - We are currently investigating guilds becoming
> unavailable. We believe this issue is related to a deploy and are actively
> investigating.
> Apr 20, 16:18 PDT
>
> ___
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] DNS resolution in Europe

[Brett Dikeman via Outages]

Yet another reminder to both people who make these posts and those who respond 
to them that this list is not for diagnostics, discussion, surveys, etc.

There is a discussion list for that type of post.

> On Mar 17, 2021, at 1:54 PM, Jason via Outages  wrote:
> 
> 
> We are getting alerted that URLs are not reachable from London, UK.
> 
> I see in /r/sysadmin a thread re: Google's DNS, but it might be larger than 
> Google to include Cloudflare and others.
> 
> Any confirmation here?
> 
> -- 
> #FarmerPower
> 
>   Jason Forst   |   Farmobile LLC 
> Director of Infrastructure 
> Direct: 913-766-4625 
> Office: 844-337-2255 x 725 
> Mobile: 913-481-7325
> This email, including any attachments, may contain confidential information. 
> If it has been sent to you in error, please reply to advise the sender of the 
> error and then immediately delete the email.
> 
> ___
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] [EXTERNAL] Re: Explosion in Nashville

[Brett Dikeman via Outages]

Yet another reminder that this is not a discussion list, and that there IS a 
discussion list. It baffles me that people on this list are so hellbent on not 
using the discuss list for discussion.

> On Dec 25, 2020, at 5:55 PM, Matt Hoppes via Outages  
> wrote:
> 
> 
> Yes. Obviously you need large enough reserves. 
> 
>>> On Dec 25, 2020, at 5:45 PM, Josh Luthman  
>>> wrote:
>>> 
>> 
>> Diesel works until it doesn't.  Remember the NY situation during Sandy?
>> 
>>> On Fri, Dec 25, 2020, 5:07 PM Matt Hoppes via Outages  
>>> wrote:
>>> Until it doesn’t. Diesel is always there as long as the tank is full. 
>>> 
> On Dec 25, 2020, at 5:02 PM, Stephens, Jamie A 
>  wrote:
> 
 
 It’s pretty common since NG normally flows
 
 From: Outages  on behalf of Matt Hoppes via 
 Outages 
 Sent: Friday, December 25, 2020 4:50:05 PM
 To: Brian Knight via Outages 
 Subject: [EXTERNAL] Re: [outages] Explosion in Nashville
  
 CAUTION: The e-mail below is from an external source. Please exercise 
 caution before opening attachments, clicking links, or following guidance.
 
 Why would you use natural gas for your backup power???  That just causes 
 issues like this. 
 
 > On Dec 25, 2020, at 4:32 PM, Brian Knight via Outages 
 >  wrote:
 > 
 ___
 Outages mailing list
 Outages@outages.org
 https://puck.nether.net/mailman/listinfo/outages
 
 The contents of this e-mail message and 
 any attachments are intended solely for the 
 addressee(s) and may contain confidential 
 and/or legally privileged information. If you
 are not the intended recipient of this message
 or if this message has been addressed to you 
 in error, please immediately alert the sender
 by reply e-mail and then delete this message 
 and any attachments. If you are not the 
 intended recipient, you are notified that 
 any use, dissemination, distribution, copying,
 or storage of this message or any attachment 
 is strictly prohibited.
>>> ___
>>> Outages mailing list
>>> Outages@outages.org
>>> https://puck.nether.net/mailman/listinfo/outages
> ___
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] calls to T-Mobile are fialing?

[Brett Dikeman via Outages]

A customer who uses an MNVO of T-Mobile is reporting busy signals, all
circuits busy errors, and dropping from LTE to HSPDA when trying to place
calls. They definitely seem to be having issues.

On Mon, Jun 15, 2020, 3:40 PM Izzy Goldstein - TeleGo via Outages <
outages@outages.org> wrote:

> i tried calling my own tmobile cell phone number thru many carriers, and
> call does not complete
>
> also getting complaints from customers that outgoing calls to cell phones
> are not completing.
>
> anyone else seeing any issues with calls completing to cellular phone
> numbers
>
> --
>
> Izzy Goldstein
>
> Chief Technology Officer
>
> Main: (212) 477-1000 x 2085 <(212)%20477-1000>
>
> Direct: (929) 477-2085
>
> Website: 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 
> ___
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] US West Coast Massive Tier 1 Backbone Issues

[Brett Dikeman via Outages]

Try the 60,000 foot view; the midwest is having a bad day as well, though
it sounds like a fiber cut is to blame.

https://www.reddit.com/r/sysadmin/comments/g5gyms/midwest_internet_outage/



On Tue, Apr 21, 2020 at 12:38 PM Jay Ashworth via Outages <
outages@outages.org> wrote:

> I was hoping somebody was going to climb up to 30,000 feet on this,
> because it sort of felt to me like it was pervasive as well. I encourage
> further analysis on this point, and apologize to anybody who would prefer
> that it be on the discussion list - I think it actually belongs here.
> 
>
> On April 21, 2020 11:58:30 AM EDT, Cary Wiedemann via Outages <
> outages@outages.org> wrote:
>>
>> Hey All,
>>
>> There's a few threads on this already, but they all call out specific
>> ISPs when this trouble isn't limited to any one last-mile provider.  Nearly
>> all tier 1 transit providers are experiencing loss on the US West Coast
>> today.  Some examples:
>>
>> Comcast/Level3 peering point in Seattle:
>> [image: image.png]
>>
>> Telia/AT in Seattle:
>> [image: image.png]
>>
>> Hurricane Electric/Cox in San Jose:
>> [image: image.png]
>>
>> And this isn't the half of it.  Very few tier 1 transit providers are
>> unaffected.
>>
>> So much for carrier redundancy!
>>
>> - Cary
>>
>>
>>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
> ___
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] San Francisco metro Cogent outage 3/26/20 4:40PM PDT - Ongoing

[Brett Dikeman via Outages]

This is not a discussion list. Take it to outages-discuss.

On *this* list, you post announcements of outages you're reasonably certain
about. *Nothing else.*

On Thu, Mar 26, 2020 at 10:39 PM Luke Rockwell via Outages <
outages@outages.org> wrote:

> My connection keeps flapping between Cogent and my backup connection on
> Zayo
>
> On Thu, Mar 26, 2020 at 7:11 PM Katz, Ethan via Outages <
> outages@outages.org> wrote:
>
>> I see my Lafayette, San Francisco, San Jose, and Sacramento offices
>> flapping.
>>
>>
>>
>> *Ethan Katz*
>>
>> AVP, Network Operations
>>
>> Technology
>>
>> 1250 S Capital of Texas Hwy | Bldg 2 Ste 600 | Austin, TX 78746
>> 
>>
>> P: 512.697.6631 | M: 559.999.9651 | ek...@nfp.com
>>
>>
>>
>> [image: cid:image002.png@01D1A782.5252CC00]
>>
>>
>>
>> *From:* Outages  *On Behalf Of *Luke
>> Rockwell via Outages
>> *Sent:* Thursday, March 26, 2020 7:32 PM
>> *To:* pkr...@unwiredltd.com
>> *Cc:* outages@outages.org
>> *Subject:* Re: [outages] San Francisco metro Cogent outage 3/26/20
>> 4:40PM PDT - Ongoing
>>
>>
>>
>> ATTENTION - EXTERNAL EMAIL - The sender of this email is EXTERNAL to our
>> email system. Do not click links or open attachments unless you recognize
>> the sender and know the content is safe. The Original Sender of this email
>> is *outages-boun...@outages.org *
>> --
>>
>> My office has a covad connection and it is offline
>>
>>
>>
>> On Thu, Mar 26, 2020 at 5:23 PM Peter Kranz via Outages <
>> outages@outages.org> wrote:
>>
>> Cogent ports in San Francisco and Oakland became black holes at ~4:40PM
>> PDT. They are currently only advertising 110 routes as their full tables in
>> that area.
>>
>>
>>
>> Peter Kranz
>> www.UnwiredLtd.com
>> 
>> Desk: 510-868-1614 x100
>> Mobile: 510-207-
>> pkr...@unwiredltd.com
>>
>>
>>
>> ___
>> Outages mailing list
>> Outages@outages.org
>> https://puck.nether.net/mailman/listinfo/outages
>> 
>>
>> --
>> This e-mail may contain information that is privileged, confidential or
>> protected under state or federal law. If you are not an intended recipient
>> of this email, please delete it, notify the sender immediately, and do not
>> copy, use or disseminate any information in the e-mail. Any tax advice in
>> this email may not be used to avoid any penalties imposed under U.S. tax
>> laws. E-mail sent to or from this e-mail address may be monitored, reviewed
>> and archived.
>> ___
>> Outages mailing list
>> Outages@outages.org
>> https://puck.nether.net/mailman/listinfo/outages
>>
> ___
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] Meraki routing issue

[Brett Dikeman via Outages]

Yet another reminder that this list is not for diagnostics,
troubleshooting, surveying, etc.

There is an outages-discuss mailing list for those things. This list is for
*announcements* of outages only.


On Wed, Jan 8, 2020 at 12:53 PM Erich Kaiser via Outages <
outages@outages.org> wrote:

> We are seeing strange routing issues to icmp.meraki.com most routes are
> going to australia, from several different source addresses.  Anyone else
> seeing an issue with this?
>
>
>
> ___
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] Google Down?

[Brett Dikeman via Outages]

*Yet another reminder* that this list is not for troubleshooting,
discussion, diagnostics, polling people if something is down, etc. *Take it
to the -discuss list.*

Also, it is worth noting that Mr. Hoppes has on *several* occasions pinged
this list to ask if various major internet sites are down, when they were
in fact not down.

On Tue, Dec 10, 2019 at 3:34 PM Ross Tajvar via Outages 
wrote:

> What region/ISP?
>
> On Tue, Dec 10, 2019, 3:32 PM Matt Hoppes via Outages 
> wrote:
>
>> As of 3:25pm Eastern we've lost access to all things Google -- Hangouts,
>> Youtube, Google Search.
>>
>> Even pinging google.com results in no response.
>> ___
>> Outages mailing list
>> Outages@outages.org
>> https://puck.nether.net/mailman/listinfo/outages
>>
> ___
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] Google Login Outage

[Brett Dikeman via Outages]

We don't actually need everyone to confirm or deny something from every
corner of the planet. This list is not for discussion or troubleshooting*.
As has been mentioned before recently, I might add, more than once.*



On Mon, Aug 19, 2019, 2:42 PM Ylan Muller via Outages 
wrote:

> Unable to sign in to a system that uses Google Oauth over on the west
> coast right now.
>
> On Mon, Aug 19, 2019 at 11:37 AM Shripal Daphtary via Outages <
> outages@outages.org> wrote:
>
>> confirmed NYC. no Admin login
>>
>>
>>
>> Shripal Daphtary
>> shripal.dapht...@pressone.net
>> D: 718.360.1222
>> C: 973.432.1440
>> F: 718.360.1222
>>
>>
>>
>>
>> On Mon, Aug 19, 2019 at 2:35 PM Biggers, Jeremy via Outages <
>> outages@outages.org> wrote:
>>
>>> Google login down for us. No one can log in to Chromebooks or Admin
>>> Console. For sure know it's at least state-wide in Alabama, but I would
>>> imagine it's all of US.
>>>
>>> --
>>> Jeremy Biggers
>>> Network Administrator
>>> Monroe County Public Schools
>>> 251-743-6035
>>> jbigg...@monroe.k12.al.us 
>>>
>>>
>>> ___
>>> Outages mailing list
>>> Outages@outages.org
>>> https://puck.nether.net/mailman/listinfo/outages
>>>
>> ___
>> Outages mailing list
>> Outages@outages.org
>> https://puck.nether.net/mailman/listinfo/outages
>>
>
>
> --
>
> Ylan Muller | IT Administrator
>
> Outreach.io
>
> ___
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages