Lauda
Legendary
Offline
Activity: 2674
Merit: 2965
Terminated.
|
|
April 22, 2017, 08:25:19 AM |
|
Via a VPN based in NL. 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).
|
"The Times 03/Jan/2009 Chancellor on brink of second bailout for banks" 😼 Bitcoin Core ( onion)
|
|
|
btctube
|
|
April 22, 2017, 09:48:14 AM |
|
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.
|
|
|
|
Populous World
Full Member
Offline
Activity: 280
Merit: 112
https://i.imgur.com/nDGTBjp.png
|
|
April 22, 2017, 10:21:06 AM |
|
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.
|
|
|
|
yatogami
Sr. Member
Offline
Activity: 462
Merit: 250
bvo.trybravo.com
|
|
April 22, 2017, 10:58:39 AM |
|
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
|
|
|
|
yatogami
Sr. Member
Offline
Activity: 462
Merit: 250
bvo.trybravo.com
|
|
April 22, 2017, 11:15:20 AM |
|
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
|
|
|
|
bitart
|
|
April 22, 2017, 03:06:08 PM |
|
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) 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.
|
|
|
|
LTU_btc
Legendary
Offline
Activity: 3234
Merit: 1375
Slava Ukraini!
|
|
April 22, 2017, 04:36:51 PM Last edit: April 22, 2017, 05:12:50 PM by LTU_btc |
|
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.
|
|
|
|
Cent21
|
|
April 22, 2017, 04:38:31 PM |
|
Just for information, i'm still experiencing connection error if i remove ip entries in the hosts file. From Italy.
|
|
|
|
Adriano2010
|
|
April 22, 2017, 05:22:38 PM Last edit: August 20, 2018, 01:38:28 PM by Adriano2010 |
|
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?
|
|
|
|
DeepCoin
Legendary
Offline
Activity: 1036
Merit: 1001
|
|
April 22, 2017, 05:42:58 PM |
|
Suffering from New York. But if I use Japanese VPN everything is normal. 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>
|
|
|
|
poptok1
|
|
April 22, 2017, 05:43:25 PM |
|
https://pastebin.com/raw/EaKixQniTheymos 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!
|
|
|
|
theymos
Administrator
Legendary
Offline
Activity: 5376
Merit: 13400
|
|
April 22, 2017, 06:07:56 PM |
|
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...)
|
1NXYoJ5xU91Jp83XfVMHwwTUyZFK64BoAD
|
|
|
Kanine Awe
|
|
April 22, 2017, 06:09:24 PM |
|
Been working perfect for a few hours now. Last night and this morning had difficulty connecting (US East).
|
|
|
|
DeepCoin
Legendary
Offline
Activity: 1036
Merit: 1001
|
|
April 22, 2017, 06:11:37 PM |
|
Seems ok and fast.
|
|
|
|
akamit
|
|
April 22, 2017, 06:17:40 PM |
|
I was also getting same problem to access bitcointalk. But it seems ok now. Let see what happens afterwards.
|
|
|
|
bitart
|
|
April 22, 2017, 07:38:27 PM Last edit: April 22, 2017, 07:49:25 PM by bitart |
|
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: >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: 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
|
|
|
|
Cent21
|
|
April 22, 2017, 07:42:28 PM |
|
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.
|
|
|
|
Real-Duke
Legendary
Offline
Activity: 3556
Merit: 2330
Top Crypto Casino
|
|
April 22, 2017, 07:52:04 PM |
|
Nice to be back! The side wasn't reachable the whole day for me but here we go again
|
|
|
|
JessicaG
|
|
April 23, 2017, 08:29:06 PM |
|
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.
|
|
|
|
lockept93
|
|
April 24, 2017, 02:20:01 AM |
|
Runs fine now - but the last days was horrorble.
|
|
|
|
|