Warnings

• github_user missing in bp.json

p2p.xprdata.org:9876

• P2P node p2p.xprdata.org:9876 is responding

https://mainnet-api.xprdata.org

• CORS headers properly configured
• API node https://mainnet-api.xprdata.org is responding correctly

http://mainnet-api.xprdata.org

• CORS headers properly configured
• API node http://mainnet-api.xprdata.org is responding correctly

Oks

• github_user present in bp.json

proton.genereos.io:9876

• P2P node proton.genereos.io:9876 is responding

http://proton.genereos.io

• CORS headers properly configured
• API node http://proton.genereos.io is responding correctly

https://proton.genereos.io

• CORS headers properly configured
• API node https://proton.genereos.io is responding correctly

Warnings

• github_user missing in bp.json

http://mainxpr.cindro.net

• CORS headers properly configured
• API node http://mainxpr.cindro.net is responding correctly

https://mainxpr.cindro.net

• CORS headers properly configured
• API node https://mainxpr.cindro.net is responding correctly

mainxpr-p2p.cindro.net:9870

• P2P node mainxpr-p2p.cindro.net:9870 is responding

Oks

• github_user present in bp.json

https://proton-api.eosiomadrid.io

• CORS headers properly configured
• API node https://proton-api.eosiomadrid.io is responding correctly
• History v1 ok for https://proton-api.eosiomadrid.io
• Hyperion history ok for https://proton-api.eosiomadrid.io

http://proton-api.eosiomadrid.io

• CORS headers properly configured
• API node http://proton-api.eosiomadrid.io is responding correctly
• History v1 ok for http://proton-api.eosiomadrid.io
• Hyperion history ok for http://proton-api.eosiomadrid.io

proton-seed.eosiomadrid.io:9876

• P2P node proton-seed.eosiomadrid.io:9876 is responding

Warnings

• github_user missing in bp.json

p2p-mainnet.artwebin.com:9876

• P2P node p2p-mainnet.artwebin.com:9876 is responding

https://mainnet-api.artwebin.com

• CORS headers properly configured
• API node https://mainnet-api.artwebin.com is responding correctly

http://mainnet-api.artwebin.com

• CORS headers properly configured
• API node http://mainnet-api.artwebin.com is responding correctly

Oks

• github_user present in bp.json

http://proton.eosusa.io

• CORS headers properly configured
• API node http://proton.eosusa.io is responding correctly
• Get authorizers from account is ok on http://proton.eosusa.io
• History v1 ok for http://proton.eosusa.io
• Hyperion history ok for http://proton.eosusa.io

proton.p2p.eosusa.io:9879

• P2P node proton.p2p.eosusa.io:9879 is responding

https://proton.eosusa.io

• CORS headers properly configured
• API node https://proton.eosusa.io is responding correctly
• Get authorizers from account is ok on https://proton.eosusa.io
• History v1 ok for https://proton.eosusa.io
• Hyperion history ok for https://proton.eosusa.io

Warnings

• github_user missing in bp.json

http://mainnet-api.xprlabs.org

• CORS headers properly configured
• API node http://mainnet-api.xprlabs.org is responding correctly

mainnet-p2p.xprlabs.org:9859

• P2P node mainnet-p2p.xprlabs.org:9859 is responding

https://mainnet-api.xprlabs.org

• CORS headers properly configured
• API node https://mainnet-api.xprlabs.org is responding correctly

Warnings

• github_user missing in bp.json

p2p.madblocks.tech:9876

• P2P node p2p.madblocks.tech:9876 is responding

https://api.madblocks.tech

• CORS headers properly configured
• API node https://api.madblocks.tech is responding correctly
• CORS headers properly configured
• API node https://api.madblocks.tech is responding correctly

Warnings

• github_user missing in bp.json

api.cats.vote:8888

• P2P node api.cats.vote:8888 is responding

https://api.cats.vote

• CORS headers properly configured
• API node https://api.cats.vote is responding correctly

http://api.cats.vote:8888

• CORS headers properly configured
• API node http://api.cats.vote:8888 is responding correctly

Oks

• github_user present in bp.json

http://api.proton.detroitledger.tech

• CORS headers properly configured
• API node http://api.proton.detroitledger.tech is responding correctly

https://api.proton.detroitledger.tech

• CORS headers properly configured
• API node https://api.proton.detroitledger.tech is responding correctly

p2p.proton.detroitledger.tech:1337

• P2P node p2p.proton.detroitledger.tech:1337 is responding

Warnings

• github_user missing in bp.json

p2p.turtlebp.online:19876

• P2P node p2p.turtlebp.online:19876 is responding

http://api-mainnet.turtlebp.online

https://api-mainnet.turtlebp.online

Warnings

• github_user missing in bp.json

http://api.protonnz.com:8888

• CORS headers properly configured
• API node http://api.protonnz.com:8888 is responding correctly

https://api.protonnz.com

• CORS headers properly configured
• API node https://api.protonnz.com is responding correctly

api.protonnz.com:9876

• P2P node api.protonnz.com:9876 is responding

Oks

• github_user present in bp.json

https://api.snipverse.io

• CORS headers properly configured
• API node https://api.snipverse.io is responding correctly

http://api.snipverse.io

• CORS headers properly configured
• API node http://api.snipverse.io is responding correctly

api.snipverse.io:9876

• P2P node api.snipverse.io:9876 is responding

Oks

• github_user present in bp.json

http://proton-public.neftyblocks.com

• CORS headers properly configured
• API node http://proton-public.neftyblocks.com is responding correctly
• Get authorizers from account is ok on http://proton-public.neftyblocks.com

proton-p2p.neftyblocks.com:9876

• P2P node proton-p2p.neftyblocks.com:9876 is responding

https://proton-public.neftyblocks.com

• CORS headers properly configured
• API node https://proton-public.neftyblocks.com is responding correctly
• Get authorizers from account is ok on https://proton-public.neftyblocks.com

Oks

• github_user present in bp.json

http://proton-hyperion.luminaryvisn.com

• Get authorizers from account is ok on http://proton-hyperion.luminaryvisn.com
• History v1 ok for http://proton-hyperion.luminaryvisn.com
• Hyperion history ok for http://proton-hyperion.luminaryvisn.com

http://api.luminaryvisn.com/

• CORS headers properly configured
• API node http://api.luminaryvisn.com/ is responding correctly

https://api.luminaryvisn.com/

• CORS headers properly configured
• API node https://api.luminaryvisn.com/ is responding correctly

p2p.luminaryvisn.com:9876

• P2P node p2p.luminaryvisn.com:9876 is responding

https://proton-hyperion.luminaryvisn.com

• Get authorizers from account is ok on https://proton-hyperion.luminaryvisn.com
• History v1 ok for https://proton-hyperion.luminaryvisn.com
• Hyperion history ok for https://proton-hyperion.luminaryvisn.com

Oks

• github_user present in bp.json

protonp2p.ledgerwise.io:23877

• P2P node protonp2p.ledgerwise.io:23877 is responding

http://protonapi.ledgerwise.io

• CORS headers properly configured
• API node http://protonapi.ledgerwise.io is responding correctly

https://protonapi.ledgerwise.io

• CORS headers properly configured
• API node https://protonapi.ledgerwise.io is responding correctly

Oks

• github_user present in bp.json

https://api.totalproton.tech

• CORS headers properly configured
• API node https://api.totalproton.tech is responding correctly

p2p.totalproton.tech:9831

• P2P node p2p.totalproton.tech:9831 is responding

http://api.totalproton.tech

• CORS headers properly configured
• API node http://api.totalproton.tech is responding correctly

Warnings

• github_user missing in bp.json

https://api.rockerone.io/

• CORS headers properly configured
• API node https://api.rockerone.io/ is responding correctly

api.rockerone.io:9876

• P2P node api.rockerone.io:9876 is responding

https://api.rockerone.io

• CORS headers properly configured
• API node https://api.rockerone.io is responding correctly

Oks

• github_user present in bp.json

http://bp-api.storex.io:8888

• CORS headers properly configured
• API node http://bp-api.storex.io:8888 is responding correctly

https://bp-api.storex.io

• CORS headers properly configured
• API node https://bp-api.storex.io is responding correctly

bp-p2p.storex.io:9999

• P2P node bp-p2p.storex.io:9999 is responding

Warnings

• github_user missing in bp.json

https://xpr-atomic.chaininfra.net

• Atomic API ok for https://xpr-atomic.chaininfra.net

https://api.chaininfra.net

• CORS headers properly configured
• API node https://api.chaininfra.net is responding correctly
• CORS headers properly configured
• API node https://api.chaininfra.net is responding correctly

p2p.chaininfra.net:9876

• P2P node p2p.chaininfra.net:9876 is responding

Oks

• github_user present in bp.json

proton.eosrio.io:8142

• P2P node proton.eosrio.io:8142 is responding

http://proton.eosrio.io

• CORS headers properly configured
• API node http://proton.eosrio.io is responding correctly

https://proton.eosrio.io

• CORS headers properly configured
• API node https://proton.eosrio.io is responding correctly

Oks

• github_user present in bp.json

p2p-xpr.blocksforge.com:9876

• P2P node p2p-xpr.blocksforge.com:9876 is responding

http://api-xpr.blocksforge.com

• CORS headers properly configured
• API node http://api-xpr.blocksforge.com is responding correctly

https://api-xpr.blocksforge.com

• CORS headers properly configured
• API node https://api-xpr.blocksforge.com is responding correctly

https://atomic-xprmain.blocksforge.com

• Atomic API ok for https://atomic-xprmain.blocksforge.com

Oks

• github_user present in bp.json

https://api-xpr-main.danemarkbp.com

• CORS headers properly configured
• API node https://api-xpr-main.danemarkbp.com is responding correctly

p2p-xpr-main.danemarkbp.com:9877

• P2P node p2p-xpr-main.danemarkbp.com:9877 is responding

http://api-xpr-main.danemarkbp.com

• CORS headers properly configured
• API node http://api-xpr-main.danemarkbp.com is responding correctly

Oks

• github_user present in bp.json

https://api-proton.nodeone.network:8344

• CORS headers properly configured
• API node https://api-proton.nodeone.network:8344 is responding correctly
• Error getting authorizers for account ledgerwiseio from https://api-proton.nodeone.network:8344/v1/chain/get_accounts_by_authorizers: Response error: 404

http://api-proton.nodeone.network:8888

• CORS headers properly configured
• API node http://api-proton.nodeone.network:8888 is responding correctly
• Error getting authorizers for account ledgerwiseio from http://api-proton.nodeone.network:8888/v1/chain/get_accounts_by_authorizers: Response error: 404

peer-proton.nodeone.network:9874

• P2P node peer-proton.nodeone.network:9874 is responding

Oks

• github_user present in bp.json

http://proton.protonuk.io

• CORS headers properly configured
• API node http://proton.protonuk.io is responding correctly
• Hyperion history ok for http://proton.protonuk.io
• Error getting authorizers for account ledgerwiseio from http://proton.protonuk.io/v1/chain/get_accounts_by_authorizers: Response error: 404

https://proton.protonuk.io

• CORS headers properly configured
• API node https://proton.protonuk.io is responding correctly
• Hyperion history ok for https://proton.protonuk.io
• Error getting authorizers for account ledgerwiseio from https://proton.protonuk.io/v1/chain/get_accounts_by_authorizers: Response error: 404

proton.protonuk.io:9876

• P2P node proton.protonuk.io:9876 is responding

Oks

• github_user present in bp.json

http://api-proton.eosarabia.net

• CORS headers properly configured
• API node http://api-proton.eosarabia.net is responding correctly
• Error getting authorizers for account ledgerwiseio from http://api-proton.eosarabia.net/v1/chain/get_accounts_by_authorizers: Response error: 404

p2p-proton.eosarabia.net:9876

• P2P node p2p-proton.eosarabia.net:9876 is responding

https://api-proton.eosarabia.net

• CORS headers properly configured
• API node https://api-proton.eosarabia.net is responding correctly
• Error getting authorizers for account ledgerwiseio from https://api-proton.eosarabia.net/v1/chain/get_accounts_by_authorizers: Response error: 404

Warnings

• github_user missing in bp.json

https://api-mainnet.xprcore.com

• CORS headers properly configured
• API node https://api-mainnet.xprcore.com is responding correctly
• Get authorizers from account is ok on https://api-mainnet.xprcore.com

p2p-mainnet.xprcore.com:9876

• P2P node p2p-mainnet.xprcore.com:9876 is responding

http://api-mainnet.xprcore.com

• CORS headers properly configured
• API node http://api-mainnet.xprcore.com is responding correctly
• Error getting authorizers for account ledgerwiseio from http://api-mainnet.xprcore.com/v1/chain/get_accounts_by_authorizers: Response error: 400

Oks

• github_user present in bp.json

http://xpr.a-dex.xyz

• CORS headers properly configured
• API node http://xpr.a-dex.xyz is responding correctly
• Error getting authorizers for account ledgerwiseio from http://xpr.a-dex.xyz/v1/chain/get_accounts_by_authorizers: Response error: 404

https://xpr.a-dex.xyz

• CORS headers properly configured
• API node https://xpr.a-dex.xyz is responding correctly
• Error getting authorizers for account ledgerwiseio from https://xpr.a-dex.xyz/v1/chain/get_accounts_by_authorizers: Response error: 404

p2p-xpr.a-dex.xyz:9976

• P2P node p2p-xpr.a-dex.xyz:9976 is responding

Errors

• No chain api nodes defined

Warnings

• github_user missing in bp.json

proton.cryptolions.io:9876

• P2P node proton.cryptolions.io:9876 is responding

http://proton.cryptolions.io

https://proton.cryptolions.io

Errors

• features not present for node 1 of type query
• No chain api nodes defined

Warnings

• github_user missing in bp.json

protonp2p.blocksindia.com:9876

• P2P node protonp2p.blocksindia.com:9876 is responding

http://protonapi.blocksindia.com/

https://protonapi.blocksindia.com/

Errors

• Error getting bp.json: 404 - Not found

Warnings

• github_user missing in bp.json

https://xpr-mainnet-api.bloxprod.io

• CORS headers properly configured
• API node https://xpr-mainnet-api.bloxprod.io is responding correctly
• History v1 ok for https://xpr-mainnet-api.bloxprod.io
• Hyperion history ok for https://xpr-mainnet-api.bloxprod.io
• Error getting authorizers for account ledgerwiseio from https://xpr-mainnet-api.bloxprod.io/v1/chain/get_accounts_by_authorizers: Response error: 404

xpr-mainnet-p2p.bloxprod.io:19876

• P2P node xpr-mainnet-p2p.bloxprod.io:19876 is responding

https://xpr-mainnet-atm-api.bloxprod.io

• Atomic API ok for https://xpr-mainnet-atm-api.bloxprod.io

Warnings

• github_user missing in bp.json

https://proton-api.alvosec.com

• CORS headers properly configured
• API node https://proton-api.alvosec.com is responding correctly
• Get authorizers from account is ok on https://proton-api.alvosec.com

p2p.alvosec.com:9876

• P2P node p2p.alvosec.com:9876 is responding

http://proton-api.alvosec.com

• CORS headers properly configured
• API node http://proton-api.alvosec.com is responding correctly
• Error getting authorizers for account ledgerwiseio from http://proton-api.alvosec.com/v1/chain/get_accounts_by_authorizers: Response error: 400

Errors

• No chain api nodes defined

Warnings

• github_user missing in bp.json

http://proton.eu.eosamsterdam.net

https://proton.eu.eosamsterdam.net

proton.eu.eosamsterdam.net:9103

• P2P node proton.eu.eosamsterdam.net:9103 is responding

Oks

• github_user present in bp.json

p2p-protonmain.saltant.io:9876

• P2P node p2p-protonmain.saltant.io:9876 is responding

https://aa-xprnetwork-main.saltant.io

• Atomic API ok for https://aa-xprnetwork-main.saltant.io

https://api-xprnetwork-main.saltant.io

• CORS headers properly configured
• API node https://api-xprnetwork-main.saltant.io is responding correctly
• History v1 ok for https://api-xprnetwork-main.saltant.io
• Hyperion history ok for https://api-xprnetwork-main.saltant.io
• Error getting authorizers for account ledgerwiseio from https://api-xprnetwork-main.saltant.io/v1/chain/get_accounts_by_authorizers: Response error: 404

Warnings

• github_user missing in bp.json

proton.cryptotribe.io:19880

• P2P node proton.cryptotribe.io:19880 is responding

http://proton.cryptotribe.io

• CORS headers properly configured
• API node http://proton.cryptotribe.io is responding correctly
• Error getting authorizers for account ledgerwiseio from http://proton.cryptotribe.io/v1/chain/get_accounts_by_authorizers: Response error: 400

https://proton.cryptotribe.io

• CORS headers properly configured
• API node https://proton.cryptotribe.io is responding correctly
• Get authorizers from account is ok on https://proton.cryptotribe.io

Errors

• No chain api nodes defined

Warnings

• github_user missing in bp.json

http://mainchain.simpleblock.org:8888

mainchain.simpleblock.org:9876

• P2P node mainchain.simpleblock.org:9876 is responding

https://mainchain.simpleblock.org

Warnings

• github_user missing in bp.json

mainnet.brotonbp.com:9876

• P2P node mainnet.brotonbp.com:9876 is responding

https://mainnet.brotonbp.com

• CORS headers properly configured
• API node https://mainnet.brotonbp.com is responding correctly
• Error getting authorizers for account ledgerwiseio from https://mainnet.brotonbp.com/v1/chain/get_accounts_by_authorizers: Response error: 404

http://mainnet.brotonbp.com

• CORS headers properly configured
• API node http://mainnet.brotonbp.com is responding correctly
• Error getting authorizers for account ledgerwiseio from http://mainnet.brotonbp.com/v1/chain/get_accounts_by_authorizers: Response error: 404

Errors

• features not present for node 2 of type query
• No chain api nodes defined

Warnings

• github_user missing in bp.json

api.homebloksbp.com:9877

• P2P node api.homebloksbp.com:9877 is responding

https://api.homebloksbp.com

Warnings

• github_user missing in bp.json

https://mainnet.cerebro.host

• API node https://mainnet.cerebro.host is responding correctly
• Get authorizers from account is ok on https://mainnet.cerebro.host
• Invalid value for CORS header access-control-allow-origin or header not present

http://mainnet.cerebro.host

• API node http://mainnet.cerebro.host is responding correctly
• Invalid value for CORS header access-control-allow-origin or header not present
• Error getting authorizers for account ledgerwiseio from http://mainnet.cerebro.host/v1/chain/get_accounts_by_authorizers: Response error: 400

mainnet-p2p.cerebro.host:9876

• P2P node mainnet-p2p.cerebro.host:9876 is responding