Public API Monero Remote Node List

API documentation to search for monitored Monero remote nodes on xmr.ditatompel.com. You can filter based on nettype, countries and more.
On this page

Since my main site that displays list of Monero remote nodes MAY contains Google AdSense (where very likely track users behavior and interests), I decided create dedicated subdomain for my Monero Remote Node pages and it’s API endpoint. No Ads, no user tracking.

API Endpoint and Query Parameters

MethodEndpoint
GEThttps://xmr.ditatompel.com/api/v1/nodes

The default response will display 10 records, sorted from last_checked node.

Optional query string parameters:

  • host: Filter nodes based on hostname or IP address.
  • protocol: Possible values:
    • any or empty string or not set: Return nodes using any protocol.
    • http: Return node using http RPC (excluding Tor network).
    • https: Return nodes using https RPC.
    • tor: Return nodes on Tor network.
  • nettype: Possible values:
    • mainnet: Return mainnet nodes.
    • stagenet: Return stagenet nodes.
    • testnet: Return testnet nodes.
    • any or empty string or not set: No filtering based on nettype is applied.
  • cc: Filter nodes from specific country. Please use two-letter ISO 3166-1 country code.
  • sort_by: Default sorted by last check time. Possible values:
    • last_checked: sorted by last check time (default).
    • uptime: sorted by percentage of uptime.
  • sort_direction: Possible values:
    • desc: descending (default).
    • asc: ascending.
  • status Node status. Possible values :
    • -1 or not set: both online and offline (default).
    • 1: only online nodes.
    • 0: only offline nodes.
  • limit: How many records should be displayed.
  • page: For paging porpose.
  • cors: Filter nodes that have Access-Control-Allow-Origin header or not. Options:
    • 1: Return nodes that have Access-Control-Allow-Origin header.
    • -1: No CORS filter is applied (default).

For example, if you want to list CORS enabled Monero nodes using https from United States sorted from recently checked node:

1curl -sL 'https://xmr.ditatompel.com/api/v1/nodes?cors=1&protocol=https&country=us&sort_by=last_checked&sort_direction=desc' | jq

Response Header

The response header includes the HTTP status code and the content-type. Clients that receive a HTTP status code other than 200 and content-type other than application/json must back-off.

Response Body

The response body includes the information of the query result, query status, and response message. In the example below, the response body of:

1curl -sL 'https://xmr.ditatompel.com/api/v1/nodes?country=SG' | jq
 1{
 2  "status": "ok"
 3  "message": "Success",
 4  "data": {
 5    "total_rows": 1,
 6    "rows_per_page": 10,
 7    "items": [
 8      {
 9        "id": 3,
10        "hostname": "xmr-node.cakewallet.com",
11        "ip": "192.46.228.85",
12        "port": 18081,
13        "protocol": "http",
14        "is_tor": false,
15        "is_available": true,
16        "nettype": "mainnet",
17        "height": 3145189,
18        "adjusted_time": 1715259907,
19        "database_size": 209379655680,
20        "difficulty": 243377341744,
21        "version": "",
22        "uptime": 100,
23        "estimate_fee": 20000,
24        "asn": 63949,
25        "asn_name": "Akamai Connected Cloud",
26        "cc": "SG",
27        "country_name": "Singapore",
28        "city": "Singapore",
29        "latitude": 0,
30        "longitude": 0,
31        "date_entered": 1715009404,
32        "last_checked": 1715259840,
33        "last_check_statuses": [
34          1,
35          1,
36          1,
37          1,
38          1
39        ],
40        "cors": false
41      }
42    ]
43  },
44}
  • status: string, ok means everything looks good.
  • message: string, Information related to your query, success or error message if any.
  • data: object, Information related to your query.
    • total_rows: unsigned int; Total number of nodes found.
    • rows_per_page: unsigned int; Number of nodes per page.
    • items: array of nodes or null if no nodes found. Each node has the structure as follows:
      • id: unsigned int; ID of the node.
      • hostname: string; The hostname / nodes IP address.
      • ip: string; The IP address of node, empty string if hostname is not resolveable (Eg.: TOR nodes)
      • port: unsigned int; TCP port the nodes is using to listen to RPC calls.
      • protocol: string; The protocol used by nodes to listen RPC calls. This can be http, https or empty string.
      • is_tor: boolean; whether the node is accessed through the Tor network.
      • is_available: boolean; whether the node is online or not. False may means node wasn’t ready or my bots can’t connect to nodes RPC daemon.
      • nettype: string; Network type (one of mainnet, stagenet or testnet).
      • height: unsigned int; Current length of longest chain known to daemon.
      • adjusted_time: unsigned int; Current time approximated from chain data, as Unix time.
      • database_size: unsigned int; The size of the blockchain database, in bytes.
      • difficulty: unsigned int; Least-significant 64 bits of the 128-bit network difficulty.
      • version: string; Vesion of remote monero node is running.
      • uptime: float; Uptime percentage of nodes for last 1 month. This likely not the real uptime value since my bots may experiencing network problems (I set connection timeout for 60 seconds).
      • estimate_fee: unsigned int; Amount of fees estimated per byte in atomic units. This just fee estimation, Malicious actors who running remote nodes still can return high fee only when you about to create a transactions.
      • asn: unsigned int; The AS number that owns nodes IP address, 0 if no information available.
      • asn_name: string; The AS name that owns nodes IP addres.
      • cc: string; two-letter ISO 3166-1 country code nodes location, empty string if no information available.
      • country_name: string; Country name based on nodes IP address, empty string if no information available.
      • city: string; City location based on nodes IP address, empty string if no information available.
      • latitude: float; Approx. latitude (geographic coordinate).
      • longitude: float; Approx. longitude (geographic coordinate).
      • date_entered: unsigned int, The Unix time when my bots start monitoring the node.
      • last_checked: unsigned int, The Unix time when was the last time my bot checked into a monero node.
      • last_check_statuses: array (size: 5); last node avaibility status. Possible values:
        • 0: Offline
        • 1: Online
        • 2: not yet checked.
      • cors: boolean, whether the node return with Access-Control-Allow-Origin header or not.

You will get 200 response code, ok status, and even if your query return no nodes (null value in data.items field).

NOTE: My API endpoint is behind Cloudflare reverse proxy, so it’s still cost your privacy. Monero community suggests to always run your own node to obtain the maximum possible privacy and to help decentralize the network.

Changelog

Upcoming changes (2024-05-31, Breaking Changes)

  • Web page UI moved from https://www.ditatompel.com/monero/remote-node to https://xmr.ditatompel.com/remote-nodes/.
  • API endpoint moved from https://api.ditatompel.com/monero/remote-node to https://xmr.ditatompel.com/api/v1/nodes.
  • The source code will be available for public.
  • The default response (without any query params) will display 10 records, sorted from last_checked node (previously it’s sorted from the highest percentage of uptime).
  • The json response structure has been changed, previously the array of nodes was in data field. Now, it’s in data.items.
    • id field added to the array of nodes.
    • last_height field renamed to height.
    • node_version field renamed to version.
    • country field renamed to cc.
    • country_name field added to the array of nodes.
  • host query string added.
  • The http value from protocol query string only return nodes using HTTP RPC, EXCLUDING Tor network.
  • The country query string filter changed from country to cc.
  • The orderby query string changed to sort_by with this possible values:
    • last_checked: sorted by last check time (default).
    • uptime: sorted by percentage of uptime.
  • sort_direction query string added to accomodate sort_by query string. Possible values:
    • desc: descending (default).
    • asc: ascending.
  • page query string added to accomodate limit query string for paging purpose.
  • status query string added. Possible values :
    • -1 or not set: both online and offline (default).
    • 1: only online nodes.
    • 0: only offline nodes.
  • cors query string only accept 1 or -1 value (previously it’s also accept boolean).

Update 2024-01-31 (Breaking Changes)

  • API endpoint moved from https://www.ditatompel.com/api/monero/remote-node to https://api.ditatompel.com/monero/remote-node.
  • x-ditatompel-rate-limit-* headers removed, no rate limit for now.
  • Indication “unchecked node statuses” in data[].last_check_statuses[] changed from null to 2.
  • Added into json field:
    • data[].ip, data[].date_entered, data[].latitude, and data[].longitude
  • Removed from json field:
    • success
    • data[].postal

Diff: 013aa7d.

Because I refactoring my backend, there will most likely be another breaking changes in the near future.

Update 2023-05-24

  • I’ve add cors and last_check_statuses to nodes data record.

Update 2022-05-10

  • I’ve add estimate_fee to nodes data record which I get from get_fee_estimate daemon RPC. This just fee estimation, moneromooo explain that malicious actors who running remote nodes still can return high fee only when you about to create a transactions.
  • selsta create pull request to add warning about high fee on official GUI conformation dialog.
  • The best and safest way is running your own node!
  • Nodes with 0% uptime within 1 month with more than 500 check attempt will be removed. You can always add your node again latter.