Author Topic: API Node Latency Map  (Read 1578 times)

0 Members and 1 Guest are viewing this topic.

Offline iamredbar

Offline litepresence

You can still use this script on your own machine, but I am no longer keeping this live updated; my internet bandwidth is very limited.  Please contact me on telegram @litepresence if you would like to keep a public version alive and I'll point this thread at it.

my github has recently been updated to newer version, you no longer need the basemap, the script will aquire it externally from imgur

Offline litepresence

What does the large pulsating circle around geographical points indicate? Activity?

the bigger the circle the faster the response time to USA east coast

Offline R

  • Hero Member
  • *****
  • Posts: 841
    • View Profile
What does the large pulsating circle around geographical points indicate? Activity?

Offline litepresence

updated repo

- removed whitespace from uploaded images for easier incorporation into user websites
- uploaded basemap.png to repo
- added list of seed nodes to jsonbin under key 'SEEDS' with data ('ip', 'ping', 'geolocation')
- plotting seed nodes on top with yellow dots
- added UTC timestamp to images
- removed misleading green dots in africa from the lens flare in the base map

new sample:

this should satisfy most requirements of issue 1348

« Last Edit: December 13, 2018, 01:12:19 am by litepresence »

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12920
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc

Offline litepresence

for data you go here:

This jsonbin api is at a stationary location.

I update the latency info hourly via python script; I'm on east coast US.

at the link you will find json dictionary with keys:


UNIVERSE is all known bitshares public api nodes mentioned in various github projects; I suspect I have the largest known list of bitshares public api domains

URLS are github urls where node lists can be found; this tool does not contain a list of nodes.  Instead it goes to many different repos on github (such as bitshares, cryptobridge, rudex) etc.  where people have configuration files with lists of nodes; if they update their repo with new nodes, the script finds them with web scraping methods

LIVE is a list of tested nodes that respond within 10 seconds and have a head block number that is not stale. 

PING is list of tuples of ping time for each LIVE node

GEO is geo location data (country, city, longitude, latitude) for each LIVE node as provided by or

COUNT is number of live nodes vs number of nodes in universe

SOURCE_CODE is my github were you can get this tool and run it yourself to produce your own web hosted latency map in distributed fashion.  The latency script will also give you information as to why each down node failed to connect.  A full report looks like this:

You can also pick up copy of metaNODE and ExtinctionEvent while you're there :D

UNIX and UTC are time stamp when this jsonbin was last updated

MAP_URL is a link to a visual image of the data on the jsonbin;
the map url will change every hour!

it will be something like:

and look like one frame of this gif

source code is here, WTFPL:

todo list... upload 24hr animations instead of still images

thanks to free and easy to use api services that make this project is possible:

« Last Edit: December 08, 2018, 08:16:24 pm by litepresence »