top | item 35876533 What happens when half of the IPFS network is down? 87 points| dennis-tra | 2 years ago |blog.ipfs.tech 9 comments order hn newest [+] [-] RobotToaster|2 years ago|reply >The problematic configuration which was applied manually (i.e. was not based on the default values of kubo-v0.17)So how did 60% of the network become manually mis-configured? Or does a single company (cloudflare?) make up 60% of the network? [+] [-] Lt_Riza_Hawkeye|2 years ago|reply From my reading, they mis-configured it in their use of the library - using the default value instead would have avoided the problem. [+] [-] bombcar|2 years ago|reply Someone did some digging on various non-Bitcoin crypto coins and found that a huge percentage of the whatever it is they run were just running on AWS. load replies (1) [+] [-] whimsicalism|2 years ago|reply Like the entire application binary was mis-configured. so anyone running the newest update would be misconfigured [+] [-] runlaszlorun|2 years ago|reply Am I the only one who finds it a bit odd that the article starts off bragging about what was an outage?And I as soon as I hear “we were still running with half our network down”, the first thing I think of is that no one really is using IPFS at all. [+] [-] kabdib|2 years ago|reply "Connection was reset."Well, that might address the mystery :-)
[+] [-] RobotToaster|2 years ago|reply >The problematic configuration which was applied manually (i.e. was not based on the default values of kubo-v0.17)So how did 60% of the network become manually mis-configured? Or does a single company (cloudflare?) make up 60% of the network? [+] [-] Lt_Riza_Hawkeye|2 years ago|reply From my reading, they mis-configured it in their use of the library - using the default value instead would have avoided the problem. [+] [-] bombcar|2 years ago|reply Someone did some digging on various non-Bitcoin crypto coins and found that a huge percentage of the whatever it is they run were just running on AWS. load replies (1) [+] [-] whimsicalism|2 years ago|reply Like the entire application binary was mis-configured. so anyone running the newest update would be misconfigured
[+] [-] Lt_Riza_Hawkeye|2 years ago|reply From my reading, they mis-configured it in their use of the library - using the default value instead would have avoided the problem.
[+] [-] bombcar|2 years ago|reply Someone did some digging on various non-Bitcoin crypto coins and found that a huge percentage of the whatever it is they run were just running on AWS. load replies (1)
[+] [-] whimsicalism|2 years ago|reply Like the entire application binary was mis-configured. so anyone running the newest update would be misconfigured
[+] [-] runlaszlorun|2 years ago|reply Am I the only one who finds it a bit odd that the article starts off bragging about what was an outage?And I as soon as I hear “we were still running with half our network down”, the first thing I think of is that no one really is using IPFS at all.
[+] [-] RobotToaster|2 years ago|reply
So how did 60% of the network become manually mis-configured? Or does a single company (cloudflare?) make up 60% of the network?
[+] [-] Lt_Riza_Hawkeye|2 years ago|reply
[+] [-] bombcar|2 years ago|reply
[+] [-] whimsicalism|2 years ago|reply
[+] [-] runlaszlorun|2 years ago|reply
And I as soon as I hear “we were still running with half our network down”, the first thing I think of is that no one really is using IPFS at all.
[+] [-] kabdib|2 years ago|reply
Well, that might address the mystery :-)