Skip to content

Backup endpoints

Choice of endpoints

Nodely uses multiple domains for API endpoints to provide end-users and dApps with a diverse choice of CDN operators.

dApps should allow end-users to customize the API endpoint set to increase availability as well as promote decentralization.
Back-end solutions should adopt automatic or feature-flag failover to quickly switch endpoints sets in case of global CDN outage.

Algorand network free endpoints

${net} = mainnet | testnet

Endpoint schemaFunctionTypeCDNAvailability
${net}-api.4160.nodely.devPrimaryAlgod APICloudflareHighest, 19 regions
${net}-idx.4160.nodely.devPrimaryIndexer APICloudflareHighest, 19 regions
${net}-api.algonode.xyzBackupAlgod APIBunnyHigh, 19 regions
${net}-idx.algonode.xyzBackupIndexer APIBunnyHigh, 19 regions
${net}-api.algonode.networkDisasterAlgod APIno CDNDNS failover, 12 regions
${net}-idx.algonode.networkDisasterIndexer APIno CDNDNS failover, 12 regions

Algorand network commercial endpoints

${net} = mainnet | testnet

Endpoint schemaFunctionTypeCDNAvailability
${net}-api.4160.nodely.ioCommercial onlyAlgod APICloudflareHighest + Argo boost, 21 regions
${net}-idx.4160.nodely.ioCommercial onlyIndexer APICloudflareHighest + Argo boost, 21 regions
${net}-api.4160.nodely.devSecondaryAlgod APICloudflareHighest
${net}-idx.4160.nodely.devSecondaryIndexer APICloudflareHighest
${net}-api.algonode.xyzBackupAlgod APIBunnyHigh
${net}-idx.algonode.xyzBackupIndexer APIBunnyHigh
${net}-api.algonode.networkDisasterAlgod APIno CDNDNS failover
${net}-idx.algonode.networkDisasterIndexer APIno CDNDNS failover