pull down to refresh

You imply that the whole LN is not working anymore, when in fact is your own single node that is not doing well. Consider changing your node policies. LN is just fine.
Due to my circumstances, I am rarely online - every couple of days when I need to spend sats I am online for a couple of hours. But being rarely online was never a problem when it came to spending sats in previous years. I use default settings. As an attempt of dealing with the problem I even created a channel with a non-onion node (with wallet of satoshi) and tried to pay over IPv4 instead of over Tor. All this top no avail. The payments do not go through and I always get this type of message:
"code": 210, "message": "Ran out of routes to try after 4 attempts: see `paystatus`", "attempts": [ { "status": "failed", "failreason": "failed: WIRE_TEMPORARY_CHANNEL_FAILURE (reply from remote)", "partid": 0, "amount_msat": 50000000 }, { "status": "failed", "failreason": "failed: WIRE_TEMPORARY_CHANNEL_FAILURE (reply from remote)", "partid": 1, "amount_msat": 50000000, "parent_partid": 0 }, { "status": "failed", "failreason": "failed: WIRE_TEMPORARY_CHANNEL_FAILURE (reply from remote)", "partid": 2, "amount_msat": 50000000, "parent_partid": 1 }, { "status": "failed", "failreason": "failed: WIRE_TEMPORARY_CHANNEL_FAILURE (reply from remote)", "partid": 3, "amount_msat": 50000000, "parent_partid": 2 } ] }
reply
Check the logs for you LN graph sync. I think you are not synced correctly and that's why you get WIRE_TEMPORARY_CHANNEL_FAILURE (reply from remote)
reply