Oks

• github_user present in bp.json

https://api.fio.services

• CORS headers properly configured
• API node https://api.fio.services is responding correctly

http://api.fio.services

• CORS headers properly configured
• API node http://api.fio.services is responding correctly

fio.services:9876

• P2P node fio.services:9876 is responding

Oks

• github_user present in bp.json

http://fio-api.eosiomadrid.io

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

fio-seed.eosiomadrid.io:9877

• P2P node fio-seed.eosiomadrid.io:9877 is responding

https://fio-api.eosiomadrid.io

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

Oks

• github_user present in bp.json

peer.fio.alohaeos.com:9876

• P2P node peer.fio.alohaeos.com:9876 is responding

http://api.fio.alohaeos.com

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

https://api.fio.alohaeos.com

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

Oks

• github_user present in bp.json

fiop2p.ledgerwise.io:25877

• P2P node fiop2p.ledgerwise.io:25877 is responding

https://fioapi.ledgerwise.io

• CORS headers properly configured
• API node https://fioapi.ledgerwise.io is responding correctly
• History v1 ok for https://fioapi.ledgerwise.io
• Hyperion history ok for https://fioapi.ledgerwise.io

http://fioapi.ledgerwise.io

• CORS headers properly configured
• API node http://fioapi.ledgerwise.io is responding correctly
• History v1 ok for http://fioapi.ledgerwise.io
• Hyperion history ok for http://fioapi.ledgerwise.io

Oks

• github_user present in bp.json

http://api.fiosweden.org

p2p.fiosweden.org:9376

• P2P node p2p.fiosweden.org:9376 is responding

https://api.fiosweden.org

Errors

• No chain api nodes defined

Warnings

• github_user missing in bp.json

https://api.fio.greeneosio.com

http://api.fio.greeneosio.com

p2p1.fio.greeneosio.com:9876

• P2P node p2p1.fio.greeneosio.com:9876 is responding

Errors

• No chain api nodes defined

Warnings

• github_user missing in bp.json

http://fio.eosargentina.io

https://fio.eosargentina.io

p2p.fio.eosargentina.io:9873

• Error connecting to p2p.fio.eosargentina.io:9873

Errors

• Error getting utpgt53qtsws bp.json (https://shapeshift.com/bp.json): Expecting value: line 1 column 1 (char 0) <class 'requests.exceptions.JSONDecodeError'>

Errors

• No chain api nodes defined

Warnings

• github_user missing in bp.json

fio.eosrio.io:8122

• P2P node fio.eosrio.io:8122 is responding

https://fio.eosrio.io

http://fio.eosrio.io

Oks

• github_user present in bp.json

https://fio.eosusa.io

• CORS headers properly configured
• API node https://fio.eosusa.io is responding correctly
• History v1 ok for https://fio.eosusa.io
• Error getting authorizers for account ledgerwiseio from https://fio.eosusa.io/v1/chain/get_accounts_by_authorizers: Response error: 404
• Hyperion ElastiSearch missing some blocks

http://fio.eosusa.io

• CORS headers properly configured
• API node http://fio.eosusa.io is responding correctly
• History v1 ok for http://fio.eosusa.io
• Error getting authorizers for account ledgerwiseio from http://fio.eosusa.io/v1/chain/get_accounts_by_authorizers: Response error: 404
• Hyperion ElastiSearch missing some blocks

fio.p2p.eosusa.io:9880

• P2P node fio.p2p.eosusa.io:9880 is responding

Oks

• github_user present in bp.json

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

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

peer-fio.nodeone.network:9876

• P2P node peer-fio.nodeone.network:9876 is responding

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

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

Errors

• Error getting bp.json: 403 - <!DOCTYPE html><html lang="en-US"><head><title>Just a moment...</title><met..

Errors

• Error getting jdyt1ftnsifr bp.json (https://www.thecurrencyhub.io/bp.json): ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) <class 'requests.exceptions.ConnectionError'>

Errors

• No chain api nodes defined

Warnings

• github_user missing in bp.json

https://fio.acherontrading.com/

fio.acherontrading.com:9876

• P2P node fio.acherontrading.com:9876 is responding

Oks

• github_user present in bp.json

http://hyperion.fio.detroitledger.tech

• Hyperion Last action 4 days ago
• Error 500 trying to check hyperion health endpoint

http://api.fio.detroitledger.tech

• Error connecting to http://api.fio.detroitledger.tech/v1/chain/get_info: Response error: 502
• Error testing v1 history from http://api.fio.detroitledger.tech: Expecting value: line 1 column 1 (char 0)

https://api.fio.detroitledger.tech

• Error connecting to https://api.fio.detroitledger.tech/v1/chain/get_info: Response error: 502
• Error testing v1 history from https://api.fio.detroitledger.tech: Expecting value: line 1 column 1 (char 0)

https://hyperion.fio.detroitledger.tech

• Hyperion Last action 4 days ago
• Error 500 trying to check hyperion health endpoint

p2p.fio.eosdetroit.io:1337

• Error connecting to p2p.fio.eosdetroit.io:1337

Errors

• No chain api nodes defined

Oks

• github_user present in bp.json

p2p.fio.genereos.io:9876

• Error connecting to p2p.fio.genereos.io:9876

https://fio.genereos.io

http://fio.genereos.io

Errors

• Error getting bp.json: 404 - <!DOCTYPE html> <html lang="en-us" prefix="content: http://purl.org/rss..

Errors

• Error getting 1imvmzuutqjq bp.json (http://EOSFIN/bp.json): HTTPConnectionPool(host='eosfin', port=80): Max retries exceeded with url: /bp.json (Caused by NameResolutionError("<urllib3.connection.HTTPConnection object at 0x73b6462f1160>: Failed to resolve 'eosfin' ([Errno -3] Temporary failure in name resolution)")) <class 'requests.exceptions.ConnectionError'>

Errors

• Error getting p5fi5ywnitjc bp.json (https://zenblocks.io/bp.json): Certificate error

Errors

• No chain api nodes defined

Warnings

• github_user missing in bp.json

https://eosapi.sentnl.io:4343

eosp2p.sentnl.io:4242

• P2P node eosp2p.sentnl.io:4242 is responding
• Error connecting to eosp2p.sentnl.io:4242: [Errno -2] Name or service not known

http://eosapi.sentnl.io:8080

Warnings

• github_user missing in bp.json

http://api.fio.blocksindia.com/

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

https://api1.fio.blocksindia.com/

• Error connecting to https://api1.fio.blocksindia.com/: <class 'type'> HTTPSConnectionPool(host='api1.fio.blocksindia.com', port=443): Max retries exceeded with url: /v1/chain/get_info (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x73b645a596a0>: Failed to establish a new connection: [Errno 111] Connection refused'))
• Error testing v1 history from https://api1.fio.blocksindia.com/: HTTPSConnectionPool(host='api1.fio.blocksindia.com', port=443): Max retries exceeded with url: /v1/history/get_actions (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x73b6462f2180>: Failed to establish a new connection: [Errno 111] Connection refused'))
• Error getting hyperion history from https://api1.fio.blocksindia.com/: HTTPSConnectionPool(host='api1.fio.blocksindia.com', port=443): Max retries exceeded with url: /v2/history/get_actions?limit=1 (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x73b6463512e0>: Failed to establish a new connection: [Errno 111] Connection refused'))

http://p2p.fio.blocksindia.com:6876

• P2P node http://p2p.fio.blocksindia.com:6876 is responding
• Invalid p2p host:port value http://p2p.fio.blocksindia.com:6876

https://api.fio.blocksindia.com/

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

http://api1.fio.blocksindia.com/

• Invalid value for CORS header access-control-allow-origin or header not present
• Error connecting to http://api1.fio.blocksindia.com/: <class 'type'> Expecting value: line 1 column 1 (char 0)
• Error getting authorizers for account ledgerwiseio from http://api1.fio.blocksindia.com/v1/chain/get_accounts_by_authorizers: Response error: 405
• Error testing v1 history from http://api1.fio.blocksindia.com/: Expecting value: line 1 column 1 (char 0)
• Error getting hyperion history from http://api1.fio.blocksindia.com/: Expecting value: line 1 column 1 (char 0)

Warnings

• github_user missing in bp.json

https://fio.eostribe.io

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

fio.eostribe.io:19877

• Error connecting to fio.eostribe.io:19877

https://fio.eostribe.io/

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

Errors

• Error getting c5aeqmc1trd2 bp.json (https://guarda.co/bp.json): Expecting value: line 2 column 3 (char 3) <class 'requests.exceptions.JSONDecodeError'>

Oks

• github_user present in bp.json

fio-p2p.eoscannon.org:9790

• Error connecting to fio-p2p.eoscannon.org:9790

http://fio-api.eoscannon.org

• Error connecting to http://fio-api.eoscannon.org/v1/chain/get_info: Response error: 404
• Error getting authorizers for account ledgerwiseio from http://fio-api.eoscannon.org/v1/chain/get_accounts_by_authorizers: Response error: 404

https://fio-api.eoscannon.org

• Error connecting to https://fio-api.eoscannon.org: Connection timed out

Errors

• Error getting ezsmbcy2opod bp.json (https://www.eosph.io/bp.json): HTTPSConnectionPool(host='www.eosph.io', port=443): Max retries exceeded with url: /bp.json (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x73b646308e00>: Failed to resolve 'www.eosph.io' ([Errno -3] Temporary failure in name resolution)")) <class 'requests.exceptions.ConnectionError'>

Errors

• No chain api nodes defined

Oks

• github_user present in bp.json

https://fio.blockpane.com

p2p.blockpane.com:9876

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

Oks

• github_user present in bp.json

dmail.dedyn.io:3856

• P2P node dmail.dedyn.io:3856 is responding

https://dmail.dedyn.io

• Error connecting to https://dmail.dedyn.io: Certificate error

http://dmail.dedyn.io

• CORS headers properly configured
• API node http://dmail.dedyn.io is responding correctly

Oks

• github_user present in bp.json

https://fio.eosphere.io

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

http://fio.eosphere.io

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

peer1-fio.eosphere.io:9876

• P2P node peer1-fio.eosphere.io:9876 is responding

Errors

• Error getting bp.json: 404 - <!doctype html> <html lang="vi" prefix="og: https://ogp.me/ns#"> <head> ..

Errors

• No chain api nodes defined

Warnings

• github_user missing in bp.json

fio.cryptolions.io:7987

• P2P node fio.cryptolions.io:7987 is responding

https://fio.cryptolions.io

http://fio.cryptolions.io

Errors

• Error getting bp.json: 404 - <!DOCTYPE html><html lang="en"><head><meta charSet="utf-8"/><meta http-equi..

Oks

• github_user present in bp.json

p2p.eos.barcelona:2093

• P2P node p2p.eos.barcelona:2093 is responding
• Error connecting to p2p.eos.barcelona:2093: [Errno -2] Name or service not known

https://api.eos.barcelona

• Error connecting to https://api.eos.barcelona: <class 'type'> HTTPSConnectionPool(host='api.eos.barcelona', port=443): Max retries exceeded with url: /v1/chain/get_info (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x73b646353380>: Failed to resolve 'api.eos.barcelona' ([Errno -2] Name or service not known)"))

http://api.eos.barcelona

• Error connecting to http://api.eos.barcelona: <class 'type'> HTTPConnectionPool(host='api.eos.barcelona', port=80): Max retries exceeded with url: /v1/chain/get_info (Caused by NameResolutionError("<urllib3.connection.HTTPConnection object at 0x73b646353800>: Failed to resolve 'api.eos.barcelona' ([Errno -2] Name or service not known)"))

Errors

• Error getting nop5m1m5ns4u bp.json (http:///bp.json): Invalid URL 'http:///bp.json': No host supplied <class 'requests.exceptions.InvalidURL'>

Errors

• Error getting fox3ss1ajpca bp.json (https://eosdublin.com/fio.json): Expecting value: line 1 column 1 (char 0) <class 'requests.exceptions.JSONDecodeError'>

Errors

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

Warnings

• github_user missing in bp.json

http://fio.eu.eosamsterdam.net

fio.eu.eosamsterdam.net:9956

• P2P node fio.eu.eosamsterdam.net:9956 is responding

https://fio.eu.eosamsterdam.net

Errors

• No chain api nodes defined

Warnings

• github_user missing in bp.json

https://fio.eosdac.io

http://fio.eosdac.io

fio-p2p.eosdac.io:6876