From 099b6e1a44b2d62eb1e08e782993a2c0b528010d Mon Sep 17 00:00:00 2001 From: Yiannis Psaras <52073247+yiannisbot@users.noreply.github.com> Date: Sun, 7 May 2023 21:13:25 +0300 Subject: [PATCH] Update src/_blog/2023-05-ipfs-unresponsive-nodes-incident.md Co-authored-by: Steve Loeppky --- src/_blog/2023-05-ipfs-unresponsive-nodes-incident.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/_blog/2023-05-ipfs-unresponsive-nodes-incident.md b/src/_blog/2023-05-ipfs-unresponsive-nodes-incident.md index 5fdd1eb4..55f645aa 100644 --- a/src/_blog/2023-05-ipfs-unresponsive-nodes-incident.md +++ b/src/_blog/2023-05-ipfs-unresponsive-nodes-incident.md @@ -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.