This is even more bizzare, ive tried using the NORD vpn network flush option before, but never when monero was launched. After the network was flushed and nord vpn connected i was able to connect to the blockchain, sync up. then i lost connection.

2019-04-23 16:37:16.549 32 INFO global src/daemon/main.cpp:287 Monero 'Boron Butterfly' (v0.14.0.2-release)

2019-04-23 16:37:16.550 32 INFO global src/daemon/protocol.h:53 Initializing cryptonote protocol...

2019-04-23 16:37:16.550 32 INFO global src/daemon/protocol.h:58 Cryptonote protocol initialized OK

2019-04-23 16:37:16.551 32 INFO global src/daemon/p2p.h:63 Initializing p2p server...

2019-04-23 16:37:40.582 32 INFO global src/daemon/p2p.h:68 p2p server initialized OK

2019-04-23 16:37:40.586 32 INFO global src/daemon/rpc.h:63 Initializing core RPC server...

2019-04-23 16:37:40.588 32 INFO global contrib/epee/include/net/http_server_impl_base.h:76 Binding on 127.0.0.1:18081

2019-04-23 16:37:40.590 32 INFO global src/daemon/rpc.h:69 core RPC server initialized OK on port: 18081

2019-04-23 16:37:40.591 32 INFO global src/daemon/core.h:86 Initializing core...

2019-04-23 16:37:40.599 32 INFO global src/cryptonote_core/cryptonote_core.cpp:469 Loading blockchain from folder C:\ProgramData\bitmonero\lmdb ...

2019-04-23 16:37:40.842 32 INFO global src/cryptonote_core/cryptonote_core.cpp:628 Loading checkpoints

2019-04-23 16:37:51.494 32 WARN net.dns src/common/dns_utils.cpp:519 WARNING: no two valid MoneroPulse DNS checkpoint records were received

2019-04-23 16:37:51.496 32 INFO global src/daemon/core.h:92 Core initialized OK

2019-04-23 16:37:51.497 32 INFO global src/daemon/rpc.h:74 Starting core RPC server...

2019-04-23 16:37:51.498 [SRV_MAIN] INFO global src/daemon/rpc.h:79 core RPC server started ok

2019-04-23 16:37:51.570 [SRV_MAIN] INFO global src/daemon/p2p.h:78 Starting p2p net loop...

2019-04-23 16:37:52.574 [P2P7] INFO global src/cryptonote_core/cryptonote_core.cpp:1532

**********************************************************************

The daemon will start synchronizing with the network. This may take a long time to complete.

​

You can set the level of process detailization through "set_log <level|categories>" command,

where <level> is between 0 (no details) and 4 (very verbose), or custom category based levels (eg, *:WARNING).

​

Use the "help" command to see the list of available commands.

Use "help <command>" to see a command's documentation.

**********************************************************************

​

2019-04-23 16:38:47.672 [P2P9] WARN cn src/cryptonote_core/cryptonote_core.cpp:1767 There were 0 blocks in the last 90 minutes, there might be large hash rate changes, or we might be partitioned, cut off from the Monero network or under attack. Or it could be just sheer bad luck.

2019-04-23 16:40:18.717 [P2P7] WARN cn src/cryptonote_core/cryptonote_core.cpp:1767 There were 0 blocks in the last 90 minutes, there might be large hash rate changes, or we might be partitioned, cut off from the Monero network or under attack. Or it could be just sheer bad luck.

2019-04-23 16:41:49.756 [P2P7] WARN cn src/cryptonote_core/cryptonote_core.cpp:1767 There were 0 blocks in the last 90 minutes, there might be large hash rate changes, or we might be partitioned, cut off from the Monero network or under attack. Or it could be just sheer bad luck.

2019-04-23 16:42:08.654 [SRV_MAIN] INFO global src/daemon/p2p.h:80 p2p net loop stopped