# Akash provider endpoint changes versus identity changes

A provider endpoint change is different from an akash1 identity change. A new access URL alone does not establish a new earnings history. A new identity likewise does not prove that old leases migrated automatically.

- Canonical: https://iotahome.site/en/learn/akash-provider-endpoint-change
- Publisher: IOTA Watch
- Topics: Akash
- Published: 2026-10-26
- Updated: 2026-10-26

## At a glance

A provider endpoint change is different from an akash1 identity change. A new access URL alone does not establish a new earnings history. A new identity likewise does not prove that old leases migrated automatically.

## What to check

Preserve the old address, endpoint, change time and official lease identifiers. After the change, compare the directory identity, then inspect each lease in the provider console. Editing a nickname or saved monitoring record affects organization only; it does not execute an on-chain migration or amend contract terms.

## Example

Example: the same akash1 provider changes its API domain and temporarily becomes unreadable. Check the endpoint and last successful observation. Neither zeroing old revenue nor duplicating the provider follows from a different URL.

## Continue

[Open project monitor](https://iotahome.site/en/projects/akash)

## Sources and implementation

- [akash.network](https://akash.network/docs/providers/getting-started/)
- [console.akash.network](https://console.akash.network/providers)