Skip to content

Uptime and Reliability

Azzamo operates infrastructure services that are expected to be available, predictable, and transparent about their limitations.

This document explains how uptime is handled, what is guaranteed, and what users should expect in normal and exceptional situations.


Service availability

Azzamo services are designed to run continuously and be accessible at all times.

This includes:

  • Nostr relays
  • Azzamo Blossom media services
  • Public APIs

Services are monitored and maintained to minimize downtime and degradation.


Best-effort uptime

Azzamo provides uptime on a best-effort basis.

  • There is no formal service-level agreement (SLA)
  • Short interruptions may occur due to maintenance or upgrades
  • Emergency interventions may require temporary service disruption

The goal is stability and reliability, not contractual guarantees.


Planned maintenance

Planned maintenance is performed when necessary to improve reliability or security.

  • Maintenance may involve brief downtime
  • Where possible, maintenance is scheduled to minimize impact
  • Major changes are communicated in advance when feasible

Not all maintenance can be announced ahead of time.


Unplanned outages

Despite precautions, unplanned outages can occur.

Common causes include:

  • Infrastructure failures
  • Network or upstream provider issues
  • Software bugs or regressions
  • Security incidents

Azzamo aims to restore service as quickly as possible when outages occur.


Data safety during outages

Outages do not automatically imply data loss.

  • Relay data is stored persistently
  • Media uploads are content-addressed and verified
  • APIs are stateless where possible

However, no system can guarantee zero data loss under all circumstances.


Degraded service

In some situations, services may remain online but operate in a degraded state.

Examples include:

  • Reduced write throughput
  • Temporary rate limiting
  • Disabled non-essential features

Degraded modes are used to preserve core functionality.


Monitoring and response

Azzamo actively monitors its services.

  • Health checks are used to detect failures
  • Automated alerts notify operators
  • Issues are investigated and mitigated promptly

Public status dashboards may be provided where appropriate.


User expectations

Users should understand that:

  • Azzamo is infrastructure, not a hosted application
  • Occasional downtime is unavoidable
  • Redundancy across multiple relays and services is encouraged

Nostr’s design allows users to mitigate outages by connecting to multiple providers.


Summary

Azzamo aims for high availability and operational reliability.

There are no absolute uptime guarantees, but failures are treated seriously and addressed as quickly as possible.