Author

Topic: Timeout connection (Read 3685 times)

hero member
Activity: 1722
Merit: 508
April 24, 2017, 10:26:08 AM
#82
It has been like all the past week i tried to visit the forum but always the same thing, or sometimes i started to read all going good, go to the next page and boom, again no connection

Got Same problem here

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

  1     1 ms     1 ms     1 ms  1.1.168.192.in-addr.arpa [192.168.1.1]
  2     5 ms     4 ms     5 ms  180.253.48.1
  3     5 ms     4 ms     4 ms  149.0.160.125.in-addr.arpa [125.160.0.149]
  4     4 ms     5 ms     5 ms  180.252.3.249
  5    30 ms    35 ms    36 ms  46.193.240.180.in-addr.arpa [180.240.193.46]
  6    32 ms    31 ms    31 ms  45.193.240.180.in-addr.arpa [180.240.193.45]
  7   250 ms   267 ms   250 ms  58.192.240.180.in-addr.arpa [180.240.192.58]
  8   256 ms   257 ms   256 ms  equinix02-iad2.amazon.com [206.126.236.35]
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11   273 ms   261 ms   268 ms  169.110.239.54.in-addr.arpa [54.239.110.169]
 12   251 ms   252 ms   258 ms  195.108.239.54.in-addr.arpa [54.239.108.195]
 13   258 ms   256 ms   256 ms  174.245.251.205.in-addr.arpa [205.251.245.174]
 14     *        *        *     Request timed out.
 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     *
full member
Activity: 187
Merit: 100
April 24, 2017, 09:56:26 AM
#81
It has been like all the past week i tried to visit the forum but always the same thing, or sometimes i started to read all going good, go to the next page and boom, again no connection
sr. member
Activity: 448
Merit: 252
April 23, 2017, 09:20:01 PM
#80
Runs fine now - but the last days was horrorble.
sr. member
Activity: 343
Merit: 252
April 23, 2017, 03:29:06 PM
#79
From the Netherlands, GMT+1:


Yesterday and today during day-break time, site wasn't reachable.
Also both yesterday and today, connection was fine in the evening.
legendary
Activity: 3486
Merit: 2287
Top Crypto Casino
April 22, 2017, 02:52:04 PM
#78
Nice to be back! The side wasn't reachable the whole day for me but here we go again  Cool
hero member
Activity: 1442
Merit: 578
April 22, 2017, 02:42:28 PM
#77
How's it working for everyone now? I changed some stuff.

(It's difficult for me to test this because I don't have access to any machines which are affected by the issue...)

From Italy now is working fine! It's fast and no more connection problems.

I will report again if problems come back.

Thanks for your work.
hero member
Activity: 1442
Merit: 629
Vires in Numeris
April 22, 2017, 02:38:27 PM
#76
Sometimes works fine, but some minutes later it's slow again like in the afternoon. (But works, more or less, at least).
Browser complains about DNS problem. I haven't amended the neccessary modifications to the IP table, because I have no access now.
There were only 2 seconds between the 1st and the 2nd trace below:
Code:
>tracert bitcointalk.org
Unable to resolve target system name bitcointalk.org.

>tracert bitcointalk.org

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

  1     2 ms     2 ms     1 ms  -----------------------------
  2    20 ms    20 ms    18 ms  lo1.meroasr0-debrecen.net.telekom.hu [145.236.238.12]
  3    24 ms    24 ms    25 ms  81.183.3.4
  4    23 ms    22 ms    22 ms  81.183.3.4
  5    22 ms    23 ms    22 ms  81.183.3.145
  6    41 ms    41 ms    39 ms  80.157.202.125
  7    38 ms    38 ms    38 ms  ae-9.r01.vienat01.at.bb.gin.ntt.net [129.250.66.125]
  8    39 ms    39 ms    38 ms  ae-1.r20.frnkge04.de.bb.gin.ntt.net [129.250.2.77]
  9   136 ms   135 ms   134 ms  ae-8.r22.asbnva02.us.bb.gin.ntt.net [129.250.4.96]
 10   135 ms   135 ms   136 ms  ae-7.r06.asbnva02.us.bb.gin.ntt.net [129.250.2.121]
 11   134 ms   133 ms   133 ms  ae-2.amazon.asbnva02.us.bb.gin.ntt.net [168.143.228.38]
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14   153 ms   157 ms   146 ms  54.239.110.183
 15   132 ms   132 ms   134 ms  54.239.108.161
 16   134 ms   139 ms   133 ms  205.251.245.174
 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.

Trace complete.
Had a similar trace 10 minutes before, the bitcointalk.org's IP was the following then:
Code:
Tracing route to bitcointalk.org [34.202.40.180]
Both IP's are mentioned in Theymos's IP table.
Reading on the forum is nearly OK, but posting or editing posts is a challenge, still
hero member
Activity: 1498
Merit: 596
April 22, 2017, 01:17:40 PM
#75
I was also getting same problem to access bitcointalk.
But it seems ok now. Let see what happens afterwards.
legendary
Activity: 1036
Merit: 1001
April 22, 2017, 01:11:37 PM
#74
Seems ok and fast.
full member
Activity: 154
Merit: 100
April 22, 2017, 01:09:24 PM
#73
Been working perfect for a few hours now.  Last night and this morning had difficulty connecting (US East).
administrator
Activity: 5222
Merit: 13032
April 22, 2017, 01:07:56 PM
#72
How's it working for everyone now? I changed some stuff.

(It's difficult for me to test this because I don't have access to any machines which are affected by the issue...)
hero member
Activity: 1638
Merit: 756
Bobby Fischer was right
April 22, 2017, 12:43:25 PM
#71
https://pastebin.com/raw/EaKixQni
Theymos posted solution to all problems with accessing forum!
All needs to be done is to edit your hosts file with one of IP addresses mentioned above.
For a Windows system, the file is located at c:\windows\system32\drivers\etc\hosts.  

This is temporary solution! Don't forget about that change cause you wont be able to access forum in few months!
legendary
Activity: 1036
Merit: 1001
April 22, 2017, 12:42:58 PM
#70
Suffering from New York.
But if I use Japanese VPN everything is normal.

Code:
Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\Users\Deep>ping bitcointalk.org

Pinging bitcointalk.org [52.45.214.107] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 52.45.214.107:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\Deep>tracert bitcointalk.org

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

  1    <1 ms    <1 ms    <1 ms  192.168.10.1
  2    31 ms    49 ms    20 ms  SYNOLOGYROUTER [192.168.1.1]
  3     *        *        *     Request timed out.
  4    39 ms    33 ms    39 ms  67.59.255.193
  5    28 ms    39 ms    41 ms  rtr1-ge1-19.mhe.whplny.cv.net [67.83.231.1]
  6    53 ms    82 ms    30 ms  64.15.8.168
  7    43 ms    37 ms    39 ms  rtr1-tg11-1.in.nwrknjmd.cv.net [64.15.0.82]
  8    31 ms    44 ms    33 ms  52.95.216.134
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18    59 ms    56 ms    53 ms  54.239.110.167
 19    47 ms    40 ms    55 ms  54.239.111.55
 20    33 ms    35 ms    36 ms  205.251.244.212
 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.

C:\Users\Deep>
hero member
Activity: 1414
Merit: 516
April 22, 2017, 12:22:38 PM
#69
Hi. I have same timeout error.  I get this timeout error from yesterdary. Now i use some proxy to acces forum. When you will resolve it?

hero member
Activity: 1442
Merit: 578
April 22, 2017, 11:38:31 AM
#68
Just for information, i'm still experiencing connection error if i remove ip entries in the hosts file. From Italy.
legendary
Activity: 3234
Merit: 1375
Slava Ukraini!
April 22, 2017, 11:36:51 AM
#67
After more than 24 hours since problems started, forum is still extremely slow. Proxy makes situation better, but it's still not perfect. Ddos attacks is usual thing on bitcointalk and it's really annoying. And one strange thing for me, that forum have connection problems only in some parts of the world.
EDIT After changin IP in my hosts file, forum loads as it should be.
hero member
Activity: 1442
Merit: 629
Vires in Numeris
April 22, 2017, 10:06:08 AM
#66
If you need another trace: (without VPN or anything, normal DSL connection)
(I can use the forum, loading of the pages are slow, usually with error messages, but it still works somehow)
Code:
Tracing route to bitcointalk.org [52.45.214.107]
over a maximum of 30 hops:

  1     3 ms     2 ms     3 ms  -------------------------
  2    20 ms    19 ms    18 ms  lo1.meroasr0-debrecen.net.telekom.hu [145.236.238.12]
  3    22 ms    22 ms    22 ms  81.183.3.16
  4    22 ms    21 ms    22 ms  81.183.3.16
  5    22 ms    24 ms    21 ms  81.183.3.145
  6    41 ms    38 ms    40 ms  80.157.202.125
  7    63 ms    39 ms    38 ms  ae-9.r01.vienat01.at.bb.gin.ntt.net [129.250.66.125]
  8    95 ms    38 ms    42 ms  ae-1.r20.frnkge04.de.bb.gin.ntt.net [129.250.2.77]
  9   131 ms   132 ms   131 ms  ae-8.r22.asbnva02.us.bb.gin.ntt.net [129.250.4.96]
 10   135 ms   264 ms   132 ms  ae-7.r06.asbnva02.us.bb.gin.ntt.net [129.250.2.121]
 11   130 ms   130 ms   132 ms  ae-5.amazon.asbnva02.us.bb.gin.ntt.net [168.143.232.74]
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14   151 ms   153 ms   149 ms  54.239.110.145
 15   133 ms   131 ms   131 ms  54.239.108.59
 16   131 ms   131 ms   132 ms  205.251.245.191
 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.

Trace complete.
sr. member
Activity: 462
Merit: 250
bvo.trybravo.com
April 22, 2017, 06:15:20 AM
#65
Its still not working from Philippines. I also thought its just me that experienced it today because it always does happen because my brothers watching youtube. Sure its not just me experiencing this from Philippines.

Been this for an hour already.



yes, i do the same thing with you, pinging the website but the result RTO but when i try checking this forum on website down checker like isitdown rightnow and uptrends result of this website is up, the problem just on me, i test using uptrend in few country can't acces the forum like new york, london, etc.

#minexcoin.com
sr. member
Activity: 462
Merit: 250
bvo.trybravo.com
April 22, 2017, 05:58:39 AM
#64
i have the same problem, the the largest isp in my country before get problem with the hardware, but the problem was fixed, i think i can't acces bitcointalk because the isp, but im trying to use VPN work and now not work again, The problem is in bitcointalk itself.

#minexcoin.com
full member
Activity: 280
Merit: 112
https://i.imgur.com/nDGTBjp.png
April 22, 2017, 05:21:06 AM
#63
Virgin is my ISP for my broadband. When I switch from my mobile network to virgin it said the bitcointalk forum was unreachable. I thought this was the site but when I switch back to my mobile nextwork which is different from my home broadband provider it the site is available, maybe the forum is blocked now by certain ISP's or O may need to reset the router after yesterday issues. I will try that shortly and inform you guys of the outcome. I'm suspecting it's an issues that some of our ISP priviera have not updates the dns records for the forum.
hero member
Activity: 700
Merit: 500
April 22, 2017, 04:48:14 AM
#62
Its still not working from Philippines. I also thought its just me that experienced it today because it always does happen because my brothers watching youtube. Sure its not just me experiencing this from Philippines.

Been this for an hour already.

legendary
Activity: 2674
Merit: 2965
Terminated.
April 22, 2017, 03:25:19 AM
#61
Via a VPN based in NL.

Quote
 2    25 ms    24 ms    27 ms  [redacted/see IP from post]
  3    67 ms    25 ms    25 ms  te-0-7-0-3.cr06.ams-01.leaseweb.net [81.17.32.214]
  4    59 ms    23 ms    28 ms  xe4-0-1.amster51.ams.seabone.net [195.22.213.38]
  5   124 ms   107 ms   108 ms  racc.newark11.new.seabone.net [195.22.216.227]
  6   185 ms   182 ms   109 ms  amazon.ashburn2.ash.seabone.net [195.22.206.29]
  7     *        *        *     Request timed out.
-snip-
 10     *        *        *     Request timed out.
 11   127 ms   127 ms   126 ms  54.239.110.155
 12   111 ms   110 ms   111 ms  54.239.111.59
 13   119 ms   111 ms   119 ms  205.251.244.212
 14     *        *        *     Request timed out.
-snip-
 30     *        *        *     Request timed out.

It has only stabilized very briefly when the IP was changed as per your post. This has lasted less than an hour. The snipped parts are all identical (i.e. all time outs).
administrator
Activity: 5222
Merit: 13032
April 22, 2017, 03:05:35 AM
#60
Does any of you know until when the problem will end? I have been getting updates from the Twitter account of Bitcointalk and at first it said it was a denial of service attack and the next hour Theymos said it is another unknown problem.

It's an ongoing DDoS attack. Eventually, the attack will either end or I will figure out how to mitigate it, but I currently don't have a time estimate.
legendary
Activity: 2898
Merit: 1823
April 22, 2017, 02:58:08 AM
#59
Does any of you know until when the problem will end? I have been getting updates from the Twitter account of Bitcointalk and at first it said it was a denial of service attack and the next hour Theymos said it is another unknown problem.

Have there been any denial of service attacks during the time of the MtGox pump?
newbie
Activity: 6
Merit: 0
April 22, 2017, 02:30:05 AM
#58
Can't connect from Croatia

Code:
			
1 * * *


2 core22.fsn1.hetzner.com 213.239.229.133 de 0.264 ms 0.259 ms
core21.fsn1.hetzner.com 213.239.229.129 de 0.253 ms


3 core1.fra.hetzner.com 213.239.245.177 de 4.834 ms
core1.fra.hetzner.com 213.239.245.218 de 4.811 ms
core1.fra.hetzner.com 213.239.245.177 de 4.834 ms


4 * * *


5 ae-1.r24.frnkge08.de.bb.gin.ntt.net 129.250.6.206 us 5.066 ms 5.303 ms 5.278 ms


6 ae-4.r25.nycmny01.us.bb.gin.ntt.net 129.250.2.4 us 86.655 ms 87.629 ms 87.622 ms


7 ae-2.r08.nycmny01.us.bb.gin.ntt.net 129.250.6.209 us 86.443 ms
ae-2.r07.nycmny01.us.bb.gin.ntt.net 129.250.3.98 us 85.554 ms
ae-2.r08.nycmny01.us.bb.gin.ntt.net 129.250.6.209 us 86.443 ms


8 ae-9.amazon.nycmny01.us.bb.gin.ntt.net 129.250.201.130 us 87.187 ms
ae-11.amazon.nycmny01.us.bb.gin.ntt.net 129.250.201.138 us 90.167 ms
ae-7.amazon.nycmny01.us.bb.gin.ntt.net 129.250.201.122 us 89.294 ms


9 * * *


10 * * *


11 * * *


12 * * *


13 * * *
No reply for 5 hops. Assuming we reached firewall
administrator
Activity: 5222
Merit: 13032
April 22, 2017, 01:44:33 AM
#57
Additional traceroutes would be useful from those still unable to connect normally.
sr. member
Activity: 630
Merit: 250
★Bitvest.io★ Play Plinko or Invest!
April 22, 2017, 01:25:46 AM
#56
I had the same problem also accessing the site thought my connection is not lagging. I think it was on bitcointalk side. I sometimes can connect easier but most of the time it takes forever for a page to load. At least I can make some posts but it really takes time and patience just to load one.From what I heard is there a site update? or just a DDOS attack?
hero member
Activity: 1442
Merit: 578
April 22, 2017, 01:20:06 AM
#55

Hi guys. From Italy i'm still experiencing problems. I can connect only if i manually set one ip into hosts file, as theymos suggested.

Here is a traceroute without hosts file change, i hope it will be useful:

Code:
Traccia instradamento verso bitcointalk.org [52.45.214.107]
su un massimo di 30 punti di passaggio:

  1     1 ms    <1 ms     1 ms  www.routerlogin.com [192.168.0.1]
  2     *        *        *     Richiesta scaduta.
  3    25 ms    47 ms    24 ms  172.17.105.181
  4    25 ms    27 ms    27 ms  172.17.104.145
  5    32 ms    28 ms    31 ms  172.19.241.228
  6    34 ms    31 ms    31 ms  etrunk42.milano1.mil.seabone.net [93.186.128.78]

  7   131 ms   128 ms   127 ms  racc.newark11.new.seabone.net [195.22.216.227]
  8   133 ms   133 ms   133 ms  amazon.ashburn2.ash.seabone.net [195.22.206.85]

  9     *        *        *     Richiesta scaduta.
 10     *        *        *     Richiesta scaduta.
 11     *        *        *     Richiesta scaduta.
 12     *        *        *     Richiesta scaduta.
 13   140 ms   145 ms   132 ms  54.239.110.173
 14   131 ms   128 ms   128 ms  54.239.111.61
 15   126 ms   127 ms   126 ms  205.251.244.216
 16     *        *        *     Richiesta scaduta.
 17     *        *        *     Richiesta scaduta.
 18     *        *        *     Richiesta scaduta.
 19     *        *        *     Richiesta scaduta.
 20     *        *        *     Richiesta scaduta.
 21     *        *        *     Richiesta scaduta.
 22     *        *        *     Richiesta scaduta.
 23     *        *        *     Richiesta scaduta.
 24     *        *        *     Richiesta scaduta.
 25     *        *        *     Richiesta scaduta.
 26     *        *        *     Richiesta scaduta.
 27     *        *        *     Richiesta scaduta.
 28     *        *        *     Richiesta scaduta.
 29     *        *        *     Richiesta scaduta.
 30     *        *        *     Richiesta scaduta.

Traccia completata.
hero member
Activity: 714
Merit: 500
April 22, 2017, 12:59:22 AM
#54
Happening with me too since yesterday, can't connect with some of the VPN either. The page opens up every now and then and that is it, the next moment it stops loading again the connection times out.
Any news on when the issue will actually be resolved?
hero member
Activity: 602
Merit: 500
April 22, 2017, 12:57:05 AM
#53
Hello!

I can't conect from Ukraine....

hero member
Activity: 882
Merit: 500
April 21, 2017, 11:40:51 PM
#52
Hello

I'm having trouble connecting to bitcointalk.org, it loads the website forever.

I can only successful access it through a USA proxy,but directly I can't connect to the site.It timeouts or loads forever.All other sites work..I'm connecting from Croatia.
This problem is from.the night , at my local.time of 12:00AM from last night , I was also not able to access , even the internet connection was very fast for every  site , but I think this problem arise due to the problem of the server problem and now I think it get solved .
I remembered that the same problem was arise in the 3last month of the year 2016 , Currently everything is smooth , so we don't need to worry for this forum ( which is like a new paper in early morning ) .
administrator
Activity: 5222
Merit: 13032
April 21, 2017, 11:08:22 PM
#51
See here for hosts file IPs and other info: https://pastebin.com/raw/EaKixQni
legendary
Activity: 3836
Merit: 4969
Doomed to see the future and unable to prevent it
April 21, 2017, 08:30:04 PM
#50
This is fucked up, DNS poisoning? What is the correct IP?

bitcointalk.org now has multiple A records. They're all correct. Tools like ping which expect only one will use the first one returned by the DNS server, which is random.

You intentionally spelled it that way?

Whats the list so I can put it in my hosts file.
administrator
Activity: 5222
Merit: 13032
April 21, 2017, 08:05:06 PM
#49
This is fucked up, DNS poisoning? What is the correct IP?

bitcointalk.org now has multiple A records. They're all correct. Tools like ping which expect only one will use the first one returned by the DNS server, which is random.
legendary
Activity: 3836
Merit: 4969
Doomed to see the future and unable to prevent it
April 21, 2017, 07:59:49 PM
#48
This is fucked up, DNS poisoning? What is the correct IP?

Code:
C:\Windows\system32>ping bitcointalk.org

Pinging bitcointalk.org [34.206.81.205] with 32 bytes of data:
General failure.
General failure.
General failure.
General failure.

Ping statistics for 34.206.81.205:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Windows\system32>ping bitcointalk.org

Pinging BITcOintALK.org [52.86.24.80] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 52.86.24.80: bytes=32 time=42ms TTL=239
Reply from 52.86.24.80: bytes=32 time=39ms TTL=239

Ping statistics for 52.86.24.80:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
    Minimum = 39ms, Maximum = 42ms, Average = 40ms

BITcOintALK

copper member
Activity: 2142
Merit: 1305
Limited in number. Limitless in potential.
April 21, 2017, 07:31:35 PM
#47
I guess its only me experiencing this, I tried googling if the forum is down since I have better connection and I can access any sites but in the end still I cant access the forum so using VPN I can access the forum again but I don't really know if what is the reason why this happens? I doubt if its DDOS attack.
hero member
Activity: 1722
Merit: 528
April 21, 2017, 07:14:46 PM
#46
Now forum works on my PC, but it loads slower than usual.
But I can't reach forum with my smarthpone by using. I'm using same Wi-Fi like on my PC.
Now I tried visit forum on my phone by using proxy and bitcointalk loads fine, but it's still hard to publish post.

I am using android phone to access this site and yes it loads slower than usual, but now, I can't access the site again, using this android phone without a VPN, I tried using VPN server in my country, it work earlier now I can't. I used the Unitwd State server and it worked fine there. I can't access these site normall as usual.
legendary
Activity: 3234
Merit: 1375
Slava Ukraini!
April 21, 2017, 06:17:36 PM
#45
Now forum works on my PC, but it loads slower than usual.
But I can't reach forum with my smarthpone by using. I'm using same Wi-Fi like on my PC.
Now I tried visit forum on my phone by using proxy and bitcointalk loads fine, but it's still hard to publish post.
legendary
Activity: 1789
Merit: 2535
Goonies never say die.
April 21, 2017, 04:05:17 PM
#44
Seems better to me now
hero member
Activity: 1386
Merit: 503
April 21, 2017, 03:40:47 PM
#43
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
Oh really? okay i'll try later after this post if i can accessing normal i'll edit my post. thanks for the information.

EDIT: its normal again now, now i can access bitcointalk without VPN. Oh yeah anyway i use ISP from Telkomsel. thanks
hero member
Activity: 1722
Merit: 528
April 21, 2017, 03:39:43 PM
#42
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.
legendary
Activity: 2030
Merit: 1059
Wait... What?
April 21, 2017, 03:34:32 PM
#41
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
hero member
Activity: 1386
Merit: 503
April 21, 2017, 03:18:09 PM
#40
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
legendary
Activity: 2030
Merit: 1059
Wait... What?
April 21, 2017, 03:14:12 PM
#39
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.
member
Activity: 115
Merit: 10
Tip: 1JBSwRgm7iMzc7uyhnJdxH7hSECdJkdMoj
April 21, 2017, 03:07:08 PM
#38
Works for now to germany.

If it's getting worse again, i will post there ->https://redd.it/66os8f!
administrator
Activity: 5222
Merit: 13032
April 21, 2017, 02:59:52 PM
#37
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.
sr. member
Activity: 787
Merit: 276
Currency Xchanger™
April 21, 2017, 02:19:09 PM
#36
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 ..
member
Activity: 115
Merit: 10
Tip: 1JBSwRgm7iMzc7uyhnJdxH7hSECdJkdMoj
April 21, 2017, 01:30:40 PM
#35
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.
copper member
Activity: 1330
Merit: 899
🖤😏
April 21, 2017, 01:29:31 PM
#34
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.
legendary
Activity: 2968
Merit: 3406
Crypto Swap Exchange
April 21, 2017, 01:08:40 PM
#33
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.
legendary
Activity: 3276
Merit: 2442
April 21, 2017, 01:04:38 PM
#32
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
newbie
Activity: 6
Merit: 0
April 21, 2017, 12:53:49 PM
#31
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.
hero member
Activity: 1722
Merit: 508
April 21, 2017, 12:14:10 PM
#30
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.
hero member
Activity: 518
Merit: 501
April 21, 2017, 12:06:52 PM
#29
must be a rolling dns update
newbie
Activity: 34
Merit: 0
April 21, 2017, 11:59:26 AM
#28
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.

hero member
Activity: 1638
Merit: 756
Bobby Fischer was right
April 21, 2017, 11:49:06 AM
#27
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) 
administrator
Activity: 5222
Merit: 13032
April 21, 2017, 11:45:15 AM
#26
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.
legendary
Activity: 3556
Merit: 9709
#1 VIP Crypto Casino
April 21, 2017, 11:44:52 AM
#25
Working fine here in the UK. I tried earlier & got a time out but fine now.
hero member
Activity: 882
Merit: 507
April 21, 2017, 11:44:04 AM
#24
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.
member
Activity: 74
Merit: 10
April 21, 2017, 11:43:19 AM
#23
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.
full member
Activity: 280
Merit: 112
https://i.imgur.com/nDGTBjp.png
April 21, 2017, 11:41:51 AM
#22
Is anyone still experiencing issues? It seems to it's connecting must faster now after all day running slow.
hero member
Activity: 924
Merit: 506
April 21, 2017, 11:41:33 AM
#21
Tried from Ashburn/ New york/ London/ middle east and only now I got the 504 error page which I didn't before, though I was good while with Romania IP this morning.
Every time I get the 504 page it means server company is on to the issue and then everything goes well after couple hours.
hero member
Activity: 728
Merit: 500
EtherSphere - Social Games
April 21, 2017, 11:41:19 AM
#20
Trying to get on since this morning for the last 4 hours but without success.
Was just timing out and thought they were moving to the new forum now when this happened.
Was thinking they just took it offline completely so to do the transition smoothly,
apparently now. Embarrassed
legendary
Activity: 1036
Merit: 1001
April 21, 2017, 11:41:13 AM
#19
From New york down, with Canada VPN some time.

hero member
Activity: 1106
Merit: 509
April 21, 2017, 11:40:06 AM
#18
work now Indonesia! Cool
member
Activity: 115
Merit: 10
Tip: 1JBSwRgm7iMzc7uyhnJdxH7hSECdJkdMoj
April 21, 2017, 11:38:24 AM
#17
Works now from Germany!
hero member
Activity: 854
Merit: 502
CTO & Spokesman
April 21, 2017, 11:37:51 AM
#16
I also experienced the same problem here in ph almost morethan 4, hours . But thanks God it's now back to normal hope it's not gonna happen again.
hero member
Activity: 518
Merit: 501
April 21, 2017, 11:36:28 AM
#15
connection from US was down

I was also having problems accessing the canadian VPN completely so maybe one of the dns servers is down.

looks like it's resolved?
legendary
Activity: 1120
Merit: 1004
April 21, 2017, 11:35:23 AM
#14
I am having great troubles accessing the forum, but it is going by bursts. For exemple, now I can browse correctly, at least for now, while a few minutes ago the forum was totally unreachable.

If someone can explain me how to get it, I can post my traceroute.
member
Activity: 108
Merit: 10
BUILD - Innovative Building Platform
April 21, 2017, 11:18:40 AM
#13
The connection from Bulagria is extremly slow too.
This is traceroute from here

 7   123 ms   123 ms   123 ms  amazon.ashburn2.ash.seabone.net [195.22.206.85]

  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12   165 ms   146 ms   143 ms  54.239.110.145
 13   132 ms   131 ms   131 ms  54.239.111.49
 14   131 ms   131 ms   131 ms  205.251.244.216
 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.
legendary
Activity: 2030
Merit: 1059
Wait... What?
April 21, 2017, 11:17:01 AM
#12
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.

Still having the problem here, Indonesia. Been like this since this morning, I am not a tech expert, in fact, my knowledge is next to nothing, but I don't think it's a mere ISP, because I've tried to access them from both my wifi and from mobile data which came from different company, both found difficulties on reaching this site.

I tried Chrome's GOM and it didn't work, tried HSS and it works fine. Should I try to change countries on HSS and inform you which countries found difficulties reaching bitcointalk?
administrator
Activity: 5222
Merit: 13032
April 21, 2017, 10:56:19 AM
#11
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.
legendary
Activity: 1232
Merit: 1091
April 21, 2017, 10:50:48 AM
#10
I wouldn't be surprised to see a few jokers stating that they have hacked this forum and compromised the user data base, where they directly try to sell it to the highest bidder (while in reality it's just the old data base).
EFS
staff
Activity: 3822
Merit: 2123
Crypto Swap Exchange
April 21, 2017, 10:33:05 AM
#9
Theymos is already informed. I don't have any connection problems though.
sr. member
Activity: 787
Merit: 276
Currency Xchanger™
April 21, 2017, 09:27:31 AM
#8
Terrible slow now , at first i thought it may be my internet so i fucked my ISP guy by calling them lol , i have very high speed internet but then saw this only happening for Bitcointalk forum , i guess large scale DDOS possibly . Any staff or admin want to mention about this issue ? please fix it :/
legendary
Activity: 1372
Merit: 1032
All I know is that I know nothing.
April 21, 2017, 09:16:17 AM
#7
so i am not alone... >facepalm<
legendary
Activity: 1042
Merit: 2805
Bitcoin and C♯ Enthusiast
April 21, 2017, 09:03:50 AM
#6
It can not be DDoS, because I can access the forum through a proxy with high speed. But with my own IP, it doesn't work.

Maybe server has gone mad and banned all the IP addresses! Grin
legendary
Activity: 1792
Merit: 1283
April 21, 2017, 08:50:23 AM
#5
Using a UK vpn now and it's still slow but at least manageable.
Couldn't get anything done through my main connection (europe)
hero member
Activity: 1022
Merit: 564
Need some spare btc for a new PC
April 21, 2017, 08:42:17 AM
#4
So it looks like its bad for all of us and it's probably some DDoS attack... Chinese attackers? Cheesy tho, it's was ok this morning for me and it started somewhere around 10am server time... Took me almost 30min to reply to this post. :|
legendary
Activity: 3276
Merit: 2442
April 21, 2017, 07:51:25 AM
#3
Forum is cancer since the morning. I was about to open this topic myself but i've seen people don't give fuck for hours so i thought i guess i am the only who's one having the problem.

Restarted my laptop, reinstalled chrome, scanned the PC with kaspersky... Non-worked.

I post this message by TOR browser. It is slow but still works somehow. My regular IP don't work, VPN don't neither. Forum is fucked.
hero member
Activity: 924
Merit: 506
April 21, 2017, 07:45:04 AM
#2
Time out connection since morning, DDOS much?
newbie
Activity: 6
Merit: 0
April 21, 2017, 07:07:04 AM
#1
Hello

I'm having trouble connecting to bitcointalk.org, it loads the website forever.

I can only successful access it through a USA proxy,but directly I can't connect to the site.It timeouts or loads forever.All other sites work..I'm connecting from Croatia.
Jump to: