Re: [outages] Optus/Akamai
- On Nov 9, 2023, at 2:31 PM, Ross Tajvar via Outages outages@outages.org wrote: Hi, > Surely it's better to drop some routes than to drop the whole session. Not necessarily. If part of your IBGP feed includes 10/8 (common in datacenters), you may end up in a situation where it's better to disable a leaking peer. Imagine a Trident 3 box in a spine layer, with 32 northbound peers and 32 southbound peers. Northbound you'll receive a few hundred routes, including 10/8. Southbound, you'll receive a few hundred host subnets and perhaps some any-cast /32s. You'll aggregate the host subnets northbound. If one of those northbound peers leaks a full table, you run the risk of losing some of your host subnets, or perhaps important any-cast routes. I would prefer to lose the offending peer over risking host routes, primarily because shutting down the peer is deterministic while you have no control over which routes are lost. Thanks, Sabri ___ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Re: [outages] T-Mobile Down Nationwide?
Hi, Second that. My wife's phone is showing "SOS" (i.e., no cellular connection), while my phone is connected to T-Mo, but no incoming or outgoing calls, or internet. Thanks, Sabri - On Feb 13, 2023, at 8:13 PM, outages wrote: > Can confirm in both socal and NorCal. Also appears to be reported in at least > one news outlet so far > [ > https://www.wboy.com/news/national/users-report-t-mobile-allegedly-experiencing-nationwide-outages/ > | > https://www.wboy.com/news/national/users-report-t-mobile-allegedly-experiencing-nationwide-outages/ > ] > On Mon, Feb 13, 2023, 8:07 PM Benjamin Monjay via Outages < [ > mailto:outages@outages.org | outages@outages.org ] > wrote: >> Seeing a lot of reports on Twitter, FB and Reddit. My personal phone is out >> as >> well. Showing no service at all. >> Interestingly enough, my Ziply Fiber went down at the same time as well but >> came >> up about 5 minutes later. >> ___ >> Outages mailing list >> [ mailto:Outages@outages.org | Outages@outages.org ] >> [ https://puck.nether.net/mailman/listinfo/outages | >> 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] cisco.com down?
Hi, It seems to be an issue with their HTTPS service: [sabri@bofh ~]$ mtr 173.37.145.84 [sabri@bofh ~]$ ping www.cisco.com PING origin-www.cisco.com (173.37.145.84): 56 data bytes 64 bytes from 173.37.145.84: icmp_seq=0 ttl=237 time=60.483 ms ^C --- origin-www.cisco.com ping statistics --- 1 packets transmitted, 1 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 60.483/60.483/60.483/0.000 ms [sabri@bofh ~]$ telnet www.cisco.com 443 Trying 173.37.145.84... ^C [sabri@bofh ~]$ telnet www.cisco.com 80 Trying 173.37.145.84... Connected to origin-www.cisco.com. Escape character is '^]'. ^] telnet> quit Connection closed. [sabri@bofh ~]$ It pings, port 80 works, port 443 does not. Thanks, Sabri - On Mar 22, 2022, at 1:54 PM, outages outages@outages.org wrote: > Is their website down? > -- > Bryan Fields > > 727-409-1194 - Voice > http://bryanfields.net > ___ > 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] Vocus routing US Salesforce.com traffic through Australia?
Hi, That's interesting. I did a traceroute from behind HE: [sabri@dora ~]$ traceroute 23.1.35.132 traceroute to 23.1.35.132 (23.1.35.132), 30 hops max, 60 byte packets 1 ge-0-0-1-unit-2.rtr1.fremont1.dc.cluecentral.net (195.16.84.1) 0.770 ms 0.690 ms 0.953 ms 2 ip-87-249.members.virt-ix.net (195.16.87.249) 25.145 ms 25.173 ms 25.458 ms 3 103.144.176.65 (103.144.176.65) 25.431 ms 25.431 ms 25.399 ms 4 v710.core4.fmt2.he.net (216.218.132.13) 36.449 ms 25.415 ms 25.809 ms 5 100ge10-1.core1.sjc1.he.net (184.105.80.193) 25.804 ms 25.795 ms 26.049 ms 6 vocus.gigabitethernet2-13.core1.sjc1.he.net (64.71.184.46) 26.331 ms 24.090 ms * 7 be100.bdr04.sjc01.ca.us.vocus.network (114.31.199.33) 252.448 ms be202.cor02.syd04.nsw.vocus.network (114.31.199.42) 248.817 ms 249.374 ms 8 be100.bdr04.syd03.nsw.vocus.network (114.31.192.45) 249.358 ms be203.cor01.syd11.nsw.vocus.network (114.31.199.40) 252.469 ms be100.bdr04.syd03.nsw.vocus.network (114.31.192.45) 249.286 ms 9 be101.bdr04.syd03.nsw.vocus.network (114.31.192.47) 252.577 ms * 252.879 ms 10 * * * 11 * a23-1-240-227.deploy.static.akamaitechnologies.com (23.1.240.227) 267.015 ms 266.998 ms 12 * static-73.173.255.49.in-addr.VOCUS.net.au (49.255.173.73) 262.371 ms * 13 be114.cor02.syd04.nsw.vocus.network (114.31.192.44) 340.616 ms static-73.173.255.49.in-addr.VOCUS.net.au (49.255.173.73) 253.192 ms be114.cor02.syd04.nsw.vocus.network (114.31.192.44) 340.815 ms 14 be114.cor02.syd04.nsw.vocus.network (114.31.192.44) 343.393 ms be114.cor01.syd11.nsw.vocus.network (114.31.192.46) 343.116 ms * 15 * * * 16 * * * 17 be201.bdr01.sin01.sin.vocus.network (114.31.206.51) 349.315 ms 357.906 ms 358.658 ms 18 80.81.65.217 (80.81.65.217) 364.537 ms 353.187 ms be201.bdr01.sin01.sin.vocus.network (114.31.206.51) 352.445 ms 19 ae9.0.cjr01.mrs002.flagtel.com (62.216.129.182) 485.064 ms 484.690 ms 80.81.65.217 (80.81.65.217) 350.032 ms 20 62.216.128.129 (62.216.128.129) 502.377 ms ae9.0.cjr01.mrs002.flagtel.com (62.216.129.182) 487.969 ms 487.956 ms 21 * * 62.216.128.129 (62.216.128.129) 500.875 ms 22 * a23-1-35-132.deploy.static.akamaitechnologies.com (23.1.35.132) 293.983 ms 293.992 ms The supernet 23.0.0.0/12 is owned by Akamai, who announces the more specific /24 to Vocus: 23.1.35.0/24 *[BGP/170] 2d 16:10:52, localpref 100 AS path: 53356 6939 4826 20940 33905 I, validation-state: unverified > to 195.16.87.249 via ge-0/0/6.0 [BGP/170] 2w2d 00:35:09, localpref 100 AS path: 136620 60011 3356 4826 20940 33905 I, validation-state: unverified > to 195.16.87.241 via ge-0/0/7.0 To me this looks like Vocus is accidentally leaking it to HE. Thanks, Sabri - On Sep 8, 2021, at 2:19 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
