need banlist or something

I keep getting this. It not likely that 156 nodes are all offline at same time. I was able to update before and didnt change my json file. Same issue with both my zites. indicates all nodes are down or only 1 replies other than me.Im on limited bandwidth(metered) so I cant always be on.

failed:none indicates Tor node(I would think succeeds)
failed:timeout Im not sure..most of the zite is optional content.
why is 127 is the peer list? (points to self)

[FAILED] 123.166.197.234:15441: {'exception': 'Timeout'}
Site:1CNWuQ..4f2m [FAILED] 113.104.202.87:15441: {'exception': 'Timeout'}
Site:1CNWuQ..4f2m [FAILED] 176.9.146.48:63379: {'exception': 'Timeout'}
Site:1CNWuQ..4f2m [FAILED] 176.9.146.48:58670: {'exception': 'Timeout'}
Site:1CNWuQ..4f2m [FAILED] 176.9.146.48:65457: {'exception': 'Timeout'}
Site:1CNWuQ..4f2m [FAILED] 127.0.0.1:45326: None
Site:1CNWuQ..4f2m [FAILED] 127.0.0.1:0: None
Site:1CNWuQ..4f2m [FAILED] 172.79.23.204:15441: {'exception': 'Timeout'}
Site:1CNWuQ..4f2m [FAILED] 80.0.167.36:15441: {'exception': 'Timeout'}
Site:1CNWuQ..4f2m [FAILED] 113.113.91.208:15441: {'exception': 'Timeout'}

error: zero nodes connected, all failed. You must be hosting the zite and have peers.

Start with the reported peer-list and node-connection behavior in the issue, especially the 127.0.0.1 entries, timeout results, and the “zero nodes connected” error. Reproduce the failure if possible with the two affected zites and determine whether offline peers are retained incorrectly or whether Tor and optional-content peers are handled differently. Done means the cause is identified and the connection error or peer list behaves correctly.

Escrito por el modelo de indexación a partir del texto del issue.