Currently regional. Inaccessible from US west coast; seeing responses from web requests from machines on east coast (nyc)
Twitter experiencing outages
41–50 of 102 posts
Re: Twitter experiencing outages
#42A bit suspicious right before the US election, maybe it's under attack. We'll find out soon enough.
Right after WikiLeaks released the last batch of DNC/Podesta/Clinton emails, the most damning ones... Hmm...
Release a huge pile of emails no one will have time to vet, the day before an election, after millions have already voted. A fiendishly diabolical plan, Mr. Assange!
Check, mate, and match!
Re: Twitter experiencing outages
#43Outages list [1] says routes aren't being announced via BGP anymore [2] [1]: https://puck.nether.net/mailman/listinfo/outages [2]: https://puck.nether.net/pipermail/outages/2016-November/0098...
Yep, i'm no expert, but a BGP looking glass seems to suggest that all of the best paths (chosen by AS pathlength?) are not being advertised to peers... But some routes are being advertised? Idk
Router: Palo Alto, CA - US
Command: show ip bgp 104.244.42.193
BGP routing table entry for 104.244.42.0/24
Versions:
Process bRIB/RIB SendTblVer
Speaker 261897778 261897778
Last Modified: Nov 7 06:11:36.675 for 00:02:37
Paths: (4 available, best #3)
Advertised to update-groups (with more than one peer):
0.2 0.3 0.6 0.7
Advertised to peers (in unique update groups):
129.250.47.126 129.250.9.146 128.242.180.62 80.150.168.193
128.241.2.58
Path #1: Received by speaker 0
Not advertised to any peer
13414 13414
116.51.31.10 (metric 14530) from 129.250.0.18 (129.250.0.18)
Origin IGP, localpref 120, valid, confed-internal
Received Path ID 0, Local Path ID 0, version 0
Community: 2914:370 2914:1405 2914:2406 2914:3400 65400:4134 65420:4134 65460:4134
Path #2: Received by speaker 0
Not advertised to any peer
13414 13414
62.73.183.110 (metric 28640) from 129.250.0.30 (129.250.0.30)
Origin IGP, localpref 120, valid, confed-internal
Received Path ID 0, Local Path ID 0, version 0
Community: 2914:370 2914:1204 2914:2205 2914:3200 65400:4134 65420:4134 65460:4134
Path #3: Received by speaker 0
Advertised to update-groups (with more than one peer):
0.2 0.3 0.6 0.7
Advertised to peers (in unique update groups):
129.250.47.126 129.250.9.146 128.242.180.62 80.150.168.193
128.241.2.58
13414 13414
129.250.195.210 (metric 7029) from 129.250.0.115 (129.250.0.167)
Origin IGP, localpref 120, valid, confed-internal, best, group-best
Received Path ID 0, Local Path ID 1, version 261897778
Community: 2914:370 2914:1007 2914:2000 2914:3000 65400:4134 65420:4134 65460:4134
Originator: 129.250.0.167, Cluster list: 0.0.0.6
Path #4: Received by speaker 0
Not advertised to any peer
13414 13414
129.250.195.210 (metric 7029) from 129.250.0.116 (129.250.0.167)
Origin IGP, localpref 120, valid, confed-internal
Received Path ID 0, Local Path ID 0, version 0
Community: 2914:370 2914:1007 2914:2000 2914:3000 65400:4134 65420:4134 65460:4134
Originator: 129.250.0.167, Cluster list: 0.0.0.6
Re: Twitter experiencing outages
#44Wikileaks and 4chan also experiencing issues. Looks like a DDoS possibly connected to DNCleaks2 released by Wikileaks a few hours ago.
They all seem back up now.
Re: Twitter experiencing outages
#45Re: Twitter experiencing outages
#46From their Facebook, "WikiLeaks servers are currently under a massive targeted DDoS attack"
Re: Twitter experiencing outages
#47"works on my machine"
although, http://downforeveryoneorjustme.com/ reports it as down
Edit: I'm from Romania
Re: Twitter experiencing outages
#48It's back now. Panic over.
Re: Twitter experiencing outages
#49It's back already. Calm down.
Re: Twitter experiencing outages
#50Wikileaks is down also, coincidence?
I get a 502 for Wikileaks but consensus is there's no BGP announcements for twitter. Possible it's the same attacker but they seem to be two different attacks.