Timeout connection - page 3. | Bitcointalksearch.org

Janation

hero member

Activity: 1722

Merit: 528

Quote from: Miiike on April 21, 2017, 03:34:32 PM

Quote from: Landak on April 21, 2017, 03:18:09 PM

Quote from: Miiike on April 21, 2017, 03:14:12 PM

Works fine for Indonesia, although it's a little bit slow. Better than no connection at all, though. If problem occurs again, I'll inform you via edit.

Not at all, some ISP on indonesia still can't access bitcointalk.org like ISP from PT. Telkom included Tekomsel. currently now i login using vpn from singapore

Uhh... But I use telkom's service too. I accessed this forum finely. Go try to turn off the vpn, maybe you can't access it via indihome few mins ago before theymos apply the newest solution

I have the opposite. I can't access the site but when I used the vpn it worked fine, I thought the server is down but I think now someone attacked. It's ok now even without VPN, by the way I'm from the Philippines.

Miiike

legendary

Activity: 2030

Merit: 1059

Wait... What?

Quote from: Landak on April 21, 2017, 03:18:09 PM

Quote from: Miiike on April 21, 2017, 03:14:12 PM

Works fine for Indonesia, although it's a little bit slow. Better than no connection at all, though. If problem occurs again, I'll inform you via edit.

Not at all, some ISP on indonesia still can't access bitcointalk.org like ISP from PT. Telkom included Tekomsel. currently now i login using vpn from singapore

Uhh... But I use telkom's service too. I accessed this forum finely. Go try to turn off the vpn, maybe you can't access it via indihome few mins ago before theymos apply the newest solution

Landak

hero member

Activity: 1386

Merit: 503

Quote from: Miiike on April 21, 2017, 03:14:12 PM

Works fine for Indonesia, although it's a little bit slow. Better than no connection at all, though. If problem occurs again, I'll inform you via edit.

Not at all, some ISP on indonesia still can't access bitcointalk.org like ISP from PT. Telkom included Tekomsel. currently now i login using vpn from singapore

Miiike

legendary

Activity: 2030

Merit: 1059

Wait... What?

Works fine for Indonesia, although it's a little bit slow. Better than no connection at all, though. If problem occurs again, I'll inform you via edit.

Edit 1: (09.44 forum time) down again for Indonesia, but I figure that anyone know that already because others from different countries are experiencing the same.

Landy1264

member

Activity: 115

Merit: 10

Tip: 1JBSwRgm7iMzc7uyhnJdxH7hSECdJkdMoj

Works for now to germany.

If it's getting worse again, i will post there ->https://redd.it/66os8f!

theymos

administrator

Activity: 5222

Merit: 13032

After I changed the IP, it happened again in about 30 minutes, which makes me think that it is in fact a DDoS attack which is getting clogged up somewhere between the interface between the US and the rest of the world.

Now there are several reverse proxies sitting in front of the server, each with its own IP address. How is this working for everyone? I can increase the number of proxies arbitrarily if necessary.

Blackshadow007

sr. member

Activity: 787

Merit: 276

Currency Xchanger™

Quote from: theymos on April 21, 2017, 10:56:19 AM

It's not a normal DDoS. It seems that certain places on Earth lost connectivity, while others work fine. So it must be a problem somewhere upstream of the forum's server.

If you still have problems, where are you and what ISP are you using? Post a traceroute if possible.

Its fast for me now ..

Landy1264

member

Activity: 115

Merit: 10

Tip: 1JBSwRgm7iMzc7uyhnJdxH7hSECdJkdMoj

Down/slow to Germany again!

Code:

C:\>tracert bitcointalk.org

Routenverfolgung zu bitcointalk.org [52.55.72.170]
über maximal 30 Hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     *        *        *     Zeitüberschreitung der Anforderung.
  3    10 ms     9 ms    10 ms  ip5886ba1e.dynamic.kabel-deutschland.de [88.134.
186.30]
  4     9 ms    11 ms    11 ms  ip5886bb1d.dynamic.kabel-deutschland.de [88.134.
187.29]
  5    14 ms    14 ms    13 ms  ip5886eb2e.static.kabel-deutschland.de [88.134.2
35.46]
  6    14 ms    14 ms    22 ms  ip5886ebdf.static.kabel-deutschland.de [88.134.2
35.223]
  7    12 ms    12 ms    13 ms  ae8-100-xcr1.hac.cw.net [195.10.62.5]
  8    95 ms    94 ms    95 ms  ae5-xcr1.ham.cw.net [195.2.24.181]
  9    98 ms    97 ms    96 ms  ae4-xcr2.amd.cw.net [195.2.9.38]
 10    93 ms    94 ms    94 ms  ae0-xcr1.ltw.cw.net [195.2.24.121]
 11    97 ms    99 ms    96 ms  ae5-xcr1.slo.cw.net [195.2.24.33]
 12    95 ms    95 ms    93 ms  ae2-xcr1.nyh.cw.net [195.2.28.169]
 13    94 ms    96 ms    96 ms  ae13-xcr2.nyk.cw.net [195.2.25.69]
 14    96 ms    96 ms    97 ms  52.95.216.78
 15     *        *        *     Zeitüberschreitung der Anforderung.
 16     *        *        *     Zeitüberschreitung der Anforderung.
 17    95 ms   100 ms   103 ms  52.93.4.197
 18    98 ms    97 ms    98 ms  52.93.4.90
 19   110 ms   107 ms    98 ms  52.93.4.99
 20    95 ms    94 ms    94 ms  52.93.4.28
 21   102 ms   103 ms   104 ms  54.239.41.220
 22     *        *        *     Zeitüberschreitung der Anforderung.
 23     *        *        *     Zeitüberschreitung der Anforderung.
 24   121 ms   122 ms   127 ms  54.239.110.137
 25   102 ms   100 ms   101 ms  54.239.111.57
 26   112 ms   104 ms   101 ms  205.251.244.216
 27     *        *        *     Zeitüberschreitung der Anforderung.
 28     *        *        *     Zeitüberschreitung der Anforderung.
 29     *        *        *     Zeitüberschreitung der Anforderung.
 30     *        *        *     Zeitüberschreitung der Anforderung.

Ablaufverfolgung beendet.

digaran

copper member

Activity: 1330

Merit: 899

🖤😏

Looks like some heavy DOS going on, long live Tor, death to attackers, good to see people from Iran lolz.

Where should we donate for some stronger servers? because after all we're the ones using this forum and it's more fair if we could help, administrator can't spend while all we do is shitposting without any contribution to the cause.

SFR10

legendary

Activity: 2968

Merit: 3406

Crypto Swap Exchange

Quote from: theymos on April 21, 2017, 11:45:15 AM

Changing the forum's IP address seems to have fixed it.
~Snipped~

Everything was restored (to the normal state) for an hour but it started to play games once again (in case you're changing something in the back-end):
Location: Iran

Code:

Tracing route to bitcointalk.org [52.55.72.170]
over a maximum of 30 hops:

  1     2 ms     3 ms    14 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    87 ms    72 ms   192 ms  10.133.55.69
  4    74 ms    77 ms    97 ms  10.133.214.90
  5    78 ms    82 ms    73 ms  100.127.255.10
  6   195 ms   237 ms   217 ms  10.21.251.54
  7     *        *        *     Request timed out.
  8   192 ms   193 ms   202 ms  ae5.istanbul1.ist.seabone.net [93.186.132.212]
  9   287 ms   277 ms   302 ms  racc.newark11.new.seabone.net [195.22.216.227]
 10   306 ms   292 ms   312 ms  amazon.ashburn2.ash.seabone.net [195.22.206.29]
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15   347 ms   292 ms   317 ms  54.239.110.133
 16   337 ms   268 ms   287 ms  54.239.108.127
 17   273 ms   287 ms   287 ms  205.251.245.174
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

mindrust

legendary

Activity: 3276

Merit: 2442

Code:

traceroute to bitcointalk.org (52.55.72.170), 30 hops max, 60 byte packets
	
1	 	 	 	*	*	*		
2	core21.fsn1.hetzner.com	213.239.229.129	de	0.233 ms	0.250 ms	 
core22.fsn1.hetzner.com	213.239.229.133	de	0.235 ms		
3	core1.fra.hetzner.com	213.239.245.177	de	4.875 ms	4.881 ms	4.875 ms		
4	 	 	 	*	*	*		
5	ae-1.r24.frnkge08.de.bb.gin.ntt.net	129.250.6.206	us	6.371 ms	6.370 ms	6.334 ms		
6	ae-4.r25.nycmny01.us.bb.gin.ntt.net	129.250.2.4	us	87.382 ms	88.147 ms	88.895 ms		
7	ae-2.r07.nycmny01.us.bb.gin.ntt.net	129.250.3.98	us	87.248 ms	 	 
ae-2.r08.nycmny01.us.bb.gin.ntt.net	129.250.6.209	us	86.423 ms	87.411 ms			
8	ae-7.amazon.nycmny01.us.bb.gin.ntt.net	129.250.201.122	us	89.329 ms	88.437 ms	 
ae-6.amazon.nycmny01.us.bb.gin.ntt.net	129.250.201.118	us	85.422 ms		
9	 	 	 	*	*	*		
10	 	 	 	*	*	*		
11	 	 	 	*	*	*		
12	 	 	 	*	*	*		
13	 	 	 	*	*	*
No reply for 5 hops. Assuming we reached firewall.

It was fine 30 mins ago or so but it started to come and go again. TOR is also suffering at the moment. Trying to connect from Turkey. It's been like this since morning. Also check this out:

Code:

--- PING bitcointalk.org (52.55.72.170) 56(84) bytes of data. ---


--- bitcointalk.org ping statistics ---

					
packets transmitted 	9
received 	0
packet loss 	100 %
time 	8004 ms

Darkus91

newbie

Activity: 6

Merit: 0

Quote from: theymos on April 21, 2017, 10:56:19 AM

It's not a normal DDoS. It seems that certain places on Earth lost connectivity, while others work fine. So it must be a problem somewhere upstream of the forum's server.

If you still have problems, where are you and what ISP are you using? Post a traceroute if possible.

Here is the traceroute:

Code:

traceroute to 52.55.72.170 (52.55.72.170), 30 hops max, 60 byte packets
 1  praha-4d-c1-vl55.masterinter.net (77.93.199.253)  121.391 ms  121.484 ms  121.573 ms
 2  vl1387.cr3.r1-8.dc1.4d.prg.masterinter.net (83.167.254.150)  0.195 ms  0.205 ms  0.307 ms
 3  vl1389.cr2.c16.127.cecolo.prg.masterinter.net (83.167.254.146)  0.329 ms vl1388.cr2.c16.127.cecolo.prg.masterinter.net (83.167.254.148)  0.432 ms  0.425 ms
 4  prag-b3-link.telia.net (62.115.147.38)  0.265 ms  0.395 ms  0.386 ms
 5  prag-bb1-link.telia.net (213.155.137.18)  0.329 ms win-bb2-link.telia.net (213.155.131.68)  6.466 ms win-bb2-link.telia.net (213.155.132.182)  5.777 ms
 6  ffm-bb4-link.telia.net (62.115.134.214)  18.645 ms ffm-bb3-link.telia.net (62.115.113.140)  7.507 ms ffm-bb4-link.telia.net (213.155.133.56)  18.665 ms
 7  ash-bb4-link.telia.net (62.115.137.115)  103.428 ms ffm-b1-link.telia.net (62.115.137.167)  19.242 ms ash-bb3-link.telia.net (62.115.139.41)  117.525 ms
 8  ash-b1-link.telia.net (213.155.136.39)  110.901 ms ash-b1-link.telia.net (62.115.143.3)  110.640 ms ash-b1-link.telia.net (213.155.136.39)  110.655 ms
 9  vadata-ic-157230-ash-bb1.c.telia.net (213.248.94.50)  110.127 ms prs-bb3-link.telia.net (62.115.123.19)  118.215 ms  118.318 ms
10  * * *
11  * ash-bb3-link.telia.net (62.115.137.88)  123.368 ms ash-b1-link.telia.net (80.91.248.159)  118.699 ms
12  ash-b1-link.telia.net (80.91.248.157)  116.284 ms * *
13  * * vadata-ic-157231-ash-bb1.c.telia.net (62.115.9.62)  123.648 ms
14  * * *
15  * * *
16  * * *
17  54.239.110.167 (54.239.110.167)  146.978 ms * *
18  * * *
19  * 54.239.111.63 (54.239.111.63)  117.169 ms *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

I still can't normal connect to the site, sometimes the website loads and then boom next page it doesn't open.

qory

hero member

Activity: 1722

Merit: 508

Can't reach bitcointalk with "Telkom Indonesia " , 100% connection lost, this ISP is owned by government. But there is no problem when accessing with cellular data.

isoneguy

hero member

Activity: 518

Merit: 501

must be a rolling dns update

ShitSticks

newbie

Activity: 34

Merit: 0

From the Uk, up and down.

Code:

Tracing route to bitcointalk.org [52.55.72.170]
over a maximum of 30 hops:

  1     3 ms     3 ms     2 ms  SkyRouter.Home [192.168.0.1]
  2     *        *        *     Request timed out.
  3    28 ms    28 ms    31 ms  be437.pr2.thlon.isp.sky.com [89.200.131.244]
  4     *        *       29 ms  lag-102.ear1.London1.Level3.net [212.113.9.141]
  5     *        *        *     Request timed out.
  6   130 ms   130 ms   151 ms  4.16.98.206
  7   140 ms   139 ms   139 ms  176.32.125.150
  8   135 ms   133 ms   133 ms  176.32.125.157
  9   139 ms   137 ms   134 ms  54.239.43.200
 10   136 ms   133 ms   137 ms  54.239.43.98
 11     *        *        *     Request timed out.
 12   198 ms     *      213 ms  54.239.110.149
 13   135 ms     *      224 ms  54.239.108.127
 14   310 ms   232 ms   190 ms  205.251.245.189
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

poptok1

hero member

Activity: 1638

Merit: 756

Bobby Fischer was right

Poland was affected as well. OK now.

Code:

traceroute to bitcointalk.org (52.55.72.170), 30 hops max, 38 byte packets
 1  pc2 (192.168.1.1)  3.159 ms  2.607 ms  2.593 ms
 2  lodz-bng2.tpnet.pl (80.50.18.98)  58.775 ms  68.774 ms  63.165 ms
 3  lodz-r1.tpnet.pl (80.50.18.97)  23.640 ms  23.381 ms  21.411 ms
 4  war-r1.tpnet.pl (194.204.175.197)  24.399 ms  24.663 ms  25.738 ms
 5  war-b2-link.telia.net (213.248.89.85)  58.211 ms  56.641 ms  60.672 ms
 6  hbg-bb4-link.telia.net (213.155.133.94)  61.040 ms  hbg-bb1-link.telia.net (213.155.135.16)  61.512 ms  hbg-bb1-link.telia.net (80.91.245.238)  59.827 ms
 7  ldn-bb2-link.telia.net (62.115.112.40)  71.678 ms  ldn-bb3-link.telia.net (62.115.115.236)  82.738 ms  ldn-bb3-link.telia.net (213.155.137.105)  82.368 ms
 8  ash-bb3-link.telia.net (62.115.124.128)  143.409 ms  ash-bb4-link.telia.net (62.115.116.68)  135.028 ms  ash-bb4-link.telia.net (80.91.251.207)  132.427 ms
 9  ash-b1-link.telia.net (80.91.248.161)  138.242 ms  136.343 ms  ash-b1-link.telia.net (213.155.136.39)  136.442 ms
10  vadata-ic-157229-ash-bb1.c.telia.net (80.239.193.210)  131.128 ms  vadata-ic-157233-ash-bb1.c.telia.net (62.115.9.70)  137.398 ms  vadata-ic-157234-ash-bb1.c.telia.net (62.115.9.74)  138.205 ms
11  *  *  *
12  *  *  *
13  54.239.110.187 (54.239.110.187)  152.063 ms  54.239.110.185 (54.239.110.185)  213.459 ms  54.239.110.145 (54.239.110.145)  153.318 ms
14  54.239.109.41 (54.239.109.41)  138.818 ms  54.239.111.49 (54.239.111.49)  135.714 ms  54.239.110.139 (54.239.110.139)  155.214 ms
15  205.251.245.189 (205.251.245.189)  137.731 ms  54.239.108.127 (54.239.108.127)  139.252 ms  205.251.245.172 (205.251.245.172)  142.489 ms
16  *  *  *
17  *  *  *
18  *  *  *
19  *  *  *
20  *  *  *
21  *  *  *
22  *  *  *
23  *  *  *
24  *  *  *
25  *  *  *
26  *  *  *
27  *  *  *
28  *  *  *
29  *  *  *
30  *  *  *

Edit: Down again, completely inaccessible. (edited through VPN)

theymos

administrator

Activity: 5222

Merit: 13032

Changing the forum's IP address seems to have fixed it.

What was happening was that IP packets bound for the forum were being dropped or misrouted somewhere between certain ISPs/regions and the forum. It looks like about half of the world was affected. I only received one useful traceroute during the incident, and this showed that the packets were being dropped at or immediately after gtt.net, but I'd need more samples to draw any strong conclusions from that. (And it's too late to send me useful traceroutes now.)

I'll try to figure out more about what happened.

LFC_Bitcoin

legendary

Activity: 3556

Merit: 9709

#1 VIP Crypto Casino

Working fine here in the UK. I tried earlier & got a time out but fine now.

Dammitt

hero member

Activity: 882

Merit: 507

There is no problem at the moment, even when I use any vpn service, I was having trouble connecting in the same way and it is obvious that it is too slow. I hope this situation has improved.

Money Maker Shaker

member

Activity: 74

Merit: 10

Quote from: theymos on April 21, 2017, 10:56:19 AM

If you still have problems, where are you and what ISP are you using? Post a traceroute if possible.

Iran and I thought they have finally banned bitcoin(talk) LOL
p.s. posting from a proxy (Sao Paulo, BR)

The trace is from my own IP:

Code:

Tracing route to bitcointalk.org [52.55.72.170]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *       20 ms  217.218.189.198
  6     *        *       21 ms  10.201.42.164
  7    22 ms    21 ms    23 ms  10.201.42.98
  8    24 ms    21 ms    22 ms  10.201.177.21
  9   121 ms   119 ms   117 ms  85.132.90.241
 10     *        *        *     Request timed out.
 11     *        *      119 ms  ae18-xcr1.fri.cw.net [213.38.245.109]
 12   200 ms   199 ms   195 ms  ae14-xcr1.ptl.cw.net [195.2.31.234]
 13   197 ms   202 ms     *     et-7-1-0-xcr1.nyh.cw.net [195.2.24.241]
 14     *        *      192 ms  ae13-xcr2.nyk.cw.net [195.2.25.69]
 15   189 ms   191 ms   188 ms  52.95.216.78
 16   197 ms   203 ms   199 ms  52.93.4.75
 17   191 ms   192 ms   191 ms  52.93.4.36
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22   206 ms   202 ms   203 ms  54.239.111.63
 23   197 ms   199 ms   199 ms  205.251.244.216
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

Topic: Timeout connection - page 3. (Read 3685 times)