adam/ipfs-blog
1
0
Fork 0
mirror of https://github.com/ipfs/ipfs-blog.git synced 2026-08-10 10:52:45 +02:00
Code Issues Packages Projects Releases Wiki Activity

Update src/_blog/2023-05-ipfs-unresponsive-nodes-incident.md

Browse Source 
Co-authored-by: Steve Loeppky <biglep@protocol.ai>
This commit is contained in:
Yiannis Psaras
2023-05-07 21:13:25 +03:00
committed by GitHub
parent 128e9bce31
commit 099b6e1a44
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/_blog/2023-05-ipfs-unresponsive-nodes-incident.md
+1 -1
View File
@@ -19,7 +19,7 @@ In this blogpost we’ll go through the timeline of the event from “Incident D
## Incident Detection: we’ve got a problem❗️
> At the beginning of 2023 a central component of the IPFS network, namely the public IPFS DHT experienced a large-scale incident. *During this incident, [60% of the IPFS DHT Server nodes became unresponsive](https://github.com/protocol/network-measurements/blob/master/reports/2023/calendar-week-04/ipfs/plots/crawl-unresponsive.png).*
> At the beginning of 2023 a central component of the IPFS network, namely the public IPFS DHT, experienced a large-scale incident. *During this incident, [60% of the IPFS DHT Server nodes became unresponsive](https://github.com/protocol/network-measurements/blob/master/reports/2023/calendar-week-04/ipfs/plots/crawl-unresponsive.png).*
>
Unresponsive here means that nodes would seem to be online, they would accept connections from other nodes, but they wouldn’t reply to requests. Basically, when a node would try to write to one of the unresponsive nodes, the unresponsive node would terminate the connection immediately.