Indeed we do need more nodes I am running 6 myself at the moment which is rather skewing the whole idea and a tad expensive in the long run.
So now I will start taking them down one at a time.
Will we see the split coalesce or will we just have two fairly small sections?
haha someone keeps pouring new vaults in 
it stays @ 27
/me unleashes BigRedSwitch
in the mean time I keep publishing websites, it seems to work smoothly despite the routing mess
I took down 5 instances
safe://eeek.southside/ is still up after 20-25% churn
Just attempted to start 5 nodes - Looks like our split has coalesced again
The data uploaded Monday night is alive. Download speed about 300KB/seg.
I think just about every vault has been rebooted since Monday night - could be wrong but I know all of mine either have been rebooted or were not running on Monday night
both mine stayed up and steady
Mine were steady too, it was me that commanded a reboot. This isn’t Windows
A tad unfair - Windows no longer crashes unexpectedly (quite so often)
oh, sure, now it often crashes expectedly 
I don’t know if is important but a couple of warn.
WARN 22:59:53.352056500 [routing::peer_manager peer_manager.rs:1246] Node(f9c735
…(1)) Failed to insert connection info from 61f471… (PeerId(cec0dfcc…)) as pe
er’s current state is AwaitingNodeIdentify(false)
WARN 22:59:53.353057300 [routing::states::node node.rs:1695] Node(f9c735…(1)) F
ailed to insert connection info from 61f471… (PeerId(cec0dfcc…)): UnexpectedSt
ate
Evening all. b53397 reporting for duty
I found a couple too
WARN 22:19:15.480730355 [routing::peer_manager peer_manager.rs:1246] Node(3e4592..(0)) Failed to insert connection info from 8a5cb9.. (PeerId(ecca0561..)) as peer's current state is AwaitingNodeIdentify(false)
WARN 22:19:15.480896536 [routing::states::node node.rs:1695] Node(3e4592..(0)) Failed to insert connection info from 8a5cb9.. (PeerId(ecca0561..)): UnexpectedState
WARN 22:19:15.510022704 [routing::peer_manager peer_manager.rs:1246] Node(3e4592..(0)) Failed to insert connection info from f9c735.. (PeerId(12c8c53c..)) as peer's current state is AwaitingNodeIdentify(false)
WARN 22:19:15.510140972 [routing::states::node node.rs:1695] Node(3e4592..(0)) Failed to insert connection info from f9c735.. (PeerId(12c8c53c..)): UnexpectedState
WARN 22:19:15.556377644 [routing::peer_manager peer_manager.rs:1246] Node(3e4592..(0)) Failed to insert connection info from d6f9f6.. (PeerId(33055170..)) as peer's current state is AwaitingNodeIdentify(false)
WARN 22:19:15.556544731 [routing::states::node node.rs:1695] Node(3e4592..(0)) Failed to insert connection info from d6f9f6.. (PeerId(33055170..)): UnexpectedState
@Viv @anon86652309 anything to get excited about?
I’ll add to the pile:
WARN 23:17:14.940776300 [routing::peer_manager peer_manager.rs:1246] Node(b53397..(1)) Failed to insert connection info from 6f21d3.. (PeerId(9bb7bc5a..)) as peer's current state is AwaitingNodeIdentify(false)
WARN 23:17:14.940776300 [routing::states::node node.rs:1695] Node(b53397..(1)) Failed to insert connection info from 6f21d3.. (PeerId(9bb7bc5a..)): UnexpectedState
Different nodes throwing errors in each case so far
Quite possible we are seeing the bug that caused them to pull 12_b originally.
The routing table is up to 30 now - I’m going to pull some of my AWS instances to save some budget for later.
But I’ll save the logs first.
I have a 60 day free trial of Google Cloud Platform. Up and running now (1 vCPU, 3.75 GB memory): static IP 104.154.104.210
I guess this is my peer id? e4ebb5be
Yes, you shoud eventually see something like
INFO 00:01:34.323192655 [routing::states::node node.rs:277] ----------------------------------------------------------------
INFO 00:01:34.323434050 [routing::states::node node.rs:278] | Node(3e4592..(0)) PeerId(a72896e7..) - Routing Table size: 31 |
INFO 00:01:34.323575015 [routing::states::node node.rs:279] ----------------------------------------------------------------